Sequence number not at expected start value on target database after import
(Doc ID 834914.1)
Last updated on JANUARY 22, 2020
Applies to:
Oracle Database - Enterprise Edition - Version 8.1.7.0 to 11.2.0.0 [Release 8.1.7 to 11.2]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Information in this document applies to any platform.
NOTE: In the images and/or the document content below, the user information and data used represents fictitious data. Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Symptoms
You might see:
A gap in sequence numbers may appear after import
A sequence number does not start at desired initial value after import.
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 |