Release 2 (9.2)
Part Number A96525-01
 Home |
 Book List |
 Contents |
 Index |
 Master Index |
 Feedback |
| Oracle9i Database Error Messages Release 2 (9.2) Part Number A96525-01 |
|
This chapter lists messages generated by the DBNEWID utility. For more information about this utility, refer to Oracle9i Database Utilities.
Cause: The specified datafile could not be opened.
Action: Ensure that the specified datafile exists and is writable.
Cause: The specified log file could not be opened.
Action: Specify a log file that is writable.
Cause: The supplied connect string could not be parsed. The connect string does not have the correct format.
Action: Refer to Oracle9i Database Concepts.
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.
Cause: The mandatory parameter TARGET was not specified.
Action: Specify TARGET=username/password when invoking this utility.
Cause: The APPEND parameter was specified without LOGFILE.
Action: Specify APPEND=YES only when LOGFILE is also specified.
Cause: An Oracle error was reported while attempting to log in to the target database.
Action: Follow the actions for the specified Oracle error.
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.
Cause: The specified new database name exceeded the maximum size.
Action: Specify a shorter, valid name.
Cause: Conflicting options were specified on the command line.
Action: Choose only one of the options.
Cause: An Oracle error was reported when executing an OCI operation.
Action: Follow the actions for the specified Oracle error.
Cause: Response caused an error.
Action: Retry the operation.
Cause: SETNAME=YES was specified but no DBNAME was provided.
Action: Specify DBNAME or remove the SETNAME=YES option.
Cause: The database was not mounted.
Action: Mount the database.
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.
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.
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.
Cause: Block 0 header has an incorrect magic number for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
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.
Cause: The database has one or more datafiles that are disabled.
Action: Drop the datafiles or recover them and bring them online.
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.
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.
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.
Cause: A datafile header shows a different DBID from the rest of the database files.
Action: Ensure that the file belongs to this database.
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.
Cause: A non-current control file is currently mounted.
Action: Perform necessary actions to make the control file current and retry.
Cause: The checkpoint in the datafile header is ahead of the checkpoint in the control file.
Action: Make the database consistent and retry.
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.
Cause: The datafile is marked as fuzzy in its header.
Action: Restart the database and shut down cleanly, then retry the operation.
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.
Cause: The database had one or more files that could not be read.
Action: Restore the missing files and retry the operation.
Cause: Block header checksum yields a nonzero value for the specified datafile.
Action: Verify that the datafile is correct and retry the operation.
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.
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.
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.
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.
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.
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.
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.
|
 Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
