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
https://support.oracle.com/
http://www.oracle.com/
Category Archives: ORA Database Error Messages
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