ORA-31480: staging database and source database cannot be the same
Cause: A CDC API call specified a source database name that matched the staging database on which the CDC API call is being executed
Action: Make sure that the CDC API call is being executed from the staging database and that the source database is correctly specified. The source database and staging database need to be different databases
https://support.oracle.com/
http://www.oracle.com/
ORA-31479: could not create LogMiner session
Cause: Failure during create of a new LogMiner session while advancing an asynchronous change set. This is an internal error
Action: Contact Oracle Corporation
ORA-31478: could not detach LogMiner session after change set advance
Cause: Failure during detach from a LogMiner session after successful advance of an asynchronous change set. This is an internal error. This exception is raised when an asynchronous change set has been successfully advanced but CDC was unable to detach from the LogMiner session
Action: Contact Oracle Corporation
ORA-31477: could not detach LogMiner session during cleanup
Cause: Failure during detach from a LogMiner session during advance of an asynchronous change set. This is an internal error. This exception is raised when a previous exception occurred during the internal protocol with LogMiner, after which Change Data Capture attempted to detach the LogMiner session as part of recovery. The detach session also failed
Action: Contact Oracle Corporation
ORA-31476: a change table data column is missing from the source table
Cause: While advancing a change set, an CDC determined that at least one of the data columns in a change table does not match the name of any of the columns in the source table. The source table column listis stored in dictionary table SYSTEM.LOGMNR_OBJ$
Action: Make sure that all of the data columns of the change table have the same names as the corresponding columns in the source table, and that all the columns exist in the source table
ORA-31475: redo log catalog contains no metadata for the source table
Cause: While advancing a change set, an CDC attempted to query the LogMiner dictionary system tables to obtain the columns from the source table. The query returned no rows. This may be because none of the redo logs contains a catalog, or it may be an internal error
Action: First, verify that the source system contains the source table. execute dbms_logmnr_d.build procedure to populate the redos log with logminer dictionary information. If this has been done and the problem persists, then contact Oracle Corporation
ORA-31472: Importing Change Data Capture version string.string is too new
Cause: An attempt was made to Import a file that was exported by a newer version of Oracle than the target instance
Action: If possible, re-export the file using a version of export that matches the import target. Objects can not be imported into previous versions of Oracle that did not support them
ORA-31471: invalid OBJECT_ID value
Cause: An object_id value of 'y' was specified for an asynchronous change table
Action: Specify an object_id parameter value of 'n' and call the procedure again
ORA-31470: asynchronous change tables must contain the RSID$ column
Cause: If creating an asynchronous change table, the RSID was set to 'N'. If altering an asynchronous change table with an operation parameter of 'DROP' RSID was set to 'Y'
Action: When creating asynchronous change tables, always specify 'Y' for the RSID parameter. When altering asynchronous change tables always specify 'N' for RSID
ORA-31469: cannot enable Change Data Capture for change set string
Cause: The change set has reached the specified limit that was set up by the CREATE_CHANGE_SET command
Action: Check the alert log to find out whether capture, apply or both reached the limit. Once apply reaches its limit, the change set is permanently disabled. Create a new change set with new limits to continue capturing data