DSXchange

What about running the SQL directly via SQL Plus or TOAD.

Ora 1 is primary key violation.

You can link the message constraint with the table to obtain more information.

Concatenate the 3 files and then sort.

You may need NLS.

Your question has the answer. User Merge stage.

This is a voluntary site. There is nothing called urgent. If you want your problem to resolved immediately, sign up for a 24x7 or premium with your support provider.

Did you try the command from your OS shell? What happens?

Use blat or external mail utility that supports that functionality.

How will you know which one of the duplicate is to be picked?

The soln will be to store the row number. Again this leads to more steps and using hash file for reference.

The user had 'insert or update rows' in a single link and not 2 different links. So that cannot be the reason for lock.

You can do that to identify duplicate keys. But what about the data value associated with the key?

As ArndW has pointed out, you need to supply some examples for others to understand and answer.

You can sort the rows before using stage variables.

As Ken suggested, getting Parameter Manager may solve your problem to include params list in multiple jobs.

Job Activity is the stage in job seq to invoke jobs.

Check whether some other person / application is modifying the table.

In that case, I think you need stage variables and not row splitter.