Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
Cause: The control file cannot be created, usually because of insufficient disk storage or filename conflicts.
Action: Check that there is sufficient disk space and no conflicts in filenames and try to create the control file again.
Cause: The control file was created by a different version of Oracle.
Action: Either
Cause: This message reports the name of the file involved in other messages.
Action: See the associated messages for a description of the problem.
Cause: The mount ID in the control file is not the same as the mount ID in the control file used by the first instance to mount this database. The control files are for the same database but are not the same files. The most likely cause is that one instance is using a backup of the control file. If you want to use a backed up control file, you can recover using the USING BACKUP CONTROLFILE option.
Action: Check that all instances are using the correct version of the control file.
Cause: A disk read-failure occurred while attempting to read the specified control file. The block location of the failure is given.
Action: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If the disk is online, then look for operating system reasons for Oracle's inability to read the disk or control file. Refer to the Oracle8 Server Administrator's Guide for information about recovering from the loss of a control file. See also your operating system-specific Oracle documentation.
Cause: The system could not find a control file of the specified name and size.
Action: Either
Cause: A disk write-failure occurred while attempting to write to the specified control file. The block location of the failure is given.
Action: Check that the disk is online. If it is not, bring it online and shut down and restart Oracle. If the disk is online, then look for operating system reasons for Oracle's inability to write to the disk or control file. See the Oracle8 Server Administrator's Guide for information on recovering from the loss of a control file. See also your operating system-specific Oracle documentation.
Cause: The database ID in the control file is not the same as the database ID in the control file used by the first instance to mount this database. The most likely cause is either that one of the mounts used the wrong control file or there are two databases with the same name.
Action: Check that the control file is for the correct database and not an old version. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control filename listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new filename in the initialization parameter file.
Cause: An attempt was made to use more control files than Oracle supports. The limit is given in the message.
Action: Shut down Oracle, reduce the number of control filenames specified in the CONTROL_FILES parameter in the initialization parameter file, and restart Oracle. Delete unused files.
Cause: A block size larger than that allowed by the operating system was specified.
Action: Reduce the block size to the amount specified in the message and try again.
Cause: The system was unable to open a control file.
Action: Check that the control file exists, that the storage device is online, and that the file is not locked by some other program and try again. Also, check to see that the operating system limit on the number of open files per process has not been exceeded.
When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the parameter from the initialization parameter file referencing the control filename indicated in the message and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file using a new filename in the initialization parameter file.
Cause: The specified control file is from another database.
Action: Locate and specify the correct control file for this database, then retry the operation. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control filename listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file, create another copy of the control file, and include the new filename in the initialization parameter file.
Cause: The specified block size is too small. Additional space is needed for system overhead.
Action: Specify a larger block size and retry the operation.
Cause: To reuse a control file, it must be the same size as the previous one used.
Action: In the CREATE DATABASE statement, do not specify REUSE.
Cause: An inconsistent set of control files, datafiles, and redo log files was used.
Action: Use a consistent set of control files, datafiles, and redo log files. That is, all the files must be for the same database and from the same time period.
Cause: No control file was specified, or the control file specified does not exist.
Action: Specify at least one valid control file and retry the operation.
Cause: Controlfiles created by release 8.0.2 were missing some records. These records are automatically added by resizing the contolfile when attempting to run a later release. The resize failed.
Action: Look in the alert log for the reason that the resize failed. If it can be fixed by giving the controlfile more space then do so. Otherwise, use the CREATE CONTROLFILE script dumped to the trace file to create a new controlfile.
Cause: The physical block size of the operating system is inconsistent with the block size of the control file.
Action: The system will not operate with invalid control files. Either restore a valid control file or recreate the database. When using multiplexed control files, that is, more than one control file is referenced in the initialization parameter file, remove the control filename listed in the message from the initialization parameter file and restart the instance. If the message does not recur, remove the problem control file from the initialization parameter file and create another copy of the control file with a new filename in the initialization parameter file.
Cause: The physical block size, stored in the control file header, was different in physical block size returned by the O/S. This usually indicates that the control file was corrupted.
Action: Restore a good copy of the control file. For more information about control files and recovery, see the index entries on "control files," "control files, backing up," "control files, recovery and" in Oracle8 Server Concepts.
Cause: The CREATE DATABASE statement specified a combination of initialization parameters that results in the control file exceeding the internal maximum size.
Action: You must recreate the database. In the CREATE DATABASE statement, use a value less than the maximum permissible value for clauses such as MAXDATAFILES and MAXLOGFILES as described in the Oracle8 Server Administrator's Guide.
Cause: The specified control file has a different mount ID than the other control files that are being mounted. This means that the first instance to mount the database did not use this control file.
Action: Find and use the correct control file.
Cause: An error occurred when writing to one or more of the control files.
Action: See accompanying messages.
Cause: Attempted to use client process connected to dispatcher. This is not allowed for queries to control file fixed tables due to the memory requirements.
Action: Connect directly to the instance, then execute the query.
Cause: An Oracle7 to Oracle8 convert file contains invalid data or was created with an different version of the migration utility. This error can also be caused by incorrect ORACLE_HOME environment variable when "ALTER DATABASE CONVERT" command is issued.
Action: Use a correct version of the convert file or regenerate it with the migration utility. Make sure that the migration utility is the same version as the Oracle8 RDBMS executable and that the ORACLE_HOME environment variable is properly set.
Cause: The file specified in the initialization parameter file is not a control file.
Action: Edit the initialization parameter file and specify the correct control filename.
Cause: The expected size of the control file as stored in its header was different than the actual operating system file size of the control file. This usually indicates that the control file was corrupted.
Action: Restore a good copy of the control file. For more information about control files and recovery, see the index entries on "control files," "control files, backing up," "control files, recovery and" in Oracle8 Server Concepts.
Cause: The attempted operation cannot be executed at this time because this process has an alternate controlfile open for fixed table access.
Action: Retry the operation after calling cfileUseCurrent.
Cause: A block header corruption or checksum error was detected on reading the controlfile.
Action: Use the CREATE CONTROLFILE or RECOVER DATABASE USING BACKUP CONTROLFILE command.
Cause: The specified file name, which was supplied as a parameter to cfileSetSnapshotName or cfileUseCopy, exceeds the maximum file name length for this operating system.
Action: Retry the operation with a shorter file name.
Cause: The attempted operation cannot be executed at this time because this process currently holds the snapshot controlfile enqueue.
Action: Retry the operation after calling cfileUseCurrent to release the snapshot controlfile enqueue.
Cause: The attempted operation cannot be executed at this time because another process currently holds the snapshot controlfile enqueue.
Action: Retry the operation after the concurrent operation that is holding the snapshot controlfile enqueue terminates.
Cause: During an invocation of cfileMakeAndUseSnapshot or cfileUseSnapshot it was detected that no filename for the snapshot controlfile had previously been specified.
Action: First specify a name for the snapshot controlfile by calling cfileSetSnapshotName.
Cause: The snapshot controlfile was found to be nonexistent, corrupt, or unreadable during an invocation of cfileUseSnapshot.
Action: Call cfileMakeAndUseSnapshot again (or for the first time).
Cause: The specified copy controlfile was found to be corrupt or unreadable during an invocation of cfileUseCopy.
Action: Before retrying cfileUseCopy, use the ALTER DATABASE BACKUP CONTROLFILE command, specifying the same filename as specified to cfileUseCopy.
Cause: A snapshot or copy controlfile of the specified name could not be found or opened during an invocation of cfileUseSnapshot, cfileMakeAndUseSnapshot, or cfileUseCopy.
Action: Recreate the snapshot or copy controlfile using cfileMakeAndUseSnapshot or ALTER DATABASE BACKUP CONTROLFILE, respectively.
Cause: Concurrent controlfile update activity caused a query on a controlfile fixed table to read inconsistent information.
Action: Retry the operation.
Cause: An attempt was made to invoke cfileSetSnapshotName, cfileMakeAndUseSnapshot, or cfileUseSnapshot when the currently mounted controlfile is a backup controlfile.
Action: Mount a current controlfile and retry the operation.
Cause: An attempt to invoke cfileMakeAndUseSnapshot with a currently mounted controlfile that was newly created with CREATE CONTROLFILE was made.
Action: Mount a current controlfile and retry the operation.
Cause: The filename supplied as a parameter to the ALTER DATABASE BACKUP CONTROLFILE command or to cfileSetSnapshotName matches the name of a file that is currently part of the database.
Action: Retry the operation with a different filename.
