Thursday 31 May 2012

ORA-32005: error while parsing size specification (string(

ORA-32005: error while parsing size specification (string(

Cause: The value specified for an alter operation on a size parameter is not valid

Action: Correct the value and retry the operation

ORA-32004: obsolete and or or deprecated parameter(s) specified

ORA-32004: obsolete and or or deprecated parameter(s) specified

Cause: One or more obsolete and or or parameters were specified in the SPFILE or the PFILE on the server side.

Action: See alert log for a list of parameters that are obsolete. or deprecated. Remove them from the SPFILE or the server side PFILE.

ORA-32003: error occured processing parameter string

ORA-32003: error occured processing parameter string

Cause: An error occured while parsing the parameter file.

Action: See additional errors to determine the root cause.

ORA-32002: cannot create SPFILE already being used by the instance

ORA-32002: cannot create SPFILE already being used by the instance

Cause: A create spfile command is trying to write to an SPFILE that was used to startup the instance.

Action: Specify a different SPFILE name

ORA-32001: write to SPFILE requested but no SPFILE specified at startup

ORA-32001: write to SPFILE requested but no SPFILE specified at startup

Cause: An alter system command or an internal self tuning mechanism requested a write to the SPFILE but no SPFILE was used to startup the instance

Action: Create an SPFILE and re-start the instance using the SPFILE.

ORA-31901: the current operation was cancelled by the user

ORA-31901: the current operation was cancelled by the user

Cause: The user requested to cancel current operation

Action: No action is necessary

ORA-31700: Very long string supplied for AUDIT_SYSLOG_LEVEL parameter

ORA-31700: Very long string supplied for AUDIT_SYSLOG_LEVEL parameter

Cause: Very long string supplied for AUDIT_SYSLOG_LEVEL in init.ora

Action: Use a valid facility.level such as local1.notice as described in syslog s manual pages

ORA-31698: Error stack buffer size must be specified and must be greater than 0.

ORA-31698: Error stack buffer size must be specified and must be greater than 0.

Cause: Called get worker exception and either specified NULL or 0 for the error stack size argument.

Action: Be sure to specify am error stack buffer size that is big enough to hold the error stack string (e.g. 4096 bytes). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31697: aborting operation at process order number string

ORA-31697: aborting operation at process order number string

Cause: User asked for it.

Action: Don t ask for it.

ORA-31696: unable to export or import string using client specified string method

ORA-31696: unable to export or import string using client specified string method

Cause: Table attributes prevent client specified method for exporting or importing data.

Action: Use default DATA_ACCESS parameter value.

ORA-31695: Inconsistent master table on restart. The following SQL statement returned string identical objects. string

ORA-31695: Inconsistent master table on restart. The following SQL statement returned string identical objects. string

Cause: Master table on restart has the same object inserted multiple times.

Action: Restart not possible, reissue original export or import.

ORA-31694: master table string failed to load or unload

ORA-31694: master table string failed to load or unload

Cause: Master table failed to load or unload.

Action: Check load or unload error, correct problem and retry command.

ORA-31693: Table data object string failed to load or unload and is being skipped due to error: string

ORA-31693: Table data object string failed to load or unload and is being skipped due to error: string

Cause: Table failed to load or unload due to some error.

Action: Check load or unload error, correct problem and retry command.

ORA-31692: The following SQL statement failed trying to insert a row into the Master table: string

ORA-31692: The following SQL statement failed trying to insert a row into the Master table: string

Cause: Bad code.

Action: Fix code and reissue export or import command.

ORA-31691: The worker received message number string from the MCP, which is invalid.

ORA-31691: The worker received message number string from the MCP, which is invalid.

Cause: Bad code.

Action: Fix mcp code and reissue export or import command.

ORA-31690: Process name buffer size must be specified and must be greater than 0.

ORA-31690: Process name buffer size must be specified and must be greater than 0.

Cause: Called get worker exception and either specified NULL or 0 for the buffer size argument.

Action: Be sure to specify a buffer size that is big enough to hold the worker process name (e.g. 30 bytes). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31689: illegal value for base worker id, string

ORA-31689: illegal value for base worker id, string

Cause: Called create worker processes with an illegal base worker id value specified.

Action: Make sure that the base worker id value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31688: Worker process string failed during startup.

ORA-31688: Worker process string failed during startup.

Cause: The worker process whose name is listed failed during startup.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31687: error creating worker process string with worker id string

ORA-31687: error creating worker process string with worker id string

Cause: Attempt to create the listed worker process failed.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31686: error creating worker processes

ORA-31686: error creating worker processes

Cause: Setup to create worker processes failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31679: Table data object string has long columns, and longs can not be loaded or unloaded using a network link

ORA-31679: Table data object string has long columns, and longs can not be loaded or unloaded using a network link

Cause: Table data objects that contain long columns can not be selected over a network link.

Action: Export this table to a file and then import the same table from the file.

ORA-31676: illegal value for number of workers, string

ORA-31676: illegal value for number of workers, string

Cause: Called create worker processes with an illegal number of workers specified.

Action: Make sure that the number of workers value is greater than 0 and less than the maximum value for the platform (normally 32767). If this error occurs from a Data Pump client (e.g. expdp or impdp) and you specified the parallel parameter, try the operation again with a smaller value for the parallel parameter. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31675: worker process interrupt for unexpected death of master process

ORA-31675: worker process interrupt for unexpected death of master process

Cause: A worker process was requested to clean up and exit (signaled by PMON, doing cleanup because the master process died unexpectedly).

Action: If this error occurs from a Data Pump client (e.g. expdp or impdp), it means that the master process for the operation died unexpectedly. Check the log file for the operaton and the trace file for the master process for any additional information. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31674: worker process interrupt for unhandled exception in master process

ORA-31674: worker process interrupt for unhandled exception in master process

Cause: A worker process was requested to clean up and exit because an unhandled exception occurred in the master process.

Action: If this error occurs from a Data Pump client (e.g. expdp or impdp), it means that the master process for the operation had an unhandled exception. Check the log file for the operaton and the trace file for the master process for any additional information. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31673: worker process interrupt for normal exit by master process

ORA-31673: worker process interrupt for normal exit by master process

Cause: A worker process was requested to clean up and exit because the master process is doing a normal exit.

Action: If this error occurs from a Data Pump client (e.g. expdp or impdp). it means that the master process for the operation exited prematurely. Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31672: Worker process string died unexpectedly.

ORA-31672: Worker process string died unexpectedly.

Cause: A Data Pump process model worker process died unexpectedly, so PMON is cleaning up the process.

Action: Check your system for problems. Check the trace file for the process, if one was created, for any additional information. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31671: Worker process string had an unhandled exception.

ORA-31671: Worker process string had an unhandled exception.

Cause: A Data Pump process model worker process had an unhandled exception condition.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31670: Username argument must be specified and non-null.

ORA-31670: Username argument must be specified and non-null.

Cause: Called change user with a NULL username or a null string.

Action: Specify a valid username argument. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31669: Worker process string violated startup protocol.

ORA-31669: Worker process string violated startup protocol.

Cause: The worker process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31668: Timeout before worker process string finished initialization.

ORA-31668: Timeout before worker process string finished initialization.

Cause: The worker process whose name is listed started up but did not finish its initialization within the allowed time limit.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31667: parameter name can not be defaulted

ORA-31667: parameter name can not be defaulted

Cause: A null was supplied for the parameter name.

Action: Fix the call by providing a valid parameter name.

ORA-31666: Master process string had an unhandled exception.

ORA-31666: Master process string had an unhandled exception.

Cause: A Data Pump process model master process had an unhandled exception condition.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31665: mode can only be defaulted for IMPORT and SQL_FILE operations

ORA-31665: mode can only be defaulted for IMPORT and SQL_FILE operations

Cause: The job mode can not be null except for IMPORT and SQL_FILE operations.

Action: Fix the call to specify the job mode.

ORA-31664: unable to construct unique job name when defaulted

ORA-31664: unable to construct unique job name when defaulted

Cause: The job name was defaulted, and the name creation algorithm was unable to find a unique job name for this schema where the table name (for the master table) didn t already exist.

Action: Specify a job name to use or delete some of the existing tables causing the name conflicts.

ORA-31663: metadata remap name can not be defaulted

ORA-31663: metadata remap name can not be defaulted

Cause: A null metadata remap name was supplied.

Action: Fix the call to specify a metadata remap name.

ORA-31662: metadata transform name can not be defaulted

ORA-31662: metadata transform name can not be defaulted

Cause: A null metadata transform name was supplied.

Action: Fix the call to specify a metadata transform name.

ORA-31661: there are no metadata transform values of type VARCHAR2

ORA-31661: there are no metadata transform values of type VARCHAR2

Cause: The specified metadata transform value was an invalid type.

Action: Fix the call to specify a valid metadata transform value.

ORA-31660: metadata filter name can not be defaulted

ORA-31660: metadata filter name can not be defaulted

Cause: A null metadata filter name was supplied.

Action: Fix the call to specify a metadata filter name.

ORA-31659: status message was invalid type - detaching job

ORA-31659: status message was invalid type - detaching job

Cause: Message from the master process on the status queue had an invalid message type, indicating a failure in the protocol.

Action: Reattach and retry the operation. Contact Oracle Customer Support if the problem persists.

ORA-31658: specifying a schema name requires a table name

ORA-31658: specifying a schema name requires a table name

Cause: The caller specified a schema name but neglected to specify a corresponding table name.

Action: Fix the call to include a table name.

ORA-31657: data filter name can not be defaulted

ORA-31657: data filter name can not be defaulted

Cause: A null data filter name was supplied.

Action: Fix the call to specify a data filter name.

ORA-31656: cannot use TABLESPACE_EXPR filter with transportable mode

ORA-31656: cannot use TABLESPACE_EXPR filter with transportable mode

Cause: A TABLESPACE_EXPR metadata filter was supplied for for a transportable mode import job. Transportable mode import does not support the subsetting of tablespaces from a dump file set.

Action: Remove the filter expression.

ORA-31655: no data or metadata objects selected for job

ORA-31655: no data or metadata objects selected for job

Cause: After the job parameters and filters were applied, the job specified by the user did not reference any objects.

Action: Verify that the mode of the job specified objects to be moved. For command line clients, verify that the INCLUDE, EXCLUDE and CONTENT parameters were correctly set. For DBMS_DATAPUMP API users, verify that the metadata filters, data filters, and parameters that were supplied on the job were correctly set.

ORA-31654: unable to convert file or volume size as specified to a number

ORA-31654: unable to convert file or volume size as specified to a number

Cause: File or volume size specification has an error the prevents it from being converted into a numeric value.

Action: Fix the call.

ORA-31653: unable to determine job operation for privilege check

ORA-31653: unable to determine job operation for privilege check

Cause: Failure trying to determine the operation of the current job in order to test for appropriate privileges.

Action: Retry in case it s an intermittent failure. If it still fails, detach, reattach, and retry the call. Contact Oracle Customer Support if the problem persists.

ORA-31652: command response message was invalid type - detaching job

ORA-31652: command response message was invalid type - detaching job

Cause: Something horribly wrong with the command or response protocol.

Action: Reattach and retry operation. Contact Oracle Customer Support if the problem persists.

ORA-31651: communication error with master process - detaching job

ORA-31651: communication error with master process - detaching job

Cause: Unexpected failure trying to communicate with the master process.

Action: Attach again and retry operation. Contact Oracle Customer Support if the problem persists.

ORA-31650: timeout waiting for master process response

ORA-31650: timeout waiting for master process response

Cause: After creating the job infrastructure and sending the initial message to the master process, it failed to respond in the allotted time and most likely aborted during startup.

Action: Retry the open or attach request. Contact Oracle Customer Support if the problem persists.

ORA-31649: Master process string violated startup protocol.

ORA-31649: Master process string violated startup protocol.

Cause: The master process whose name is listed started up but then exited before notifying the creating process that it was finished with initialization.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31648: Timeout before master process string finished initialization.

ORA-31648: Timeout before master process string finished initialization.

Cause: The master process whose name is listed started up but did not finish its initialization within the allowed time limit.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31645: unable to read from dump file string

ORA-31645: unable to read from dump file string

Cause: Import could not read from the dumpfile, probably because of a device error. This message is usually followed by a device message from the operating system.

Action: Take appropriate action to restore the device.

ORA-31644: unable to position to block number string in dump file string

ORA-31644: unable to position to block number string in dump file string

Cause: Export or Import was unable to position its file pointer to a specific block within the dump file. This message is usually followed by device messages from the operating system.

Action: Take appropriate action based on the device messages.

ORA-31643: unable to close dump file string

ORA-31643: unable to close dump file string

Cause: Export or Import was unable to close the dump file. This message is usually followed by device messages from the operating system.

Action: Take appropriate action to restore the device.

ORA-31642: the following SQL statement fails: string

ORA-31642: the following SQL statement fails: string

Cause: An internal error was generated from package DBMS_METADATA.

Action: Contact Oracle Customer Support and report the error.

ORA-31641: unable to create dump file string

ORA-31641: unable to create dump file string

Cause: Export was unable to create the specified file with write enabled.

Action: Check the file name and file system for the source of the error.

ORA-31640: unable to open dump file string for read

ORA-31640: unable to open dump file string for read

Cause: Import was unable to open the export file for reading. This message is usually followed by device messages from the operating system.

Action: Take appropriate action to restore the device.

ORA-31639: unexpected data found

ORA-31639: unexpected data found

Cause: The Master Table or Data Pump file contents appear invalid. The table or file may not have been produced by a Data Pump job, or they may have been corrupted.

Action: Select a different job name (Master Table) or replace the table or file with one produced by Data Pump.

ORA-31638: cannot attach to job string for user string

ORA-31638: cannot attach to job string for user string

Cause: Unable to attach a job to a session. Refer to any following or prior error messages for clarification.

Action: Eliminate the problems indicated.

ORA-31637: cannot create job string for user string

ORA-31637: cannot create job string for user string

Cause: Unable to create or restart a job. Refer to any following or prior error messages for clarification.

Action: Eliminate the problems indicated.

ORA-31636: session is already attached to job string for user string

ORA-31636: session is already attached to job string for user string

Cause: The session executing the attach is already attached to the specified job.

Action: Select a different job or create a new session.

Wednesday 30 May 2012

ORA-31635: unable to establish job resource synchronization

ORA-31635: unable to establish job resource synchronization

Cause: A lock used in synchronizing Data Pump resources during job creation and deletion could not be obtained during job creation. This indicates that a process for some other Data Pump job has not released the lock due to an internal error.

Action: Eliminate the processes for any failed Data Pump job and try to create the new job again. If the error continues to occur, contact Oracle Customer Support and report the error.

ORA-31634: job already exists

ORA-31634: job already exists

Cause: Job creation or restart failed because a job having the selected name is currently executing. This also generally indicates that a Master Table with that job name exists in the user schema. Refer to any following error messages for clarification.

Action: Select a different job name, or stop the currently executing job and re-try the operation (may require a DROP on the Master Table).

ORA-31633: unable to create master table string.string

ORA-31633: unable to create master table string.string

Cause: Job creation failed because a Master Table and its indexes could not be created, most commonly due to the pre-existance of a table with the same name (job name) in the user schema. Refer to any following error messages for clarification.

Action: Select a different job name, DROP the existing table, or eliminate any problems indicated by the following error messages.

ORA-31632: master table string.string not found, invalid, or inaccessible

ORA-31632: master table string.string not found, invalid, or inaccessible

Cause: A Master Table is required but no such table exists, or the content is not consistent with that of a valid Master Table, or the table is not accessible. Refer to any following error messages for clarification.

Action: Make sure a valid Master Table exists, and eliminate any problems indicated by the following error messages.

ORA-31631: privileges are required

ORA-31631: privileges are required

Cause: The necessary privileges are not available for operations such as: restarting a job on behalf of another owner, using a device as a member of the dump file set, or ommiting a directory object associated with any of the various output files. Refer to any following error messages for additional information.

Action: Select a different job to restart, try a different operation, or contact a database administrator to acquire the needed privileges.

ORA-31630: a job name is required to attach a job for user string

ORA-31630: a job name is required to attach a job for user string

Cause: No job name was supplied for an attach and the user has either no jobs executing or mutiple jobs executing.

Action: Provide a job name for attach to use in selecting an executing job, or to use for restarting a stopped job.

ORA-31629: unable to allocate additional memory

ORA-31629: unable to allocate additional memory

Cause: A dynamic memory allocation failure occurred.

Action: Report this problem to a database administrator.

ORA-31628: error getting worker process exception

ORA-31628: error getting worker process exception

Cause: Attempt to get a worker process exception failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31627: API call succeeded but more information is available

ORA-31627: API call succeeded but more information is available

Cause: The user specified job parameters that yielded informational messages.

Action: Call DBMS_DATAPUMP.GET_STATUS to retrieve additional information.

ORA-31626: job does not exist

ORA-31626: job does not exist

Cause: An invalid reference to a job which is no longer executing, is not executing on the instance where the operation was attempted, or that does not have a valid Master Table. Refer to any following error messages for clarification.

Action: Start a new job, or attach to an existing job that has a valid Master Table.

ORA-31625: Schema string is needed to import this object, but is unaccessible

ORA-31625: Schema string is needed to import this object, but is unaccessible

Cause: An error occurred when attempting to import objects. The schema specified is needed to import this object, but access to this schema is not available.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31624: A job cannot be modified after it has started.

ORA-31624: A job cannot be modified after it has started.

Cause: The user attempted to change the definition of a Data Pump job through filters, transforms or parameters after it had started. These changes can only be made while defining a job.

Action: Stop the current job and rerun it with the correct definition.

ORA-31623: a job is not attached to this session via the specified handle

ORA-31623: a job is not attached to this session via the specified handle

Cause: An attempt to reference a job using a handle which is invalid or no longer valid for the current session.

Action: Select a handle corresponding to a valid active job or start a new job.

ORA-31622: ORACLE server does not have string access to the specified file

ORA-31622: ORACLE server does not have string access to the specified file

Cause: An attempt was made to read or write files within protected directories.

Action: Correct the file or directory permissions and try the call again.

ORA-31621: error creating master process

ORA-31621: error creating master process

Cause: Setup to create a master process failed.

Action: Refer to any following error messages for possible actions. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31620: file or device string cannot be specified for string operation

ORA-31620: file or device string cannot be specified for string operation

Cause: There was an inappropriate use of file or device in the current operation.

Action: Correct operation or job setup.

ORA-31619: invalid dump file string

ORA-31619: invalid dump file string

Cause: Either the file was not generated by Export or it was corrupted.

Action: If the file was indeed generated by Export, report this as an Import bug and submit the export file to Oracle Customer Support.

ORA-31618: dump file size too small

ORA-31618: dump file size too small

Cause: The value specified for the FILESIZE parameter or the VOLUMESIZE parameter was too small to hold the header information for the export file, plus any data.

Action: Increase the value of the FILESIZE or VOLUMESIZE parameter.

ORA-31617: unable to open dump file string for write

ORA-31617: unable to open dump file string for write

Cause: Export was unable to open the export file for writing. This message is usually followed by device messages from the operating system.

Action: Take appropriate action to restore the device.

ORA-31616: unable to write to dump file string

ORA-31616: unable to write to dump file string

Cause: Export was unable to write to the export file, probably because of a device error. This message is usually followed by a device message from the operating system.

Action: Take appropriate action to restore the device.

ORA-31615: routine string received this error: string

ORA-31615: routine string received this error: string

Cause: The specified routine failed and the specific error text is included in this error message (the last %s string).

Action: Correct inputs to the specified routine.

ORA-31614: routine string received this error from string: string

ORA-31614: routine string received this error from string: string

Cause: The call to the specified routine failed and the specific error text is included in this error message (the last %s string).

Action: Correct inputs to the specified routine.

ORA-31613: Master process string failed during startup.

ORA-31613: Master process string failed during startup.

Cause: The master process whose name is listed failed during startup.

Action: Refer to any following error messages for possible actions. Check the trace log for the failed process to see if there is any information about the failure. Correct the error, if possible, and try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31612: Allocation of process descriptor failed.

ORA-31612: Allocation of process descriptor failed.

Cause: During creation of a master process or a worker process, a failure occurred allocating a process descriptor for the process.

Action: Try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31610: cannot call this function from a non-master process

ORA-31610: cannot call this function from a non-master process

Cause: Called a Data Pump process model function from a process which is not a master process.

Action: Create a master process first. Then call the function from the master process. If this error occurs from a Data Pump client (e.g. expdp or impdp), try the operation again. If the error occurs again, contact Oracle Customer Support and report the error.

ORA-31609: error loading file string from file system directory string

ORA-31609: error loading file string from file system directory string

Cause: The installation script initmeta.sql failed to load the named file from the file system directory into the database.

Action: Examine the directory and see if the file is present and can be read.

ORA-31608: specified object of type string not found

ORA-31608: specified object of type string not found

Cause: The specified object was not found in the database.

Action: Correct the object specification and try the call again.

ORA-31607: function string is inconsistent with transform.

ORA-31607: function string is inconsistent with transform.

Cause: Either (1) FETCH_XML was called when the DDL transform was specified, or (2) FETCH_DDL was called when the DDL transform was omitted.

Action: Correct the program.

ORA-31606: XML context number does not match any previously allocated context

ORA-31606: XML context number does not match any previously allocated context

Cause: A method in package UTL_XML was called with an invalid XML context handle. All handles must have previously been allocated by UTL_XML.XMLINIT.

Action: Always call XMLINIT before any other methods in pkg. UTL_XML.

ORA-31605: the following was returned from string in routine string: LPX-number: string

ORA-31605: the following was returned from string in routine string: LPX-number: string

Cause: An LPX routine (XML or XSL processing) returned an internal error number to its PL or SQL wrapper routine in facility KUX which provides the implementation for package UTL_XML.

Action: Look up the LPX error number and follow its corrective action.

ORA-31604: invalid string parameter string for object type string in function string

ORA-31604: invalid string parameter string for object type string in function string

Cause: The specified parameter value is not valid for this object type.

Action: Correct the parameter and try the call again.

ORA-31603: object string of type string not found in schema string

ORA-31603: object string of type string not found in schema string

Cause: The specified object was not found in the database.

Action: Correct the object specification and try the call again.

ORA-31602: parameter string value string in function string inconsistent with string

ORA-31602: parameter string value string in function string inconsistent with string

Cause: The parameter value is inconsistent with another value specified by the program. It may be inconsistent with the object type associated with the OPEN context, or it may be of the wrong datatype (a boolean rather than a text string or vice versa).

Action: Correct the program

ORA-31601: Function string cannot be called now that fetch has begun.

ORA-31601: Function string cannot be called now that fetch has begun.

Cause: The function was called after the first call to FETCH_xxx.

Action: Correct the program.

ORA-31600: invalid input value string for parameter string in function string

ORA-31600: invalid input value string for parameter string in function string

Cause: A NULL or invalid value was supplied for the parameter.

Action: Correct the input value and try the call again.

ORA-31536: cannot support encrypted column string in the source table

ORA-31536: cannot support encrypted column string in the source table

Cause: One of the columns specified in the parameter COLUMN_TYPE_LIST was an encrypted column in the source table

Action: remove the encrypted column in the parameter COLUMN_TYPE_LIST

ORA-31535: cannot support change source string in this configuration

ORA-31535: cannot support change source string in this configuration

Cause: Each database can only have one change source with hot mine option enabled. The system detected an existing hot mine change source in the database, therefore, a second hot mine change source cannot be created.

Action: Remove the existing change source and create this new change source again.

ORA-31534: Change Data Capture string publisher string is missing DBA role

ORA-31534: Change Data Capture string publisher string is missing DBA role

Cause: The publisher does not have the DBA role, which is required by the Change Data Capture operation.

Action: Grant the DBA role the Change Data Capture publisher.

ORA-31533: only one change set (string) is allowed in change source

ORA-31533: only one change set (string) is allowed in change source

Cause: A Distributed HotLog change source can contain at most one change set.

Action: Create a new change source and create the change set in the new change source.

ORA-31532: cannot enable change source string

ORA-31532: cannot enable change source string

Cause: The change source cannot be enabled when there is no change table created in any of the change sets associated with the change source.

Action: Add a change table to a change set before enabling the the change source.

ORA-31531: could not find column string in CDC subscriber view string.string

ORA-31531: could not find column string in CDC subscriber view string.string

Cause: A column was missing in a subscriber view for an imported Change Data Capture subscription.

Action: It is likely that this view existed before the import operation and import did not overwrite it. Determine whether the imported subscriber view should supercede the original view. If so, drop the original view and retry the import. If not, the subscriber view must have a different name in order to be imported.

ORA-31530: could not find published column string for CDC subscriber view string.string

ORA-31530: could not find published column string for CDC subscriber view string.string

Cause: A published column was missing for an imported Change Data Capture subscription.

Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing published column was included in the original export. If needed, perform the export again, including the schema of the missing published column.

ORA-31529: could not find publication for CDC subscriber view string.string

ORA-31529: could not find publication for CDC subscriber view string.string

Cause: A publication was missing for an imported Change Data Capture subscription.

Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing publication was included in the original export. If needed, perform the export again, including the schema of the missing publication.

ORA-31528: could not find change set string for CDC subscription string

ORA-31528: could not find change set string for CDC subscription string

Cause: The change set was missing for an imported Change Data Capture subscription.

Action: Drop the imported subscription because it is invalid. Verify that the schema containing the missing change set was included in the original export. If needed, perform the export again, including the schema of the missing change set.

ORA-31527: could not find source column string for CDC change table string.string

ORA-31527: could not find source column string for CDC change table string.string

Cause: A source column was missing for an imported Change Data Capture change table.

Action: Drop the imported change table because it is invalid. Verify that the schema containing the source table was included in the original export. If needed, perform the export again, including the schema of the missing source table.

ORA-31526: could not find source table string.string for CDC change table string.string

ORA-31526: could not find source table string.string for CDC change table string.string

Cause: The source table was missing or was not set up correctly for an imported Change Data Capture change table. A synchronous change table requires the source table to exist and have the Change Data Capture trigger defined on it. An asynchronous change table requires table rules to be defined for the source table.

Action: Drop the imported change table because it is invalid. Verify that the schema containing the source table was included in the original export. If needed, perform the export again, including the schema of the source table. If change table is asynchronous, ensure that STREAMS_CONFIGURATION=y is specified for the import.

ORA-31525: could not find column string in CDC change table string.string

ORA-31525: could not find column string in CDC change table string.string

Cause: A column was missing for an imported Change Data Capture change table.

Action: It is likely that this table existed before the import operation and import did not overwrite it. Determine whether the imported change table should supercede the original table. If so, drop the original table and retry the import. If not, the change table must have a different name in order to be imported.

ORA-31524: could not find change set string for CDC change table string.string

ORA-31524: could not find change set string for CDC change table string.string

Cause: The change set was missing for an imported Change Data Capture change table.

Action: Drop the imported change table because it is invalid. Verify that the schema containing the missing change set was included in the original export. If needed, perform the export again, including the schema of the missing change set.

ORA-31523: could not find change source string for CDC change set string

ORA-31523: could not find change source string for CDC change set string

Cause: The change source was missing for an imported Change Data Capture change set.

Action: Drop the imported change set because it is invalid. Verify that the schema containing the missing change source was included in the original export. If needed, perform the export again, including the schema of the missing change source.

ORA-31522: could not find Streams object string for CDC change set string

ORA-31522: could not find Streams object string for CDC change set string

Cause: An underlying Streams capture, apply, or queue was missing for an imported Change Data Capture change set.

Action: Drop the imported change set because it is invalid. Retry the import, ensuring that STREAMS_CONFIGURATION=y is specified.

ORA-31521: CDC subscription string already subscribes to publication ID string column string

ORA-31521: CDC subscription string already subscribes to publication ID string column string

Cause: A Change Data Capture subscription intended for import already subscribed to a published column.

Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again.

ORA-31520: CDC subscription string already subscribes to publication ID string

ORA-31520: CDC subscription string already subscribes to publication ID string

Cause: A Change Data Capture subscription intended for import already subscribed to a publication.

Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again.

ORA-31519: CDC subscription string already exists

ORA-31519: CDC subscription string already exists

Cause: A Change Data Capture subscription intended for import already existed.

Action: Either verify that the existing subscription has the desired characteristics or drop the existing subscription and perform the import again.

ORA-31518: change column string already exists in CDC change table string.string

ORA-31518: change column string already exists in CDC change table string.string

Cause: A column in a Change Data Capture change table intended for import was already present in the change table.

Action: Either verify that the change table contains the desired columns or drop the change table and perform the import again.

ORA-31517: CDC change table string.string already exists

ORA-31517: CDC change table string.string already exists

Cause: A Change Data Capture change table intended for import already existed.

Action: Either verify that the existing change table has the desired characteristics or drop the existing change table and perform the import again.

ORA-31516: CDC change set string already exists

ORA-31516: CDC change set string already exists

Cause: A Change Data Capture change set intended for import already existed.

Action: Either verify that the existing change set has the desired characteristics or drop the existing change set and perform the import again.

ORA-31515: CDC change source string already exists

ORA-31515: CDC change source string already exists

Cause: A Change Data Capture change source intended for import already existed.

Action: Either verify that the existing change source has the desired characteristics or drop the existing change source and perform the import again.

ORA-31514: change set string disabled due to capture error

ORA-31514: change set string disabled due to capture error

Cause: This change set has encountered a capture error and was disabled.

Action: Contact the change set s publisher to request that the capture error be resolved. Subscriptions using this change set cannot be activated or have their subscription windows extended or purged until the capture error is resolved.

ORA-31513: unsupported column type specified in change table

ORA-31513: unsupported column type specified in change table

Cause: A source column of an unsupported type was specified for inclusion in a change table. Columns types of LOB or LONG are not currently supported for change capture.

Action: Change the column list so that it does not include columns of LOB or LONG types.

ORA-31512: name cannot contain double quotation marks

ORA-31512: name cannot contain double quotation marks

Cause: A name containing a double quotation mark was supplied. Subscription names cannot contain the double quotation mark.

Action: Change the name so it has no double quotation marks

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.

ORA-31455: nothing to ALTER

ORA-31455: nothing to ALTER

Cause: The specified column list is NULL and all optional control columns are N.

Action: Specify one or more columns to ALTER.

ORA-31454: invalid value string for operation parameter, expecting: ADD or DROP

ORA-31454: invalid value string for operation parameter, expecting: ADD or DROP

Cause: The specified value was not ADD or DROP.

Action: Specify ADD or DROP and retry the command.

ORA-31453: invalid value string for parameter, expecting: Y, N, or NULL

ORA-31453: invalid value string for parameter, expecting: Y, N, or NULL

Cause: The specified value was not Y, N or NULL.

Action: Specify Y, N or NULL for the parameter and retry the command.

ORA-31452: invalid value string for parameter, expecting: Y or N

ORA-31452: invalid value string for parameter, expecting: Y or N

Cause: The specified value was not Y or N.

Action: Specify Y or N for the parameter and retry the command.

ORA-31451: invalid value string for capture_values, expecting: OLD, NEW, or BOTH

ORA-31451: invalid value string for capture_values, expecting: OLD, NEW, or BOTH

Cause: The specified value was not a valid option for a capture_values.

Action: Specify a valid option and retry the command.

ORA-31450: invalid value for change_table_name

ORA-31450: invalid value for change_table_name

Cause: The specified value was not a valid name for a Change Table.

Action: Specify a valid name and retry the command.

ORA-31449: invalid value for change_set_name

ORA-31449: invalid value for change_set_name

Cause: The specified value was not a valid name for a Change Set.

Action: Specify a valid name and retry the command.

Monday 28 May 2012

ORA-31448: invalid value for change_source

ORA-31448: invalid value for change_source

Cause: The specified value was not a valid name for a Change Source.

Action: Specify a valid name and retry the command.

ORA-31447: cannot create change tables in the SYS schema

ORA-31447: cannot create change tables in the SYS schema

Cause: Attempted to create a change table in the SYS schema. This is not allowed.

Action: Use a different existing schema and retry the command.

ORA-31446: this session does not own the lock handle for string

ORA-31446: this session does not own the lock handle for string

Cause: CDC attempted to acquire a lock on the resource, does not own the the lock associated with the lock. This is an internal error.

Action: Contact Oracle corporation

ORA-31445: invalid lock handle while acquiring lock on string

ORA-31445: invalid lock handle while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but encountered a invalid lock handle, which did not correspond to any existing handle.

Action: Contact Oracle corporation

ORA-31444: parameter error while acquiring lock on string

ORA-31444: parameter error while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but encountered a problem passing parameters to the lock manager.

Action: Contact Oracle corporation

ORA-31443: deadlock detected while acquiring lock on string

ORA-31443: deadlock detected while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but encountered a deadlock.

Action: Contact Oracle corporation

ORA-31442: operation timed out while acquiring lock on string

ORA-31442: operation timed out while acquiring lock on string

Cause: CDC attempted to acquire a lock on the resource, but the operation timed out.

Action: Retry the operation later.

ORA-31441: table is not a change table

ORA-31441: table is not a change table

Cause: User attempted to execute the DROP_CHANGE_TABLE procedure on a table that is not a CHANGE table. This can also occur when a CHANGE table object has been orphaned. CHANGE tables can become orphaned after a CREATE_CHANGE_TABLE failure or an incomplete DROP_CHANGE_TABLE.

Action: Check spelling. If error was due to an incorrect name, then retry the procedure using the correct name. To drop a table that is not a CHANGE table, or an orphaned CHANGE table, use the DROP TABLE DDL command instead.

ORA-31440: change set string is empty and cannot be advanced

ORA-31440: change set string is empty and cannot be advanced

Cause: User attempted to advance a change set which does not contain any change tables. Without change tables, a change set cannot be advanced.

Action: Create change tables in the change set, then retry the advance.

ORA-31439: subscription is already active

ORA-31439: subscription is already active

Cause: The subscription is already active.

Action: Check name and retry.

ORA-31438: duplicate change table string

ORA-31438: duplicate change table string

Cause: A change table by the specified name already exists.

Action: Recreate the change table with a unique name.

ORA-31437: duplicate change set string

ORA-31437: duplicate change set string

Cause: A change set by the specified name already exists.

Action: Recreate the change set with a unique name.

ORA-31436: duplicate change source string

ORA-31436: duplicate change source string

Cause: A change source by the specifed name already exists.

Action: Recreate the change source with a unique name.

ORA-31435: an error occurred during the purge operation

ORA-31435: an error occurred during the purge operation

Cause: An error occurred during the purge operation

Action: Check the logfile for a more detailed report of the underlying errors.

ORA-31434: purge is currently running

ORA-31434: purge is currently running

Cause: Called the PURGE procedure while a purge job was currently running.

Action: Wait for purge to complete before reissueing this command.

ORA-31433: subscriber view does not exist

ORA-31433: subscriber view does not exist

Cause: The subscription did not contain this subscriber view.

Action: Recheck the name, and specify the name of an existing subscriber view.

ORA-31432: invalid source table

ORA-31432: invalid source table

Cause: Either the schema_name.source_table did not exist or it did not belong to this subscription.

Action: Check the spelling of the schema_name and source_table. Verify that the specifed table exists in the specifed schema and is subscribed to by the subscription.

ORA-31431: all source tables must belong to the synchronous change set

ORA-31431: all source tables must belong to the synchronous change set

Cause: Not all of the source tables belong to the synchronous change set.

Action: Check the spelling of the source tables. Make sure that all of the source tables belong to the synchronous change set.

ORA-31430: subscriber view exists

ORA-31430: subscriber view exists

Cause: A view that is already in use was specified for the subscriber view.

Action: Call the SUBSCRIBE procedure using a different subscriber view name.

ORA-31429: subscription has not been activated

ORA-31429: subscription has not been activated

Cause: The called procedure required an activated subscription.

Action: Check the subscription name and correct if necessary. Call the ACTIVATE_SUBSCRIPTION procedure for this subscription and then reissue the original command.

ORA-31428: no publication contains all the specified columns

ORA-31428: no publication contains all the specified columns

Cause: One or more of the specifed columns cannot be found in a single publication.

Action: Change the subscription request to select only columns that are in the same publication. Consult the USER_PUBLISHED_COLUMNS view to see current publications.

ORA-31427: publication string already subscribed

ORA-31427: publication string already subscribed

Cause: The subscription already contained this publication.

Action: Check the values of subscription_name and publication_id. Check any other subscribe calls to see if they subscribe to columns that are shared among more than one publication on the same source table. Do not attempt to subscribe to the same publication more than once in the same subscription. Use the publication_id variant of the SUBSCRIBE call if needed to specify precise publications.

ORA-31426: cannot modify active subscriptions

ORA-31426: cannot modify active subscriptions

Cause: The subscription was already activated so that additional calls to SUBSCRIBE were prohibited.

Action: Subscribe to all the desired tables and columns before activating the subscription. Ensure that the correct subscription name is specifed.

ORA-31425: subscription does not exist

ORA-31425: subscription does not exist

Cause: The subscription either did not exist or did not belong to this user.

Action: Call the function again with a valid subscription name.

ORA-31424: change table has active subscriptions

ORA-31424: change table has active subscriptions

Cause: The change table is subscribed to, so it cannot be dropped.

Action: Do not drop a change table while there are active subscribers. If this is an emergency, use the FORCE parameter. This will forcibly drop the change table out from under all subscribers.

ORA-31423: change table string does not contain column string

ORA-31423: change table string does not contain column string

Cause: Issued ALTER_CHANGE_TABLE with a drop operation and the specified column does not exist in the change table.

Action: Recheck the names, and call the procedure again.

ORA-31422: owner schema string does not exist

ORA-31422: owner schema string does not exist

Cause: Value specifed for the owner parameter does not contain the name of an existing schema in the database.

Action: Recheck the name, and call the procedure again using an existing schema name.

ORA-31421: change table does not exist

ORA-31421: change table does not exist

Cause: Specified change table does not exist.

Action: Recheck the name, and call the procedure again using an existing change table.

ORA-31420: unable to submit the purge job

ORA-31420: unable to submit the purge job

Cause: When creating the first change table, a purge job is submitted to the job queue. Submission of this purge job failed.

Action: Make sure that job queue processes are enabled and are currently running. If this does not solve the problem, contact Oracle.

ORA-31419: source table string does not exist

ORA-31419: source table string does not exist

Cause: When creating a synchronous change table, the underlying source table must exist when the procedure is called. In this case, the source table did not exist.

Action: Specify the name of an existing table.

ORA-31418: source schema string does not exist

ORA-31418: source schema string does not exist

Cause: Trying to create a synchronous change table and the source schema did not match any existing schema names in the database.

Action: Specify the name of an existing schema.

ORA-31417: column list contains control column string

ORA-31417: column list contains control column string

Cause: Reserved column name was specified in a column list or column type parameter.

Action: Control columns are selected with separate parameters. If you did not want a control column, then change the name of the specified column so that it does not conflict with a reserved column name.

ORA-31416: invalid SOURCE_COLMAP value

ORA-31416: invalid SOURCE_COLMAP value

Cause: A source_colmap value of y was specified for an asynchronous change table.

Action: Specify a source_colmap parameter value of n and call the procedure again.

ORA-31415: change set string does not exist

ORA-31415: change set string does not exist

Cause: Specified change set does not exist or the user does not have access to the publications in that change set. The name specified did not match the name of any existing change set. Certain privileges are required to access the publications within that change set.

Action: Check the name and call the procedure again, with the name of an existing change set. Contact the publisher or database administrator if user privileges are required to access the publications in the change set.

ORA-31414: error(s) occurred during change table advance

ORA-31414: error(s) occurred during change table advance

Cause: One or more errors occurred during the advance operation.

Action: Check the log file(s) for a more detailed report of the underlying errors.

ORA-31413: change set string is currently being advanced

ORA-31413: change set string is currently being advanced

Cause: An advance operation is in progress for this change set and we only allow one at a time.

Action: Since the change set is currently being advanced, the best action is to wait for it to finish advancing. Only one caller at a time can advance the change set. Check for the cause of long running advance operations.

ORA-31412: change set string is disabled and cannot be advanced

ORA-31412: change set string is disabled and cannot be advanced

Cause: The specified change set is disabled. The change set needs to be enabled for the operation to succeed.

Action: Determine why the change set is disabled and correct this condition. Alter the change set specifying y for advance_enable then retry the operation.

ORA-31411: change set string is referenced by a change table

ORA-31411: change set string is referenced by a change table

Cause: The operation cannot be performed because the change set contains one or more change tables.

Action: You will need to drop the change table(s) first, then repeat the operation

ORA-31410: change set string is not an existing change set

ORA-31410: change set string is not an existing change set

Cause: Could not find an existing change set by this name.

Action: Check the spelling of the change set name. Call the procedure again, passing the correct change set name.

ORA-31409: one or more values for input parameters are incorrect

ORA-31409: one or more values for input parameters are incorrect

Cause: One or more of the inputs to the procedure had invalid values.

Action: Identify the bad parameter(s) and supply correct values to the procedure.

ORA-31408: invalid value specified for begin_scn or end_scn

ORA-31408: invalid value specified for begin_scn or end_scn

Cause: The begin_scn was not greater than zero. The end_scn was less than zero. The end_scn was less than the begin_scn.

Action: Check the values of both begin_scn and end_scn. Correct them to make sure that they form a legal SCN range. An end_scn value of zero indicates an infinite scn range.

ORA-31407: end_date must be greater than the begin_date

ORA-31407: end_date must be greater than the begin_date

Cause: The end data of the change set is earlier than the begin date. The end date must always be later in time than the begin date, so that the duration between the begin and end dates is a positive amount of time.

Action: Change the begin date and or or the end date, so that the end date is later than the begin date.

ORA-31406: change source string is referenced by a change set

ORA-31406: change source string is referenced by a change set

Cause: The operation cannot complete because this change source is referenced by one or more change sets.

Action: Drop the change sets first, then re-issue the command. May have to drop some change tables before the change sets are dropped.

ORA-31405: cannot make changes while change set string is advancing

ORA-31405: cannot make changes while change set string is advancing

Cause: The change set is currently advancing. Change sources related to an advancing change set cannot be altered. Change tables related to the advancing change set cannot be created, altered or dropped. Some or all the parameters of the change set cannot be altered while the set is advancing.

Action: Wait until the change set has finished advancing, then reissue the command. If altering the change set, only the advance_enable parameter can be altered during an advance.

ORA-31404: all input parameters are null

ORA-31404: all input parameters are null

Cause: All input parameters are null. At least one property must be altered.

Action: Call the procedure again, making sure that all the required parameters have been specified. Ensure that at least one parameter is not null. Refer to user documentation for the correct way of calling this procedure.

ORA-31403: change table string already contains a column string

ORA-31403: change table string already contains a column string

Cause: Issued ALTER_CHANGE_TABLE with an add operation but a column by this name already exists in the specified table.

Action: Check the names and call the procedure again.

ORA-31402: unrecognized parameter string

ORA-31402: unrecognized parameter string

Cause: Unrecognized parameter was detected.

Action: Check for too many parameters in the call.

ORA-31401: change source string is not an existing change source

ORA-31401: change source string is not an existing change source

Cause: The caller did not use the name of an existing change source. The name given does not match the name of any existing change source.

Action: Check the spelling of the change source name. Choose an existing change source.

ORA-31399: Cannot contact LDAP server string at port number

ORA-31399: Cannot contact LDAP server string at port number

Cause: The LDAP server specified could not be contacted. This can happen if the server is down or inaccessible.

Action: Contact the administrator of the LDAP server or or or or or or or or or or or or or or or or or or or or or or or or or or End of DBMS_LDAP OiD messages