Changes to the behavior of Import with a Streams configuration or AQ commit time queues
(Doc ID 1380295.1)
Last updated on APRIL 09, 2020
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 126.96.36.199 [Release 10.2 to 11.2] Oracle Database - Enterprise Edition - Version 188.8.131.52 to 184.108.40.206 [Release 12.1] Oracle Database Cloud Schema Service - Version N/A and later Oracle Database Exadata Cloud Machine - Version N/A and later Oracle Cloud Infrastructure - Database Service - Version N/A and later Information in this document applies to any platform.
Specifically this issue affects both Datapump import (impdp) and conventional import (imp)
Changes introduced in the January 2012 Critical Patch Update and associated Patch Set Updates / Bundles may require additional user actions when performing a database or user import. You should read this document if you have performed, or intend performing, an import into a patched database. The following functionality is impacted:
Import of Streams capture configuration data
Import of AQ commit time queues
It is especially important to read this document if you see a messages like those below reported either to the terminal or the alert log:
Cannot set an SCN larger than the current SCN. If a Streams Capture configuration was imported then the Apply that processes the captured messages needs to be dropped and recreated. See My Oracle Support article number 1380295.1
sqlplus@xx(TNS V1-V3): Cannot set an SCN larger than the current SCN.
This document is for DBAs and other Oracle users that may perform an import after installing January 2012 Critical Patch Update or later, or any equivalent bundle.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!