Oracle Database Errors or Warnings from Error ORA-39217 to ORA-39230


ORA-39217: object type “string”.”string” typeid mismatch
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 or a dependent type is used by an existing table. Tables in the transportable tablespace set that use this object be created.
Action: Drop the object type and dependent objects from the target system if possible and retry the operation.
ORA-39218: type check on object type “string”.”string” failed
Cause: The type check on a type failed. Therefore, the table create for the table which uses the type also fails.
Action: Refer to any following error messages for additional information. Correct the error, if possible, and try the action again.
ORA-39219: directory object name is too long
Cause: The directory object name provided to the Data Pump Job was invalid because its length was greater than 30 characters.
Action: Retry the operation with a valid directory object name.

ORA-39220: file name is too long
Cause: The file name provided to the Data Pump Job was invalid because its length was greater than 4000 characters.
Action: Retry the operation with a valid file name.
ORA-39221: Specifying data filters is invalid when dumpfiles do not contain table data.
Cause: A data filter was supplied for an import job, but the dumpfile does not contain any table data. The export command created a dumpfile with metadata only. No table data was included. From the command line, data filters can be specified by the CONTENT, SAMPLE and QUERY parameters.
Action: Do not restrict data handling on jobs that cannot support data filtering.
ORA-39222: Unable to create global temporary master table string
Cause: Data Pump tried to create a global temporary master table but could not. The errors that follow describe why the table could not be created.
Action: Examine and fix the problems described in the additional errors.

ORA-39223: Internal Data Pump error. Master table information for version string not found.
Cause: An unexpected error occurred while processing the job. The data in an internal table could not be found.
Action: Contact Oracle Support Services.
ORA-39224: string row(s) were rejected with the following error: string
Cause: These rows were not loaded due to constraint or index violations.
Action: Retry the operation when row data is fixed.
ORA-39228: Unable to construct a unique departitioned object name for string string.string:string when defaulted.
Cause: All (sub)partitions in the job were to be created as individual objects and the renaming was defaulted. The job will attempt to create unique object names, but the name creation algorithm was unable to find a unique object name for the specified (sub)partition.
Action: Specify a rename_table transform to use or delete some of the existing objects causing the name conflicts.
ORA-39230: Service name string is not available
Cause: The specified resource service name for the Data Pump job
Action: Pick a service name that the user is authorized to use.

Above are list of Oracle Database Errors or Warnings from Error ORA-39217 to ORA-39230 received while performing certain operation against Oracle Database or related products.

What are atOracle Database Error Messages?

Oracle Error Messages may be returned while using products which are part of Oracle Database. Each Oracle Dabase Error or Warning Message mentioned above contains the Warning or Error Message Statement, a short explanation of the probable causes of the Error message, and a recommended action.

Hope this was helpful.

SQLServerF1 Team
Information about Oracle Database Error Messages or Warning Messages on Windows and Linux Operating Systems.


Leave a Reply

Your email address will not be published. Required fields are marked *