56 NID-00001 to NID-00604
- NID-00001: Illegal command line syntax - parse error = (number)
-
Cause: Illegal operand on command line.
- NID-00002: Parse error: string
-
Cause: An error was encountered while parsing the command line.
- NID-00010: Password:
-
Cause: Password was not specified in command line.
- NID-00100: Cannot open datafile "string"
-
Cause: The specified datafile could not be opened.
- NID-00101: LOGFILE (string) not accessible
-
Cause: The specified log file could not be opened.
- NID-00102: Garbled target string
-
Cause: The supplied connect string could not be parsed. The connect string does not have the correct format.
- NID-00103: Missing password in connect string "string"
-
Cause: Could not find the password in the supplied connect string. The connect string does not have the correct format.
- NID-00104: Need to specify TARGET connection parameter in command line
-
Cause: The mandatory parameter TARGET was not specified.
- NID-00105: Need to specify "LOGFILE=logfile" when using APPEND=YES option
-
Cause: The APPEND parameter was specified without a LOGFILE.
- NID-00106: LOGIN to target database failed with Oracle error:\nstring
-
Cause: An Oracle error was reported while attempting to log in to the target database.
- NID-00107: File I/O error on datafile "string" during string operation (number/string)
-
Cause: An operating system error was reported while performing the specified operation in the specified file.
- NID-00109: DBNAME string length number exceeds maximum length of number
-
Cause: The specified new database name exceeded the maximum size.
- NID-00110: Cannot use REVERT and specify a database name at the same time
-
Cause: Conflicting options were specified in the command line.
- NID-00111: Oracle error reported from target database while executing\nstring\nstring
-
Cause: An Oracle error was reported when executing an OCI operation.
- NID-00112: unsupported connection mode
-
Cause: A mode different than SYSDBA or SYSBACKUP was specified for the connection to the target.
- NID-00113: Error reading answer - aborting
-
Cause: Response caused an error.
- NID-00114: Must specify new database name when SETNAME is used
-
Cause: SETNAME=YES was specified but no DBNAME was provided.
- NID-00115: Database should be mounted
-
Cause: The database was not mounted.
- NID-00116: The Oracle Pluggable Database option specified is invalid.
-
Cause: The Oracle Pluggable Database option specified was not valid.
- NID-00120: Database should be mounted exclusively
-
Cause: The database was started in parallel mode. To change the DBID, the database must be mounted exclusively.
- NID-00121: Database should not be open
-
Cause: The database was open. To change the DBID, the database must be mounted exclusively.
- NID-00122: Database should have no offline immediate datafiles
-
Cause: The database has one or more datafiles that are in OFFLINE IMMEDIATE mode.
- NID-00123: Magic number for datafile "string" is incorrect
-
Cause: Block 0 header has an incorrect magic number for the specified datafile.
- 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.
- NID-00125: Database should have no disabled datafiles
-
Cause: The database has one or more datafiles that are disabled.
- NID-00126: Database should have no datafiles in unknown state
-
Cause: The database has one or more datafiles that are in an unknown state.
- 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.
- 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.
- 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.
- NID-00130: Mismatched CHECKPOINT_CHANGE# in datafile "string", expecting string, found string
-
Cause: The datafile header does not match information in the control file.
- NID-00131: Control file is not current
-
Cause: A non-current control file is currently mounted.
- 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.
- NID-00133: Database should have only consistent datafiles
-
Cause: The database has one or more datafiles that are marked FUZZY in the control file.
- NID-00134: Datafile "string" is not consistent
-
Cause: The datafile is marked as fuzzy in its header.
- NID-00135: There are number active threads
-
Cause: There are active threads in the database. The most likely cause is that the database crashed the last time it was shut down.
- NID-00137: All datafiles that are not dropped should be readable
-
Cause: The database had one or more files that could not be read.
- NID-00138: Block verification failed for datafile string (number)
-
Cause: Block header checksum yields a nonzero value for the specified datafile.
- 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.
- 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.
- 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.
- 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.
- NID-00143: Mismatched controlfile string
-
Cause: A controlfile did not have the correct status.
- 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.
- NID-00145: nls subsystem initialization failure for product=string, facility=string
-
Cause: The NLS product/facility error message file could not be located or properly initialized.
- NID-00300: Connected to database string (DBID=number)
-
Cause: Informational message.
- NID-00301: Datafile string - dbid changed, wrote new name
-
Cause: Informational message.
- NID-00302: Datafile string - dbid changed
-
Cause: Informational message.
- NID-00303: Datafile string - wrote new name
-
Cause: Informational message.
- NID-00304: Datafile string - reverted
-
Cause: Informational message.
- NID-00305: Datafile string - already changed
-
Cause: Informational message.
- NID-00306: Datafile string - no revert needed
-
Cause: Informational message.
- NID-00307: Control File string - dbid changed, wrote new name
-
Cause: Informational message.
- NID-00308: Control File string - dbid changed
-
Cause: Informational message.
- NID-00309: Control File string - wrote new name
-
Cause: Informational message.
- NID-00310: Control File string - reverted
-
Cause: Informational message.
- NID-00311: Control File string - modified
-
Cause: Informational message.
- NID-00312: Connected to server version string
-
Cause: Informational message.
- NID-00315: Operation already in progress, continuing
-
Cause: Informational message.
- NID-00320: Operation cancelled at user request
-
Cause: Informational message.
- NID-00321: Proceeding with operation
-
Cause: Informational message.
- NID-00330: The following datafiles are offline immediate:
-
Cause: Informational message.
- NID-00331: The following datafiles are disabled:
-
Cause: Informational message.
- NID-00332: The following datafiles are in unknown state:
-
Cause: Informational message.
- NID-00333: Cannot read the header of the following datafiles:
-
Cause: Informational message.
- NID-00334: The following datafiles are not checkpointed to string:
-
Cause: Informational message.
- NID-00335: The following datafiles are not consistent:
-
Cause: Informational message.
- NID-00336: The following datafiles are offline clean:
-
Cause: Informational message.
- NID-00337: The following datafiles are read-only:
-
Cause: Informational message.
- NID-00338: Control Files in database:
-
Cause: Informational message.
- NID-00350: string (number) string
-
Cause: Informational message.
- NID-00351: string (number)
-
Cause: Informational message.
- NID-00352: string (number), error: number
-
Cause: Informational message.
- NID-00353: string
-
Cause: Informational message.
- NID-00354: Instance shut down
-
Cause: Informational message.
- NID-00370: Change database ID of database string? (Y/[N]) =>
-
Cause: Informational message.
- NID-00371: Change database name of database string to string? (Y/[N]) =>
-
Cause: Informational message.
- NID-00372: Change database ID and database name string to string? (Y/[N]) =>
-
Cause: Informational message.
- NID-00373: Revert changes for database string (Y/[N]) =>
-
Cause: Informational message.
- NID-00390: These files must be writable by this utility.
-
Cause: Informational message.
- NID-00395: Reverting database name from string to string
-
Cause: Informational message.
- NID-00396: Reverting database ID from number to number
-
Cause: Informational message.
- NID-00397: Changing database name from string to string
-
Cause: Informational message.
- NID-00398: Changing database ID from number to number
-
Cause: Informational message.
- NID-00400: DBNEWID - Completed with errors.
-
Cause: Informational message.
- NID-00401: Must finish REVERT changes before attempting any database operation.
-
Cause: Informational message.
- NID-00402: Must finish change or REVERT changes before attempting any database operation.
-
Cause: Informational message.
- NID-00403: DBNEWID - Completed with validation errors.
-
Cause: Informational message.
- NID-00404: DBNEWID - Completed succesfully.
-
Cause: Informational message.
- NID-00405: Reversion of database name and database ID failed.
-
Cause: Informational message.
- NID-00406: Reversion of database name failed.
-
Cause: Informational message.
- NID-00407: Reversion of database ID failed.
-
Cause: Informational message.
- NID-00410: Reversion of database changes failed during validation - database is intact.
-
Cause: Informational message.
- NID-00415: Change of database name and database ID failed.
-
Cause: Informational message.
- NID-00416: Change of database name failed.
-
Cause: Informational message.
- NID-00417: Change of database ID failed.
-
Cause: Informational message.
- NID-00420: Change of database name and ID failed during validation - database is intact.
-
Cause: Informational message.
- NID-00421: Change of database name failed during validation - database is intact.
-
Cause: Informational message.
- NID-00422: Change of database ID failed during validation - database is intact.
-
Cause: Informational message.
- NID-00425: Database name restored to string.
-
Cause: Informational message.
- NID-00426: Database ID for database string restored to number.
-
Cause: Informational message.
- NID-00430: Database is ready to be open or shut down.
-
Cause: Informational message.
- NID-00431: DBNEWID - Reversion completed.
-
Cause: Informational message.
- NID-00435: Database name changed to string.
-
Cause: Informational message.
- NID-00436: Modify parameter file and generate a new password file before restarting.
-
Cause: Informational message.
- NID-00440: Database ID for database string changed to number.
-
Cause: Informational message.
- NID-00441: All previous backups and archived redo logs for this database are unusable.
-
Cause: Informational message.
- NID-00442: Database has been shutdown, open database with RESETLOGS option.
-
Cause: Informational message.
- NID-00450: Succesfully changed database name and ID.
-
Cause: Informational message.
- NID-00451: Succesfully changed database name.
-
Cause: Informational message.
- NID-00452: Succesfully changed database ID.
-
Cause: Informational message.
- NID-00480: Database is intact - database is ready to be open or shut down.
-
Cause: Informational message.
- NID-00481: DBNEWID - Cancelled.
-
Cause: Informational message.
- NID-00482: Database is not aware of previous backups and archived logs in Recovery Area.
-
Cause: Because the database id was changed, previous backups and archived redo logs in recovery area are not managed by this database.
- NID-00490: LOG being redirected to STDERR due to errors.
-
Cause: Could no write message to log file.
- NID-00500: Keyword Description (Default)
-
Cause: Informational message.
- NID-00501: ----------------------------------------------------
-
Cause: Informational message.
- NID-00502: TARGET Username/Password (NONE)
-
Cause: Informational message.
- NID-00503: DBNAME New database name (NONE)
-
Cause: Informational message.
- NID-00504: LOGFILE Output Log (NONE)
-
Cause: Informational message.
- NID-00505: REVERT Revert failed change NO
-
Cause: Informational message.
- NID-00506: SETNAME Set a new database name only NO
-
Cause: Informational message.
- NID-00507: APPEND Append to output log NO
-
Cause: Informational message.
- NID-00508: HELP Displays these messages NO
-
Cause: Informational message.
- NID-00600: Internal Error - [number] [number] [number] [number]
-
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
- NID-00601: Internal Error - [number] [string] [number] [number]
-
Cause: This is the generic internal error number for program exceptions. This indicates that the program has encountered an exceptional condition.
- NID-00602: Could not allocate number bytes for "string"
-
Cause: Memory allocation failed.
- NID-00603: No datafiles found in database
-
Cause: Controlfile has not datafiles recorded
- NID-00604: No control files found in database
-
Cause: Instance has no control files recorded