Oracle Error Messages: 05/29/12

Tuesday, 29 May 2012

ORA-31511: name exceeds maximum length of 30 characters

ORA-31511: name exceeds maximum length of 30 characters

Cause: A name was supplied that exceeds the maximum length of 30 characters.

Action: Change the name so it does not exceed 30 characters

ORA-31510: name uses reserved prefix CDC$

ORA-31510: name uses reserved prefix CDC$

Cause: A name was specified that starts CDC$. The name prefix CDC$ is reserved for use by Oracle Corporation.

Action: Change the name so it does not start with characters CDC$

ORA-31509: publication does not exist

ORA-31509: publication does not exist

Cause: The specified publication did not exist or the specified subscription subscribed to a publication that no longer exists.

Action: Recheck the publication or subscription specified. Either call the procedure again with an existing publication or create a new subscription that only subscribes to existing publications.

ORA-31508: invalid parameter value for synchronous change set

ORA-31508: invalid parameter value for synchronous change set

Cause: A parameter value was specified that is not supported for synchronous change sets.

Action: Correct the call to supply only valid parameter values for a synchronous change set. Synchronous change sets only support the default values for the following parameters: begin_scn, end_scn, begin_date, end_date, stop_on_ddl, supplemental_processes.

ORA-31507: %s parameter value longer than maximum length string

ORA-31507: %s parameter value longer than maximum length string

Cause: A value was specified for a parameter that was longer than the maximum permitted length.

Action: Correct the call to supply a shorter value for this parameter that fits within the maximum length.

ORA-31506: duplicate subscription name string

ORA-31506: duplicate subscription name string

Cause: A subscription by the specifed name already exists.

Action: Recreate the subscription with a unique name.

ORA-31505: cannot alter or drop predefined change set

ORA-31505: cannot alter or drop predefined change set

Cause: The caller attempted to alter or drop the predefined change set SYNC_SET.

Action: Do not attempt to alter or drop the predefined change set or correct call to supply the name of a user-created change set.

ORA-31504: cannot alter or drop predefined change source

ORA-31504: cannot alter or drop predefined change source

Cause: The caller attempted to alter or drop one of the predefined change sources HOTLOG_SOURCE or SYNC_SOURCE.

Action: Do not attempt to alter or drop a predefined change source or correct call to supply the name of a user-created change source.

ORA-31503: invalid date supplied for begin_date or end_date

ORA-31503: invalid date supplied for begin_date or end_date

Cause: The caller supplied an invalid value for begin_date or end_date. The value must be a valid date value.

Action: Correct call to supply a valid date value for begin_date and or or end_date.

ORA-31502: invalid number supplied for supplemental_processes

ORA-31502: invalid number supplied for supplemental_processes

Cause: The caller supplied an invalid value for supplemental_processes. The value must be a positive integer.

Action: Correct call to supply a positive integer value for supplemental_ processes.

ORA-31501: change source string is not an AutoLog change source

ORA-31501: change source string is not an AutoLog change source

Cause: A change source was specified that was not an AutoLog change source, but an AutoLog change source was required.

Action: Correct call to supply an AutoLog change source.

ORA-31500: change source string is not a ManualLog change source

ORA-31500: change source string is not a ManualLog change source

Cause: A change source was specified that is not a ManualLog change source, but a ManualLog change source is required.

Action: Correct call to supply a ManualLog change source.

ORA-31499: null value specified for required parameter string

ORA-31499: null value specified for required parameter string

Cause: A null value was specified for a parameter that requires an explicit value.

Action: Correct call to supply a value for this parameter.

ORA-31498: description and remove_description cannot both be specified

ORA-31498: description and remove_description cannot both be specified

Cause: The description and remove_description parameters were both specified.

Action: Check the values of description and remove_description. Correct call to only supply one of these values.

ORA-31497: invalid value specified for first_scn

ORA-31497: invalid value specified for first_scn

Cause: The first_scn was not greater than zero or was less than the previous value of first_scn.

Action: Check the value of first_scn. Correct it to make sure it is an integer greater than zero and greater than any previous value for this change source.

ORA-31496: must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables

ORA-31496: must use DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE to drop change tables

Cause: An attempt was made to use the SQL command DROP TABLE for change tables, but DROP TABLE is not supported for change tables.

Action: Use the DBMS_CDC_PUBLISH.DROP_CHANGE_TABLE procedure instead of the DROP TABLE command.

ORA-31495: error in synchronous change table on string . string

ORA-31495: error in synchronous change table on string . string

Cause: There was an error originating from this synchronous change table. One possible cause is that schema redefinition has occurred on the source table and one or more columns in the change table are now a different type than corresponding source columns. Another possible cause is that there is a problem accessing the synchronous change table.

