NID-00144: New name for database string is the same as current name string

NID-00144: New name for database string is the same as current name string

Cause: The specified name is the same as the current name of the database.

Action: Specify a different name or do not use the DBNAME option.

NID-00143: Mismatched controlfile string

NID-00143: Mismatched controlfile string

Cause: A controlfile did not have the correct status.

Action: Shutdown the database, remove the mismatched controlfile, mount the database, and retry the operation.

NID-00142: Only changing database name, previous attempt changed dbid to number

NID-00142: Only changing database name, previous attempt changed dbid to number

Cause: This is a continuation of a failed attempt. However, in the failed attempt, the database id was also being changed.

Action: Retry the command removing SETNAME=YES.

NID-00141: No database name specified, previous attempt used string

NID-00141: No database name specified, previous attempt used string

Cause: This is a continuation of a failed attempt. However, in the failed attempt, a database name was provided.

Action: Retry the command using the original database name.

NID-00140: Specified database name string does not match previous name used string

NID-00140: Specified database name string does not match previous name used string

Cause: This is a continuation of a failed attempt. However in the failed attempt, the database name is different than the one used in the last attempt.

Action: Retry the command using the original database name.

NID-00139: Mismatched dbname for datafile string, expected string, found string

NID-00139: Mismatched dbname for datafile string, expected string, found string

Cause: The dbname of the datafile does not match the old dbname or the new dbname.

Action: Verify that this datafile belongs to the database. You may need to restore a backup of the datafile.

NID-00138: Block verification failed for datafile string (number)

NID-00138: Block verification failed for datafile string (number)

Cause: Block header checksum yields a nonzero value for the specified datafile.

Action: Verify that the datafile is correct and retry the operation.

NID-00137: All datafiles that are not dropped should be readable

NID-00137: All datafiles that are not dropped should be readable

Cause: The database had one or more files that could not be read.

Action: Restore the missing files and retry the operation.

NID-00135: There are number active threads

NID-00135: There are number active threads

Cause: is that the database crashed the last time it was shut down.

Action: Ensure that all threads are closed before retrying the operation. Start and open the database to perform crash recovery, then shut down with the NORMAL or IMMEDIATE options to close it cleanly. Finally, try running the utility again.

NID-00134: Datafile string is not consistent

NID-00134: Datafile string is not consistent

Cause: The datafile is marked as fuzzy in its header.

Action: Restart the database and shut down cleanly, then retry the operation.

NID-00133: Database should have only consistent datafiles

NID-00133: Database should have only consistent datafiles

Cause: The database has one or more datafiles that are marked FUZZY in the control file.

Action: Restart the database and shut down consistently, then retry the operation.

NID-00132: CHECKPOINT_CHANGE# in datafile string : string in the future of controlfile: string

NID-00132: CHECKPOINT_CHANGE# in datafile string : string in the future of controlfile: string

Cause: The checkpoint in the datafile header is ahead of the checkpoint in the control file.

Action: Make the database consistent and retry.

NID-00131: Control file is not current

NID-00131: Control file is not current

Cause: A non-current control file is currently mounted.

Action: Perform necessary actions to make the control file current and retry.

NID-00130: Mismatched CHECKPOINT_CHANGE# in datafile string , expecting string, found string

NID-00130: Mismatched CHECKPOINT_CHANGE# in datafile string , expecting string, found string

Cause: The datafile header does not match information in the control file.

Action: Revert the change, open the database, and verify that all datafiles are consistent. Then, shut down the database and retry the operation.

NID-00129: Invalid DBID for datafile string , expecting number, found number

NID-00129: Invalid DBID for datafile string , expecting number, found number

Cause: A datafile header shows a different DBID from the rest of the database files.

Action: Ensure that the file belongs to this database.

NID-00128: Cannot revert change of database, change not in progress

NID-00128: Cannot revert change of database, change not in progress

Cause: The REVERT option was used, but the control file does not show that a change of DBID was in progress.

Action: Do not use the REVERT option, or possibly restore the control file that was in place when the utility was started.

NID-00127: All online files in the database must have the same checkpoint SCN

NID-00127: All online files in the database must have the same checkpoint SCN

Cause: The database has one or more datafiles that have a checkpoint SCN that does not match the database checkpoint SCN.

Action: Restart the database and shut it down cleanly, then retry the operation.

NID-00126: Database should have no datafiles in unknown state

NID-00126: Database should have no datafiles in unknown state

Cause: The database has one or more datafiles that are in an unknown state.

Action: Drop the datafiles or recover them and bring them online.

NID-00125: Database should have no disabled datafiles

NID-00125: Database should have no disabled datafiles

Cause: The database has one or more datafiles that are disabled.

Action: Drop the datafiles or recover them and bring them online.

NID-00124: Mismatched dbid for datafile string, expected number, found number

NID-00124: Mismatched dbid for datafile string, expected number, found number

Cause: The dbid of the datafile does not match the old DBID or the new DBID.

Action: Verify that this datafile belongs to the database. You may need to restore a backup of the datafile.

UDI-00007: attempt to free unallocated memory

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-00006: failed to allocate memory of size number

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-00005: unexpected End-Of-File encountered while reading input.

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-00004: operation generated ORACLE error number

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-00003: all allowable logon attempts failed

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-00002: invalid username or password

