ORA-31468: cannot process DDL change record
Cause: The change set has stop_on_ddl enabled and was trying to process a DDL change record
Action: Check the alert log to find out what the DDL record contained. Make any necessary changes to the change tables. Call ALTER_CHANGE_SET with recover_after_error and remove_ddl set to 'Y'
https://support.oracle.com/
http://www.oracle.com/
ORA-31467: no column found in the source table
Cause: The OBJECT_ID flag was set to 'Y' on the call to CREATE_CHANGE_TABLE and change table belongs to the synchronous change set. The corresponding object column was not detected in the source table
Action: Create the change table with the OBJECT_ID flag set to 'N' or investigate why the object column is not in the source table and add it to the source table
ORA-31466: no publications found
Cause: Did not find any publications that matched the input parameters or the user does not have the privileges to access the specified publication
Action: Check the input parameters on the call to SUBSCRIBE. Validate that the proposed source table has been published by checking the USER_PUBLICATIONS view for that source table. Contact the publisher if user privileges are required to access the publication. Retry the command with correct security or publication information
ORA-31465: cannot obtain a lock on the subscription
Cause: A timeout occurred while trying to place a lock on the subscription. Another session had already acquired the lock on the subscription
Action: Ensure the subscription name is correct and correct it if necessary. If it is already correct, try the operation again after the session holding the lock has released it
ORA-31464: target table for the change table no longer exists
Cause: User tried to drop a change table but its underlying storage table (that contains the change data) has been dropped
Action: Contact Oracle Corporation
ORA-31463: logfile location string is an empty directory
Cause: The directory specification for logfile location for the change source, is an empty directory
Action: 1. Make sure it is the correct location of the logfiles. If it is, make sure the directory contains logfiles. OR 2. perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles
ORA-31462: internal error while accessing metadata
Cause: An unexpected internal error occurred while CDC was accessing its internal Metadata
Action: Contact Oracle Corporation
ORA-31461: logfile location string contains no files that match pattern string
Cause: The directory specification for logfile location for the change source, does not contain any files whose names pattern-match the logfile_suffix
Action: 1. Make sure that the logfile location contains logfiles whose names match the logfile_suffix pattern for the change set. OR 2. perform ALTER CHANGE SOURCE and change the logfile_suffix such that it matches the names of existing logfiles in the directory
ORA-31460: logfile location string is not an existing directory
Cause: The directory specification for logfile location for the change source, does not correspond with an existing directory, or the directory was not accessible
Action: 1. Create the directory if it does not exist. If the directory does exist, change the file system permissions so the directory can be accessed. OR 2. perform ALTER CHANGE SOURCE and change the logfile_location to be an existing directory that contains the logfiles
ORA-31459: system triggers for DBMS_CDC_PUBLISH package are not installed
Cause: One or more required system triggers are not installed. These triggers are required for the proper operation of Change Data Capture. Operations on Change tables cannot continue
Action: Install or reenable the triggers, or reinstall the package