Sequence number issue

[dnat]

Hi,

I have a job where i am generating the sequence number through KeyMgtGetNextValueConcurrent('N') and storing in unique id.

The job.invocation id aborted with ORA-00001: unique constraint violation on the unique id index.

When i check the current max value of the database and the value in SDKSequences file, the SDKSequences file contains one value greater than the database value. Looks like no issue with the sequence number generation.

I am wondering what could be the reason for this unique constraint violation.

[ray.wurlod]

The key in SDKSequences obviously got out of synchronization with the key of the Oracle table, or perhaps you are not using the correct sequence name in your KeyMgtGetNextKey() call.

[chulett]

I am wondering what could be the reason for this unique constraint violation.

So are we, and it's not really a question we can answer for you other than to state what Ray did. The routine has no clue if some other process has already issued a given number or not, it just assures that it only hands a number out once.

You'll need to do the investigation, find out where the records you collided with came from.