Sequence number not at expected start value on target database after import
Last updated on JUNE 10, 2009
Applies to:Oracle Server - Enterprise Edition - Version: 18.104.22.168 to 22.214.171.124
This problem can occur on any platform.
You might see:
A gap in sequence numbers may appear after import
A sequence number does not start at desired initial value after import.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms