My Oracle Support Banner

Changing Database Sequence Definition Will Not Impatch DBAdapter Cached Sequence (Doc ID 3057769.1)

Last updated on NOVEMBER 06, 2024

Applies to:

Oracle Integration 3 - Version 22.06 and later
Information in this document applies to any platform.

Symptoms

Database side has INCREMENT BY 50 and The adapter generates sequence numbers in a batch of 50. After integration activation, customer finds exiting data has some overlap with database sequence. So sequence from database side is changed with ALTER SEQUENCE statement. But it seems this change from database side has no effect to dbAdapter at all, the dbAdapter cached sequence number is still being used before they are used up.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.