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