Go to main content
30/69
26
UDI-00001 to UDI-00053
UDI-00001: user requested cancel of current operation
Cause:
User has requested a cancellation of current job.
Action:
No action is needed.
UDI-00002: invalid username or password
Cause:
An invalid username or password was specified.
Action:
Retry with a valid username and password.
UDI-00003: all allowable logon attempts failed
Cause:
Attempts were repeatedly made to log on with an invalid username or password.
Action:
Shut down the utility, then restart and retry with a valid username and password.
UDI-00004: operation generated ORACLE error
number
Cause:
The operation unexpectedly produced the specified error. Refer to the description of that error for more information.
Action:
s.
UDI-00005: unexpected End-Of-File encountered while reading input.
Cause:
Encountered an End-Of-File while reading the user input.
Action:
If input to import is being redirected, check the file for errors.
UDI-00006: failed to allocate memory of size
number
Cause:
Unable to allocate the necessary memory.
Action:
Record the messages that follow and report this to Oracle Customer Support as an Import internal bug.
UDI-00007: attempt to free unallocated memory
Cause:
An attempt was made to free memory that was not allocated.
Action:
Contact Oracle Customer Support NLS_DO_NOT_TRANSLATE [8,9]
UDI-00010: multiple job modes requested,
string
and
string
.
Cause:
Invalid job mode was specified.
Action:
Specify only one valid mode, then retry.
UDI-00011: parameter
string
is incompatible with parameter
string
Cause:
An invalid combination of parameters was specified.
Action:
Refer to documentation for the set of valid modes, then retry.
UDI-00012: table mode imports only allow objects from one schema
Cause:
Multiple schemas were selected for import.
Action:
Retry import specifying only one schema.
UDI-00013: internal impdp error.
Cause:
Fatal internal Data Pump client error.
Action:
Contact Oracle Customer Support.
UDI-00014: invalid value for parameter, "
string
"
Cause:
Could not parse the specified parameter or parameter value.
Action:
Refer to documentation for valid parameter values.
UDI-00015: invalid context or job state for parameter, "
string
".
Cause:
Invalid job state or context for specified parameter.
Action:
Refer to documentation for correct parameter usage.
UDI-00016: "
string
" parameter requires a value.
Cause:
Parameter was specified without a value.
Action:
Refer to documentation for correct parameter usage.
UDI-00017: Data Pump job is already executing.
Cause:
Incorrect Data Pump job state for requested operation.
Action:
Refer to documentation for correct usage.
UDI-00018: Import utility version can not be more recent than the Data Pump server.
Cause:
The Import utility is at a higher version than the database version and is thereby incompatible.
Action:
Use the same version of Import utility as the database.
UDI-00019: "
string
" parameter list is too long.
Cause:
Requested parameter list exceeds 4000 character maximum.
Action:
Reduce the specified number of parameter values and rerun.
UDI-00050: unable to setup parameter processing.
Cause:
An unexpected error occurred during parameter manager initialization.
Action:
Record the messages that follow and report this to Oracle Customer Support as an Import internal bug.
UDI-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.
Cause:
Import was unable to set NLS_NUMERIC_CHARACTERS to ".,"
Action:
Record the accompanying messages and report this as an Import internal error to Oracle Customer Support.
UDI-00052: incorrect Data Pump client for operation:
string
Cause:
Import client attempted to attach to export job.
Action:
Use appropriate client when attaching to an existing job
UDI-00053: unrecognized client command "
string
"
Cause:
Invalid interactive client command.
Action:
Refer to documentation for valid client commands.
Scripting on this page enhances content navigation, but does not change the content in any way.