UDI-00002: invalid username or password

Cause: An invalid username or password was specified.

Action: Retry with a valid username and password.

UDI-00001: user requested cancel of current operation

UDI-00001: user requested cancel of current operation

Cause: User has requested a cancellation of current job.

Action: No action is needed.

UDE-00053: unrecognized client command string

UDE-00053: unrecognized client command string

Cause: Invalid interactive client command.

Action: Refer to documentation for valid client commands.

UDE-00052: incorrect Data Pump client for operation: string

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-00051: unable to set NLS_NUMERIC_CHARACTERS to required defaults.

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-00050: Unable to setup parameter processing.

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-00019: string parameter list is too long.

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-00018: Export utility version can not be more recent than the Data Pump server.

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-00017: Data Pump job is already executing.

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-00016: string parameter requires a value.

UDE-00016: string parameter requires a value.

Cause: Parameter was specified without a value.

Action: Refer to documentation for correct parameter usage.

UDE-00015: invalid context or job state for parameter, string .

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-00014: invalid value for parameter, string .

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-00013: internal expdp error.

UDE-00013: internal expdp error.

Cause: Fatal internal Data Pump client error.

Action: Contact Oracle Customer Support

UDE-00012: table mode exports only allow objects from one schema

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-00011: parameter string is incompatible with parameter string

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-00010: multiple job modes requested, string and string.

UDE-00010: multiple job modes requested, string and string.

Cause: Multiple job modes were specified.

Action: Specify only one valid mode, then retry.

UDE-00007: attempt to free unallocated memory

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-00006: failed to allocate memory of size number

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-00005: unexpected End-Of-File encountered while reading input

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-00004: operation generated ORACLE error number

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-00003: all allowable logon attempts failed

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-00002: invalid username or password

UDE-00002: invalid username or password

Cause: An invalid username or password was specified.

Action: Retry with a valid username and password.

UDE-00001: user requested cancel of current operation

UDE-00001: user requested cancel of current operation

Cause: User has requested a cancellation of current job.

Action: No action is needed.

KUP-11012: file string in string already exists

KUP-11012: file string in string already exists

Cause: The specified file could not be used for this unload because that would mean overwriting an existing file.

Action: Specify a file that does not currently exist.

KUP-11011: file string is not valid for this load operation

KUP-11011: file string is not valid for this load operation

Cause: The specified file could not be used for this load because the internal header, file version number, and or or table metadata of this file were not consistent with those of the first file listed in the LOCATION clause.

Action: Verify all the files listed in the LOCATION clause are from the same unload operation.

KUP-11010: unable to open at least one dump file for load

KUP-11010: unable to open at least one dump file for load

Cause: None of the files listed in the LOCATION clause could be opened for load.

Action: A load operation requires that at least one file could be opened. Check that the unload operation succeeded. Check that the path and filenames to the dump files are correct.

KUP-11009: data for row: string

KUP-11009: data for row: string

Cause: A conversion error occurred while loading data into a table. The message shows values for the field in the row that had the conversion error.

Action: None. This is only an informational message.

KUP-11008: conversion error loading table string.string partition string

KUP-11008: conversion error loading table string.string partition string

Cause: A row could not be loaded into the table because there was a conversion error for one or more columns in a row.

Action: See the message that follows for more information about the row that could not be loaded. To avoid this error, make sure the definition of the table being loaded matches the definition of the table being unloaded.

KUP-04024: field end is before field start

KUP-04024: field end is before field start

Cause: The end of the field comes after the start of the field. This can happen if the field is defined with a relative start position and an absolute end position.

Action: Verify that the definition of the layout of fields in the data file is correct.

KUP-04023: field start is after end of record

KUP-04023: field start is after end of record

Cause: This can happen when specifying either absolute or relative positioning for a field.

Action: Verify that the definition of the layout of fields in the data file is correct. If it is valid for fields at the end of the record to be missing, use the MISSING FIELD VALUES ARE NULL clause in the access parameters.

KUP-04022: field start is before start of record

KUP-04022: field start is before start of record

Cause: The position of the start of a field is before the start of a record. This can occur if a negative number is used to indicate the relative start of a field.

Action: Verify that the definition of the layout of fields in the data file is correct.

KUP-04021: field formatting error for field string

KUP-04021: field formatting error for field string

Cause: There was an error trying to find the contents of the specified field in a record.

Action: This message should be followed by another message containing more specific information about the cause of the error.

KUP-04020: found record longer than buffer size supported, number, in string

KUP-04020: found record longer than buffer size supported, number, in string

Cause: a record in the data source was longer than the maximum data size supported. The number reported is the maximum supported size of a record.

Action: none

KUP-04019: illegal length found for VAR record in file string

KUP-04019: illegal length found for VAR record in file string

Cause: A record in a VAR file has an length field with either no numeric characters in it or with non numeric characters in it.

Action: Verify the records in the file have the correct length specified for them.

KUP-04018: partial record at end of file string

KUP-04018: partial record at end of file string

Cause: An incomplete record was found at the end of the file.

Action: Verify the file is not corrupt or missing data.