Thursday 21 June 2012

ORA-39167: Tablespace string was not found.

ORA-39167: Tablespace string was not found.

Cause: If exporting or importing over the network, the user specified a tablespace name that was not found in the source database. For importing from files, the user specified a tablespace name not found in the dump file set.

Action: Retry the operation using the correct tablespace name.

ORA-39166: Object string was not found.

ORA-39166: Object string was not found.

Cause: If exporting or importing over the network, either the user specified an object name that was not found in the source database or else the user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow them to access the object another in another schema. For importing from files, the user specified an object name not found in the dump file set.

Action: Retry the operation using the correct object name.

ORA-39165: Schema string was not found.

ORA-39165: Schema string was not found.

Cause: If exporting or importing over the network, either the user specified a schema name that was not found in the source database or else the user lacked the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role that would allow them to access another schema. For importing from files, the user specified a schema name not found in the dump file set.

Action: Retry the operation using the correct schema name.

ORA-39164: Partition string was not found.

ORA-39164: Partition string was not found.

Cause: If exporting or importing over the network, the user specified a partition name that was not found in the source database. For importing from files, the user specified a partition name not found in the dump file set.

Action: Retry the operation using the correct partition name.

ORA-39163: A sample size of string is invalid.

ORA-39163: A sample size of string is invalid.

Cause: An attempt was made to do data sampling on a table with a value outside of the range of 0 - 100.

Action: Retry the filtering using a sampling number greater than 0 and less than 100

ORA-39162: Transportable tablespace job require privileges

ORA-39162: Transportable tablespace job require privileges

Cause: User attempted to perform a transportable tablespace job without being having the proper EXP_FULL_DATABASE or IMP_FULL_DATABASE role.

Action: Retry the operation in a schema that has the required roles.

ORA-39161: Full database jobs require privileges

ORA-39161: Full database jobs require privileges

Cause: Either an attempt to perform a full database export without the EXP_ FULL_DATABASE role or an attempt to perform a full database import over a network link without the IMP_FULL_DATABASE role.

Action: Retry the operation in a schema that has the required roles.

ORA-39160: error on whats my name call

ORA-39160: error on whats my name call

Cause: Attempt to get the Data Pump process name failed.

Action: Refer to any following error messages for additional information. 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-39159: cannot call this function from a non-Data Pump process

ORA-39159: cannot call this function from a non-Data Pump process

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

Action: Refer to any other error messages for additional information. 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-39157: error appending extension to file string

ORA-39157: error appending extension to file string

Cause: Export or Import was unable to append the default extension to create the file name. The given file name could be too long or contain illegal characters. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39156: error parsing dump file name string

ORA-39156: error parsing dump file name string

Cause: Export was unable to parse the dump file name. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39155: error expanding dump file name string

ORA-39155: error expanding dump file name string

Cause: Export was unable to expand the directory object and dump file name into a full file name. Subsequent messages will detail the problems.

Action: Fix the problems outlined in the secondary messages.

ORA-39154: Objects from foreign schemas have been removed from import

ORA-39154: Objects from foreign schemas have been removed from import

Cause: An non-privileged user attempted to import objects into a schema other than their own.

Action: Either perform the import from a privileged schema or else remap all schemas that were exported into the username running the import.

ORA-39150: bad flashback time

ORA-39150: bad flashback time

Cause: A flashback time was specified for the Data Pump job which either could not be parsed or else could not be translated into a system change number (SCN). This typically occurs when

Action: Specify an explicit SCN for the desired flashback rather than a time.

ORA-39149: cannot link privileged user to non-privileged user

ORA-39149: cannot link privileged user to non-privileged user

Cause: A Data Pump job initiated be a user with EXPORT_FULL_ DATABASE or IMPORT_FULL_DATABASE roles specified a network link that did not correspond to a user with equivalent roles on the remote database.

Action: Specify a network link that maps users to identically privileged users in the remote database.

ORA-39148: unable to import data into pre-existing queue table string. Table_exists_ action of string being ignored for this table

ORA-39148: unable to import data into pre-existing queue table string. Table_exists_ action of string being ignored for this table

Cause: A Data Pump import detected that a queue table that was to be imported already exists. Importing data into pre-existing queue tables is not supported.

Action: If the data from the dump file is desired, then drop the queue table and perform the import again, or use the import parameter table_exists_ action=replace.

