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.