Oracle Errors DBNEWID Messages (NID)

NID-00100 Cannot open datafile "string"

Cause: The specified datafile could not be opened.

Action: Ensure that the specified datafile exists and is writable.

NID-00101 LOGFILE (string) not accessible

Cause: The specified log file could not be opened.

Action: Specify a log file that is writable.

NID-00102 Garbled target string

Cause: The supplied connect string could not be parsed. The connect string does not have the correct format.

Action: Refer to Oracle9i Database Concepts.

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.

Action: Refer to Oracle9i Database Concepts.

NID-00104 Need to specify TARGET connection parameter in command line

Cause: The mandatory parameter TARGET was not specified.

Action: Specify TARGET=username/password when invoking this utility.

NID-00105 Need to specify "LOGFILE=<logfile>" when using APPEND=YES option

Cause: The APPEND parameter was specified without LOGFILE.

Action: Specify APPEND=YES only when LOGFILE is also specified.

NID-00106 LOGIN to target database failed with Oracle error: string

Cause: An Oracle error was reported while attempting to log in to the target database.

Action: Follow the actions for the specified Oracle error.

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.

Action: Verify the datafile and check for operating system errors.

NID-00109 DBNAME string length number exceeds maximum length of number

Cause: The specified new database name exceeded the maximum size.

Action: Specify a shorter, valid name.

NID-00110 Cannot use REVERT and specify a database name at the same time

Cause: Conflicting options were specified on the command line.

Action: Choose only one of the options.

NID-00111 Oracle error reported from target database while executing string string

Cause: An Oracle error was reported when executing an OCI operation.

Action: Follow the actions for the specified Oracle error.

NID-00113 Error reading answer - aborting

Cause: Response caused an error.

Action: Retry the operation.

NID-00114 Must specify new database name when SETNAME is used

Cause: SETNAME=YES was specified but no DBNAME was provided.

Action: Specify DBNAME or remove the SETNAME=YES option.

NID-00115 Database should be mounted

Cause: The database was not mounted.

Action: Mount the database.

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.

Action: Shut down the database and start it in exclusive mode.

NID-00121 Database should not be open

Cause: The database was open. To change the DBID, the database must be mounted exclusively.

Action: Shut down the database and mount it in exclusive mode.

NID-00122 Database should have no offline immediate datafiles

Cause: The database has one or more datafiles that are in OFFLINE IMMEDIATE mode.

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

NID-00123 Magic number for datafile "string" is incorrect

Cause: Block 0 header has an incorrect magic number for the specified datafile.

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

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.

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-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-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-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-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-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-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-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-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-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-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.

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-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-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-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-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-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-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-00143 Mismatched controlfile string

Cause: A controlfile did not have the correct status.

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

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-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.

Action: Check that the error message directory and files have been properly installed.