ORA-39147: cannot migrate Data Pump queue table ownership to this instance

ORA-39147: cannot migrate Data Pump queue table ownership to this instance

Cause: There are active Data Pump jobs running on another instance in a RAC. All concurrent, active Data Pump jobs must be run on the same instance.

Action: Start this job on the same instance where other active Data Pump jobs are running, or wait until they finish.

ORA-39146: schema string does not exist

ORA-39146: schema string does not exist

Cause: The specified schema was referenced as the source of a REMAP_SCHEMA parameter, but did not exist in the dump file (for

Action: Specify the correct name of the schema to be remapped.

ORA-39145: directory object parameter must be specified and non-null

ORA-39145: directory object parameter must be specified and non-null

Cause: No directory object was provided in either an DBMS_DATAPUMP.ADD_ FILE API call or to the directory parameter used by the Data Pump command line clients.

Action: Correct the directory object parameter and retry the operation.

ORA-39144: file name parameter must be specified and non-null

ORA-39144: file name parameter must be specified and non-null

Cause: No file name was provided in an DBMS_DATAPUMP.ADD_FILE API call.

Action: Correct the file name parameter and reissue the API request.

ORA-39143: dump file string may be an original export dump file

ORA-39143: dump file string may be an original export dump file

Cause: A dump file was specified for an import operation which appears to have been created using the original export utility. These dump files cannot be processed by the Data Pump import utility.

Action: Try using the original import utility to process this dump file.

ORA-39142: incompatible version number string in dump file string

ORA-39142: incompatible version number string in dump file string

Cause: A dump file was specified for an import operation whose version number is incompatible with the dump file version of the Data Pump product currently running on the system. Usually this message indicates that the dump file was produced by a newer version of the Data Pump export utility.

Action: Import this dump file using the Data Pump import utility with the same version as the export which created the file.

ORA-39141: dump file string is a duplicate of dump file string

ORA-39141: dump file string is a duplicate of dump file string

Cause: When a dump file set consists of multiple files, all files in the set must be specified for an import operation. One of the files provided to import was found to be a duplicate of another dump file in the set. This can occur if the files in the dump set were copied or renamed using operating system utilities and the same dump file was inadvertently copied more than once with different destination names.

Action: Remove the dump file indicated in the message and retry the import operation providing only the complete set of dump files created by a specific export job.

ORA-39140: dump file string belongs to job string

ORA-39140: dump file string belongs to job string

Cause: When a dump file set consists of multiple files, all files in the set must be specified for an import operation, and all files must have been produced by the same export job. One of the files provided does not belong to the original dump file set. For instance, it was created by a different export job than the other files.

Action: Remove the dump file indicated in the message and retry the import operation providing only the complete set of dump files created by a specific export job.

ORA-39139: Data Pump does not support XMLSchema objects. string will be skipped.

ORA-39139: Data Pump does not support XMLSchema objects. string will be skipped.

Cause: Object has XMLSchema-based columns, which are unsupported by Data Pump.

Action: Use the original exp and imp utilities to move this object.

ORA-39138: Insufficient privileges to load data not in your schema

ORA-39138: Insufficient privileges to load data not in your schema

Cause: An unprivileged user attempted to load data into a different schema.

Action: Use a privileged account if you must load data not in your schema

ORA-39137: cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata

ORA-39137: cannot specify a TABLE_EXISTS_ACTION of string for a job with no metadata

Cause: A job was defined with the TABLE_EXISTS_ACTION parameter set to REPLACE or SKIP, but without metadata. Without metadata, data could not be loaded for the requested table actions.

Action: Change the setting of the TABLE_EXISTS_ACTION parameter to APPEND or TRUNCATE or supply Metadata with the data.

ORA-39136: cannot specify an SCN on a transportable job

ORA-39136: cannot specify an SCN on a transportable job

Cause: A target SCN was specified for a table in a transportable job by the streams or logical standy components which was not the defaulted SCN for the table.

Action: This is an internal error. Please report it to Oracle support.

ORA-39134: Cannot include string tablespace as a Transportable Tablespace

ORA-39134: Cannot include string tablespace as a Transportable Tablespace

Cause: The user attempt to specify the SYSAUX or SYSTEM tablespace as a member of the transportable tablespace list in the current job. These tablespaces may not be transported between databases.

Action: Specify different tablespaces to be transported.

ORA-39133: object type string . string already exists with different typeid

ORA-39133: object type string . string already exists with different typeid

Cause: An object type in a transportable tablespace set already exists on the target system, but with a different typeid. The typeid could not be changed because the type is used by an existing table. Tables in the transportable tablespace set that use this object type cannot be read.

Action: Drop the object type from the target system and retry the operation.

ORA-39132: object type string . string already exists with different hashcode

ORA-39132: object type string . string already exists with different hashcode

Cause: An object type could not be created because there was already a type with the same name but a different hashcode on the target system. Tables in the transportable tablespace set that use this object type cannot be read.

Action: Drop the object type from the target system and retry the operation.

ORA-39130: Object type string not imported. Base object name conflicts with the master table

ORA-39130: Object type string not imported. Base object name conflicts with the master table

Cause: The object being imported from the remote instance is dependent on an object that has the same name as the master table running this Data Pump job.

Action: Rerun the Data Pump job with a nonconflicting name.

ORA-39129: Object type string not imported. Name conflicts with the master table

ORA-39129: Object type string not imported. Name conflicts with the master table

Cause: The table being imported from the remote instance has the same name as the master table running this Data Pump job.

Action: Rerun the Data Pump job with a nonconflicting name.

ORA-39128: unexpected DbmsJava error number from statement string

ORA-39128: unexpected DbmsJava error number from statement string

Cause: The error was returned from a call to a DbmsJava procedure.

Action: Record the accompanying messages and report this as a Data Pump internal error to customer support.

ORA-39127: unexpected error from call to string string

ORA-39127: unexpected error from call to string string

Cause: The exception was raised by the function invocation, a procedural action extension of export.

Action: Record the accompanying messages and report this as a Data Pump internal error to customer support.

ORA-39126: Worker unexpected fatal error in string (string( string

ORA-39126: Worker unexpected fatal error in string (string( string

Cause: An unhandled exception was detected internally within the worker process for the Data Pump job. This is an internal error. Additional information may be supplied.

Action: If problem persists, contact Oracle Customer Support.

ORA-39125: Worker unexpected fatal error in string while calling string (string(

ORA-39125: Worker unexpected fatal error in string while calling string (string(

Cause: An unhandled exception was detected internally within the worker process for the Data Pump job while calling the specified external routine. This is an internal error. Additional information may be supplied.

Action: If problem persists, contact Oracle Customer Support.

ORA-39124: dump file name string contains an invalid substitution variable

ORA-39124: dump file name string contains an invalid substitution variable

Cause: The substitution variable % must be followed by % , u , or U .

Action: Correct the substitution variable in the dump file name and re-enter the command.

ORA-39123: Data Pump transportable tablespace job aborted string

ORA-39123: Data Pump transportable tablespace job aborted string

Cause: A DBMS_PLUGTS procedure failed and the Data Pump operation could not continue so it was aborted. The DBMS_PLUGTS failure listed describes the original error.

Action: Look at the DBMS_PLUGTS error to determine actual cause.

ORA-39122: Unprivileged users may not perform string remappings.

ORA-39122: Unprivileged users may not perform string remappings.

Cause: A user attempted to remap objects during an import but lacked the IMPORT_FULL_DATABASE privilege.

Action: Retry the job from a schema that owns the IMPORT_FULL_DATABASE privilege.

ORA-39121: Table string can t be replaced, data will be skipped. Failing error is: string

ORA-39121: Table string can t be replaced, data will be skipped. Failing error is: string

Cause: Table data was about to be loaded into a table that already existed and the table_exists_action parameter is replace, but the table could not be dropped.

Action: Determine actual cause by looking at base error.

ORA-39120: Table string can t be truncated, data will be skipped. Failing error is: string

ORA-39120: Table string can t be truncated, data will be skipped. Failing error is: string

Cause: Table data was about to be loaded into a table that already existed and the table_exists_action parameter is truncate, but the table could not be truncated.

Action: Determine actual cause by looking at base error.

ORA-39119: worker process interrupt for delete worker processes call by master process

ORA-39119: worker process interrupt for delete worker processes call by master process

Cause: The master process that created this worker process called delete worker processes to abort the current operation.

Action: No action is necessary. This is an informational error message.

ORA-39115: %s is not supported over a network link

ORA-39115: %s is not supported over a network link

Cause: An attempt was made to use an option that is not supported over network links such as the PARTITION_LIST filter.

Action: Do not attempt to use Data Pump features on network jobs if they are not compatible with jobs over the network.

ORA-39114: Dump files are not supported for network jobs.

ORA-39114: Dump files are not supported for network jobs.

Cause: An attempt was made to add a dumpfile to an Import job that is using a network link to the source database.

Action: Do not specify a dumpfile for jobs that do not require dumpfiles.

ORA-39113: Unable to determine database version

ORA-39113: Unable to determine database version

Cause: The Data Pump was unable to determine the compatibility level and version of the current database using SYS.DBMS_UTILITY.DB_VERSION.

Action: Make sure access to the DBMS_UTILITY package is granted to you. If this is a network job, be sure that access to the DBMS_UTILITY package is granted to you on the remote instance.

ORA-39112: Dependent object type string skipped, base object type string creation failed

ORA-39112: Dependent object type string skipped, base object type string creation failed

Cause: During a Data Pump import job, a dependent object is being skipped because its base object creation failed.

Action: If the object from the dump file is wanted, drop the base and dependent objects and try to import again using desired filters

ORA-39111: Dependent object type string skipped, base object type string already exists

ORA-39111: Dependent object type string skipped, base object type string already exists

Cause: During a Data Pump import job, a dependent object is being skipped because its base object already existed.

Action: If the object from the dump file is wanted, drop the base and dependent objects and try to import again using desired filters.

ORA-39110: error deleting worker processes

ORA-39110: error deleting worker processes

Cause: An attempt to delete the 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-39109: Unprivileged users may not operate upon other users schemas

ORA-39109: Unprivileged users may not operate upon other users schemas

Cause: An unprivileged user attempted to reference another user s schema during a Data Pump operation. Because of this, no schemas were were selected for the job.

Action: Retry the operation under a username owning the schema.

ORA-39108: Worker process string violated startup protocol. Worker error:

ORA-39108: Worker process string violated startup protocol. Worker error:

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. Also, check the trace log for the failed process, if one was created, to see if there is any additional 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-39107: Master process string violated startup protocol. Master error:

ORA-39107: Master process string violated startup protocol. Master error:

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. Also, check the trace log for the failed process, if one was created, to see if there is any additional 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-39106: Worker process string failed during startup. Worker error:

ORA-39106: Worker process string failed during startup. Worker error:

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

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional 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-39105: Master process string failed during startup. Master error:

ORA-39105: Master process string failed during startup. Master error:

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

Action: Refer to any following error messages for possible actions. Also, check the trace log for the failed process, if one was created, to see if there is any additional 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-39104: cannot call this function from a SQL parallel query slave process

ORA-39104: cannot call this function from a SQL parallel query slave process

Cause: Called a Data Pump process model function from a process which is a SQL parallel query slave process

Action: A SQL parallel query slave process cannot create a Data Pump master process. This is not supported. If this error occurs from a Data Pump client (for example, expdp or impdp), contact Oracle Customer Support and report the error.

ORA-39103: Timeout before worker process string finished initialization. Worker error:

ORA-39103: Timeout before worker process string finished initialization. Worker error:

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. Also, check the trace log for the failed process, if one was created, to see if there is any additional 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-39102: Timeout before master process string finished initialization. Master error:

ORA-39102: Timeout before master process string finished initialization. Master error:

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. Also, check the trace log for the failed process, if one was created, to see if there is any additional 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-39099: cannot create index for string on master table string

ORA-39099: cannot create index for string on master table string

Cause: One or more indexes couldn t be created on the master table. subsequent error messages describe the failure.

Action: Correct the condition that is preventing the indexes from being created.

ORA-39098: Worker process received data objects while loading metadata. Invalid process order range is string..string

ORA-39098: Worker process received data objects while loading metadata. Invalid process order range is string..string

Cause: This is an internal error. Messages will detail the problem.

Action: If problem persists, contact Oracle Customer Support.

ORA-39097: Data Pump job encountered unexpected error string

ORA-39097: Data Pump job encountered unexpected error string

Cause: An unexpected, potentially non-fatal error occurred while processing a Data Pump job.

Action: Contact Oracle Customer Support.