DSXchange

If your insert DML is updated as I noted to include the reference to SEQ_NAME.NEXTVAL, then yes - the only time it will be incremented is when the insert statement is executed.

Excellent putzing!

ajithaselvan wrote:Any help?

Seriously? You waited what - all of an hour an a half before pushing for help? Learn some patience, this is an all volunteer post-when-you-can peer support board, not 1-800-HELPMENOW.

For anyone to be able to help, you're going to need to provide details. For example, we have no idea what your job design looks like nor what exactly it is you are doing in the RDBMS stage. Looks like you are working with XMLTYPE data? Stored procedure?

<split out from and linked back to 'jacked post> :!: Please - no matter how "same" your issue is, always start your own post rather than jumping on someone else's post your search turned up. If you feel it would be helpful, link back to any related posts from the past. And just do this on...

I don't have any documentation in front of me at the moment but it should be pretty straight-forward to work out what you need there. Basically, for every field you are not grouping by you have to tell the Aggregator what aggregation method you want applied. One of the available methods is Max or Ma...

By "common merge stage" do you actually mean a Link Collector?

OK, that only changes my answer slightly. After the lookup, branch out two links from a transformer - one for records where the lookup succeeded and another for where it failed. For the former, process as normal (I've been assuming an insert follows). For the latter, process as indicated previously....

Shuffle = Randomize, in a sense. As in re-arrange whom has which address within a given state.

Which was Frankline's point I do believe. However, much like Mike I never considered lumping multiple independent flows in a single job any kind of a good idea for the reasons he stated.

Aggregator. Group by the first column, take max() on both of the other two columns.

Rather than select it on every row (which you could do via a lookup) I would just use custom sql. Pass all columns except the sequence field to the target stage, let it generate the DML and then modify it to include the sequence field with a value of SEQ_NAME.NEXTVAL which tells the insert DML to au...

Then it must be something they've smartened up in later releases as I don't recall that being the case in the past.

I believe that format string will only work for single digit months / days like the 7/4 example posted but will have issues with dates like 10/4 or 7/25 or 11/16. The link James posted shows not only the valid format tags but also the options that are valid for them. Check out the "s" note...

Colin - This post by our friend Ken Bland may help.