Skip Headers
Oracle® Database Error Messages
10g Release 2 (10.2)

Part Number A14219-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
 

25 UDE-00001 to UDE-00053

UDE-00001: user requested cancel of current operation
Cause: User has requested a cancellation of current job.
Action: No action is needed.
UDE-00002: invalid username or password
Cause: An invalid username or password was specified.
Action: Retry with a valid username and password.
UDE-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.
UDE-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.
UDE-00005: unexpected End-Of-File encountered while reading input
Cause: Encountered an End-Of-File while reading the user input.
Action: If input to export is being redirected, check the file for errors.
UDE-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 Export internal bug.
UDE-00007: attempt to free unallocated memory
Cause: An attempt was made to free memory that was not allocated.
Action: Contact Oracle Worldwide Support NLS_DO_NOT_TRANSLATE [8,9]
UDE-00010: multiple job modes requested, string and string.
Cause: Multiple job modes were specified.
Action: Specify only one valid mode, then retry.
UDE-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.
UDE-00012: table mode exports only allow objects from one schema
Cause: Multiple schemas were selected for export.
Action: Retry export specifying only one schema.
UDE-00013: internal expdp error.
Cause: Fatal internal Data Pump client error.
Action: Contact Oracle Customer Support
UDE-00014: invalid value for parameter, "string".
Cause: Could not parse the specified parameter or parameter value.
Action: Refer to documentation for valid parameter values.
UDE-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.
UDE-00016: "string" parameter requires a value.
Cause: Parameter was specified without a value.
Action: Refer to documentation for correct parameter usage.
UDE-00017: Data Pump job is already executing.
Cause: Incorrect Data Pump job state for requested operation.
Action: Refer to documentation for correct usage.
UDE-00018: Export utility version can not be more recent than the Data Pump server.
Cause: The Export utility is at a higher version than the database version and is thereby incompatible.
Action: Use the same version of Export utility as the database.
UDE-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.
UDE-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 Export internal bug.
UDE-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.
Cause: Export was unable to set NLS_NUMERIC_CHARACTERS to ".,"
Action: Record the accompanying messages and report this as an Export internal error to Oracle customer support.
UDE-00052: incorrect Data Pump client for operation: string
Cause: Export client attempted to attach to import job.
Action: Use appropriate client when attaching to an existing job
UDE-00053: unrecognized client command "string"
Cause: Invalid interactive client command.
Action: Refer to documentation for valid client commands.