ORAOCI9 Stage INSERTing Twice - unique constraint violated

[smuppidi]

Hi All,

8x SERVER
STAGE - ORAOCI9

When inserting records into the taget oracle table (which is truncated) job throws warning messages of "unique constraint (UK) violated".But the data being inserted DO NOT have any Duplicates on UK.

The reason this is happening is becuase of the execution of INSERT statement twice by the Target oracle stage.
The log shows something like below-

11:30:45 AM 7/14/2009 JobName.StageName Using NLS map UTF8
11:30:45 AM 7/14/2009 JobName.StageName Using NLS map UTF8
11:30:46 AM 7/14/2009 JobName.StageName INSERT INTO TABLEX (A, B, c) VALUES (SEQ.NEXTVAL,:1,:2)
11:30:46 AM 7/14/2009 JobName.StageName INSERT INTO TABLEX (A, B, c) VALUES (SEQ.NEXTVAL,:1,:2)

There is onle ONE INSERT (custom SQL statement) in my ORAOCI9 target stage.Why would it execute the INSERT twice?
Has anyone encountered this before? Please advice.

Thanks,
Satish.

[chulett]

Never seen any such thing. What 'update action' are you using? How many links are going into the stage?

[smuppidi]

Never seen any such thing. What 'update action' are you using? How many links are going into the stage?

It is a "Custom SQL Statement" like below -

INSERT INTO TABLEX (A, B, c) VALUES (SEQ.NEXTVAL,:1,:2)

[smuppidi]

...And only ONE link.

[chulett]

Very odd. First suggestion would be to delete that stage from the job and set it back up again from scratch, see if that fixes whatever is going on.

[Sainath.Srinivasan]

Your lines from log appear twice. Is it how it appears in the job log?

You can do the following to analyse
1.) Try disabling the unique constraint and check the result after the run.
2.) Include a constraint to pass only one row from source and check the result
3.) Redirect the same output to sequential file and check its contents
4.) Truncate the table manually before run and re-run the job