Action: Check further error messages in stack for more detail about the cause. If there has been schema redefinition, drop and recreate the synchronous change table.

ORA-31494: could not activate a LogMiner session

ORA-31494: could not activate a LogMiner session

Cause: Failure during activation of a LogMiner session while advancing an asynchronous change set. This is an internal error.

Action: Contact Oracle Corporation

ORA-31493: could not prepare session for LogMiner session

ORA-31493: could not prepare session for LogMiner session

Cause: Failure during prepare session for a LogMiner session while advancing an asynchronous change set. This is an internal error.

Action: Contact Oracle Corporation

ORA-31492: could not set session parameters for LogMiner session

ORA-31492: could not set session parameters for LogMiner session

Cause: Failure during set parameters for a LogMiner session while advancing an asynchronous change set. This is an internal error.

Action: Contact Oracle Corporation

ORA-31491: could not add logfile to LogMiner session

ORA-31491: could not add logfile to LogMiner session

Cause: Failure during add logfile to a LogMiner session while advancing an asynchronous change set. This is an internal error.

Action: Contact Oracle Corporation

ORA-31490: could not attach to LogMiner session

ORA-31490: could not attach to LogMiner session

Cause: Failure during attach to a LogMiner session while advancing an asynchronous change set. This is an internal error.

Action: Contact Oracle Corporation

ORA-31488: cannot support change set string in this configuration

ORA-31488: cannot support change set string in this configuration

Cause: Change sources with the hot mine option enabled are limited to 1 change set. The system detected an existing change set so a second one can not be created.

Action: Associate the change set with a different change source.

ORA-31487: cannot support begin dates or end dates in this configuration

ORA-31487: cannot support begin dates or end dates in this configuration

Cause: The specified values cannot be used in a Distributed HotLog configuration.

Action: Remove the specified values from the CREATE_CHANGE_SET CDC API call.

ORA-31486: cannot support column string in this configuration

ORA-31486: cannot support column string in this configuration

Cause: The specified column cannot be used in a Distributed HotLog configuration when the source database version is 9.2.0.6 or 10.1.0.0.

Action: Remove the specified column from the CREATE_CHANGE_TABLE or ALTER_CHANGE_TABLE CDC API call.

ORA-31485: invalid database link

ORA-31485: invalid database link

Cause: The database link used to connect from a staging database to a source database was invalid. The database link may not exist, may not be accessible to the current user, or may have been redefined since the Distributed HotLog change source was originally created.

Action: Make sure that there is a database link to the source_database for the Distributed HotLog change source. Make sure this database link is accessible to the current user.

ORA-31484: source database version must be at least 9.2.0.6 or greater

ORA-31484: source database version must be at least 9.2.0.6 or greater

Cause: The source database is not at version 9.2.0.6 or higher.

Action: Upgrade the source database to 9.2.0.6 or higher.

ORA-31483: cannot have spaces in the parameter string

ORA-31483: cannot have spaces in the parameter string

Cause: The specifed parameter contained at least 1 space character.

Action: Check the value of the specified parameter. Remove the spaces and reissue the CDC API call.

ORA-31482: invalid option for non-distributed Hotlog change source

ORA-31482: invalid option for non-distributed Hotlog change source

Cause: A CDC API call specified enabled_source = Y on a non-Distributed HotLog change source.

Action: Specify a Distributed HotLog change source.

ORA-31481: change source string is not a HotLog change source

ORA-31481: change source string is not a HotLog change source

Cause: A change source was specified that was not a HotLog change source, but a HotLog change source was required.

Action: Correct the call to supply a HotLog change source.

ORA-31480: staging database and source database cannot be the same

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.

ORA-31479: could not create LogMiner session

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

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

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

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

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

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

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

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

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.

ORA-31468: cannot process DDL change record

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 .

ORA-31467: no column found in the source table

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

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

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

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

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

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

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

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

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.

ORA-31458: an internal error occurred

ORA-31458: an internal error occurred

Cause: This is an internal error.

Action: Contact Oracle Worldwide Customer Support and report the error.

ORA-31457: maximum length of description field exceeded

ORA-31457: maximum length of description field exceeded

Cause: The maximum number of characters permitted in the description field was exceeded.

Action: The maximum length of the description field is 30 characters. Ensure the length does not exceed this value and retry the command.

ORA-31456: error executing a procedure in the DBMS_CDC_UTILITY package

ORA-31456: error executing a procedure in the DBMS_CDC_UTILITY package

Cause: An internal attempt to invoke a procedure within the DBMS_CDC_ UTILITY package failed.

Action: Check the trace logs for more information. Ensure that the package has been installed successfully. Try issuing a DESCRIBE command from SQL on the package. If it fails, then try reinstalling the package. If it succeeds then try invoking one of the procedures from SQL.