Release 8.0.4
A58312-01
 Library |
 Product |
 Contents |
 Index |
| Oracle8 Error Messages Release 8.0.4 A58312-01 |
|
This sections lists messages generated when files are accessed by the Oracle Server.
Cause: An attempt was made to mount a database with the name of a currently mounted database.
Action: No action required.
Cause: An attempt was made to create a database with the name of a currently mounted database.
Action: Either change the database name or shut down the other instance.
Cause: An instance tried to mount the database in exclusive mode, but some other instance has already mounted the database in exclusive or parallel mode.
Action: Either mount the database in parallel mode or shut down all other instances before mounting the database in exclusive mode.
Cause: The database name used does not match that in the control file.
Action: Ensure the correct control file and database name are used.
Cause: The number of control files used by this instance disagrees with the number of control files in an existing instance that is accessing the same database.
Action: Make sure all control files are listed in the initialization parameter CONTROL_FILES, then retry the operation.
Cause: An attempt was made to mount the database, but another instance has already mounted a database by the same name, and the mounts are not compatible. Additional messages will accompany this message to report why the mounts are incompatible.
Action: See the accompanying messages for the appropriate action to take.
Cause: An attempt was made to dismount a database before it was closed.
Action: Close the database, then retry the operation.
Cause: An attempt to perform media recovery was made, but the database is not mounted.
Action: Mount the database, then retry the operation.
Cause: Media recovery is actively being applied to the given file. The file cannot be used for normal database access or crash recovery.
Action: Wait for media recovery to complete or cancel the media recovery session.
Cause: An attempt was made to perform an operation on an unopened database.
Action: Open the database, then retry the operation.
Cause: This message reports the filename involved with other messages.
Action: See the associated messages for a description of the problem.
Cause: The datafile was missing from a CREATE CONTROLFILE command or backup control file recovery was done with a control file that was saved before the file was created.
Action: Rename the missing file to the name of the real file.
Cause: An attempt was made to continue media recovery, but media recovery had not been started.
Action: No action required.
Cause: An attempt was made to open a datafile that is in need of media recovery.
Action: First apply media recovery to the datafile identified in the message, then retry the operation.
Cause: The device on which the file resides is probably off line.
Action: Restore access to the device, then retry the operation.
Cause: The device on which the file resides is probably off line.
Action: Restore access to the device, then retry the operation.
Cause: Usually the file is not accessible.
Action: Make sure the datafile is in the expected location and can be accessed properly, then retry the operation.
Cause: An attempt was made to add a datafile with a block size that is greater than the maximum block size allowed.
Action: Retry the operation with a smaller block size.
Cause: An attempt to add a datafile failed because the limit for such files had already been reached.
Action: If more database space is required, export the database and re-create it with a higher limit for datafiles and perhaps increased file size.
Cause: Insufficient space on device.
Action: Decrease the size of the requested file or allocate a file on another device with more available space. If a file size was not specified in the statement, then specify a file size smaller than the available space on the device.
Cause: An attempt to remove an online datafile failed because the file was not closed or was opened in parallel mode. This message can occur when trying to drop a tablespace. A tablespace cannot be dropped while users are accessing its data, index, rollback, or temporary segments or while the database is mounted in parallel mode.
Action: Shut down Oracle and mount the database in exclusive mode to drop a tablespace. To prevent users from opening the tablespace, take it off line or put the instance in restricted access mode.
Cause: An attempt to rename an online datafile failed because the file was not closed or was being recovered. Either the file is online and the datafile is open to some instance, or another process is currently performing media recovery on the file.
Action: Close the file or shut down Oracle and mount the database in exclusive mode. End all recovery sessions. To prevent users from opening the file, take its tablespace off line or put the instance into restricted mode.
Cause: The information in the datafile is inconsistent with information from the control file. This could be for any of the following reasons:
Action: Make certain that the datafiles and control files are the correct files for this database, then retry the operation.
Cause: An attempt to start backup of an online tablespace failed because archiving was not enabled.
Action: Enable archiving and retry the operation.
Cause: An attempt to do media recover found that the file was not available for recovery. Either it is online and the database is open in some instance, or another process is currently doing media recovery on the file.
Action: Do not do media recovery.
Cause: An attempt to disable media recovery encountered an online recovery still in progress.
Action: Wait for the recovery to finish before retrying the operation.
Cause: An operation failed because the database was not mounted in exclusive mode.
Action: Shut down Oracle and mount the database in exclusive mode.
Cause: The specified database name is too long.
Action: Shorten the database name to eight characters or fewer, then retry the operation.
Cause: A file to be backed up in the online backup is offline.
Action: Either of the following:
Cause: A user's default or temporary tablespace was dropped.
Action: Re-create the tablespace that was dropped or change the user's default or temporary tablespace.
Cause: The named datafile was created under an incompatible version of Oracle, or the file is invalid or nonexistent.
Action: Shut down and restart the correct version of Oracle or check the references to the datafile and make sure it exists.
Cause: The specified value of the initialization parameter DB_FILES is too large.
Action: Reduce the value of the DB_FILES parameter and retry the operation.
Cause: The specified datafile name is too long.
Action: Shorten the filename and retry the operation.
Cause: The specified redo log filename is too long.
Action: Shorten the filename and retry the operation.
Cause: An attempt to access a database failed because it is mounted in exclusive mode by another instance.
Action: Either shut down the other instance or wait for the other instance to either close the database or mount it in parallel mode, before retrying the operation.
Cause: A query failed because it referenced a datafile that belongs to an offline tablespace. An offline tablespace must be brought online to access its data.
Action: Wait until the tablespace is brought online before executing the query.
Cause: An attempt was made to specify a size in the AS clause of the ALTER DATABASE CREATE datafile command that is smaller than the size needed.
Action: Issue the statement again using the correct size for the file.
Cause: It was not possible to get the lock for a file that is offline when attempting to bring it online. The most likely cause is that the lock is still held by the instance that is took it offline.
Action: Wait for the other instance to release the lock on the file.
Cause: The requested operation cannot be done when the database is mounted but not open by this instance, and another instance has the database open.
Action: Execute the operation in the open instance, open the database in the current instance, or close the database in the other instances.
Cause: The RESET LOGS option was specified in an ALTER DATABASE OPEN statement, but there has been no incomplete recovery session.
Action: Re-execute the statement without specifying RESET LOGS.
Cause: All the files were offline when attempting to end an online backup.
Action: None. Online backup does not need to be ended for this tablespace.
Cause: An attempt to change a datafile's name in the control file failed because no file was found with the new name.
Action: Make sure that the datafile has been properly renamed by the operating system, then retry the operation.
Cause: None of the files were found to be in the online backup when attempting to end the online backup.
Action: None. Online backup does not need to be ended for this tablespace.
Cause: An attempt to disable media recovery found a file that needs media recovery. Therefore, media recovery cannot be disabled.
Action: Recover the offending file or drop the tablespace to which it belongs, then retry the operation.
Cause: The specified file size is larger than the maximum allowable size.
Action: Specify a smaller size.
Cause: ALTER TABLESPACE ... OFFLINE IMMEDIATE or ALTER DATABASE DATAFILE ... OFFLINE is only allowed if database is in ARCHIVEREDO LOG mode.
Action: Take the tablespace offline as usual or do a shutdown abort before attempting the required operation. It is worthwhile reconsidering the backup strategy for the database. The attempted operations can be done if ARCHIVEREDO LOG mode is enabled.
Cause: An attempt was made to start an online backup, but an online backup was already started for one of the datafiles.
Action: End the first backup before beginning another.
Cause: A file belonging to the SYSTEM tablespace has been marked offline by the database administrator. The database cannot be started until all SYSTEM tablespace files are online and can be opened.
Action: Bring the file online.
Cause: An attempt was made to mount the database PARALLEL without the existence of a lock manager.
Action: Mount the database in EXCLUSIVE mode and retry the operation.
Cause: A normal shutdown was attempted while the online backup was in progress.
Action: End the online backup and then shut down.
Cause: Tablespace cannot be taken offline or made read-only when online backup is running. Ending the backup entails writing the file header, which this operation, were it permitted, would prevent.
Action: End the online backup and then take the tablespace offline or make it read-only.
Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery. This message is usually accompanied by ORA-01172.
Action: There is additional information for ORA-01172. Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, restore the file from a backup and recover it again.
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the database consistent. This file is still in the future of the last redo log applied. The most likely cause of this message is forgetting to restore the file from backup before doing incomplete recovery.
Action: Apply additional redo log files until the database is consistent or restore the datafiles from an older backup and repeat recovery.
Cause: An attempt was made to start an incompatible media recovery or to open resetlogs during media recovery. Media recovery sessions are incompatible if they attempt to recover the same datafile. Incomplete media recovery or OPEN RESETLOGS is incompatible with any media recovery.
Action: Complete or cancel the other media recovery session.
Cause: Some operation is in progress that expects the state of the instance to remain open or mounted.
Action: Wait for the operation to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT.
Cause: The attempted operation will not succeed while the instance is in one of the states mentioned in the message.
Action: Wait for the open, close, mount, or dismount to complete and try again. If attempting a normal database shutdown, try SHUTDOWN ABORT.
Cause: Either media or instance recovery is in progress. The recovery may need access to the files that the attempted operation tried to use.
Action: Wait for the recovery to complete and try again.
Cause: The background process was not able to find one of the datafiles. The database will prohibit access to this file but other files will be unaffected. However, the first instance to open the database will need to access all online datafiles. Accompanying messages from the operating system will describe why the file was not found.
Action: Make the file available to the database. Then either open the database or do ALTER SYSTEM CHECK datafiles. See also your operating system-specific Oracle documentation.
Cause: Another instance has mounted a database of this name already.
Action: Find and shut down the instance that has this database mounted before issuing the CREATE CONTROLFILE statement.
Cause: Not all of the files specified in the CREATE CONTROLFILE statement are from the same database.
Action: Check the list of files specified in the CREATE CONTROLFILE statement and remove files that are not part of the same database.
Cause: The file in the datafile or log file section of the CREATE CONTROLFILE statement is not of the type listed in the command line.
Action: Check the file and determine its type. Enter the command again using the correct type for the file.
Cause: The database name given at the command line does not match the database name found in the file header. The database name specified at the command line is incorrect.
Action: Enter the command again with the correct name for the database.
Cause: CREATE CONTROLFILE discovered that the block size for this file is incompatible with the initialization parameter DB_BLOCK_SIZE used to allocate cache buffers. If this is not the first file, then there is a mixture of block sizes, or the file is corrupt.
Action: If this is the first file in the command, then correct DB_BLOCK_SIZE to match the file and restart the instance; if it is not the first file, find the correct version of the file.
Cause: The size specified in bytes in the SIZE clause of the CREATE CONTROLFILE statement does not equate to the number of blocks recorded in the header.
Action: Specify the correct filename and size, in bytes.
Cause: The value for MAXLOGFILES specified on the command line is greater than num.
Action: Retry the command with a value of MAXLOGFILES that is num or less.
Cause: The value for MAXDATAFILES specified on the command line is greater than num.
Action: Retry the command with a value of MAXDATAFILES that is num or less.
Cause: In the CREATE CONTROLFILE statement, the file mentioned has a file number that is larger than that specified in MAXDATAFILES or MAXLOGFILES, or the file number is larger than the maximums specified in the initialization parameter, DB_FILES.
Action: Increase the values of MAXLOGFILES, MAXDATAFILES, or of the parameter DB_FILES.
Cause: There is an overlap of file numbers in the files specified on the command line or the same file is specified twice. If they are not the exact same file then one is likely to be a backup of the other. If they are two members of the same log they must be specified together in a group file spec. This message will also appear if the same controlfile appears more than once in the CONTROL_FILES parameter in the INIT.ORA file. If this happens, check for additional error messages.
Action: Confirm that the file mentioned is not a repeat of a file already mentioned in the command. If they are different files then omit the earlier backup. If they are members of the same log, insure they are in the same group file specification. If this message appears because of a duplicate controlfile, check the CONTROL_FILES parameter in the INIT.ORA file and see if a file is specified more than once. If all files names appear to be unique, check to make sure that the actual controlfiles themselves are unique. For example, in UNIX check for a symbolic or a hard link to another controlfile in the list.
Cause: The file is located on a device with a different physical block size than the other members in the group.
Action: Use a physical device with matching block size.
Cause: datafile number 1 was not specified in a CREATE CONTROLFILE statement.
Action: Locate datafile number 1 and retry the CREATE CONTROLFILE statement, making certain to include datafile on the command line.
Cause: A file specified in the CREATE CONTROLFILE statement was not found. All datafiles and all redo log files, if NORESETLOGS was used, must be accessible by the process that issues the CREATE CONTROLFILE statement.
Action: Check the statement for a typing mistake in the filename and check for the existence of all files. Then issue the statement again after correcting the filenames.
Cause: The checkpoint in the file header could not be advanced. See accompanying messages for the reason. The datafile will be taken offline the same as for a write error of a data block.
Action: See accompanying messages for details. Restore access to the file, do media recovery, and bring it back online.
Cause: Crash recovery or instance recovery could not apply a change to a block because it was not the next change. This can happen if the block was corrupted and then repaired during recovery.
Action: Perform a RECOVER datafile for the file containing the block. If this does not resolve the problem, then restore the file from a backup and recover it again.
Cause: Either
Action: Either
Cause: The maximum number of datafiles supported by this instance is not the same as for the other instances. All instances must be able to open all the files any instance can open.
Action: Change the value of the DB_FILES initialization parameter to be compatible.
Cause: The data dictionary has more files than the instance can support.
Action: Increase the value of the initialization parameter DB_FILES, then shut down and restart the instance.
Cause: After a CREATE CONTROLFILE statement, the data dictionary has more datafiles than supported by the control file.
Action: Re-create the control file with a larger value for MAXDATAFILES.
Cause: When comparing the control file with the data dictionary after a CREATE CONTROLFILE or OPEN RESETLOGS, it was noted that this datafile was inconsistent with the dictionary. Most likely the file is a backup of a file that was dropped from the database, and the same file number was reused for a new file. It may also be that an incomplete recovery stopped at a time when this file number was used for another datafile.
Action: Do a CREATE CONTROLFILE with the correct file or none at all.
Cause: An attempt was made to use the ALTER DATABASE CREATE datafile to re-create a datafile that existed at the last CREATE CONTROLFILE command. The information needed to re-create the file was lost with the control file that existed when the file was added to the database.
Action: Find a backup of the file and recover it. Perform incomplete recovery to the time before the file was originally created.
Cause: During datafile recovery, a file was listed that was not part of the database.
Action: Recheck the filename. Remember to use single quotation marks at the SQL*DBA command line. Remember also that the filename is translated in the operating environment of SQL*DBA.
Cause: datafile 1 cannot be created with the ALTERDATABASECREATEDATA FILE command.
Action: Either recover the file from a backup or re-create the database.
Cause: An attempt was made to use the ALTER DATABASE CREATE datafile command to re-create a datafile that existed before the last time the database was opened using the RESETLOGS option.
Action: Find a backup of the file and recover the backup file. Perform incomplete recovery to a time before the file was originally created.
Cause: An attempt was made to use the ALTER DATABASE CREATE datafile command to re-create a datafile that is currently online in an open instance or is currently being recovered.
Action: Close the database to all instances or end all recovery sessions. Then take the file offline and retry the operation.
Cause: The database is mounted in exclusive mode by another instance. It is not possible to mount a database in SHARED mode if it is mounted in exclusive mode by another instance.
Action: Shut down the other instance and try again.
Cause: An ALTER DATABASE ADD log file command specified a log number for the new redo log which is already in use.
Action: Specify a different redo log file number or let the database choose an unused value.
Cause: An ALTER DATABASE ADD log file command specified a redo log number for the new redo log that is too large.
Action: Specify a valid redo log file number.
Cause: The datafile did not pass the checks to ensure it is part of the database. See the accompanying messages for the reason the verification failed.
Action: Make the correct file available to database. Then either open the database or execute ALTER DATABASE CHECK.
Cause: The datafile did not pass the checks to ensure it is part of the database. Reading the file is not allowed until it is verified.
Action: Make the correct file available to database. Then either open the database or execute ALTER DATABASE CHECK.
Cause: A redo log file member given to CREATE CONTROLFILE is on a physical device that has a different block size than the device originally used to create the redo log.
Action: Move the file to a device with the correct block size or use the RESETLOGS option to CREATE CONTROLFILE.
Cause: In a CREATE CONTROLFILE command, either this file or all previous files were backups from before the last RESETLOGS. This also may occur if this is a file that is offline and has been offline since before the last RESETLOGS.
Action: If the file was taken offline normally before the last RESETLOGS and is still offline, omit it from the CREATE CONTROLFILE command. Rename and online the file after the database is open. Otherwise, find the version of the mentioned file consistent with the rest of the datafiles and retry the command.
Cause: An attempt was made to perform media recovery when the redo log reset information in a datafile does not match the control file. Either the datafile or the control file must be a backup that was made before the most recent ALTER DATABASE OPEN RESETLOGS.
Action: Restore the file from a more recent backup.
Cause: An attempt was made to take a tablespace offline as usual, but the file named in the message was already offline.
Action: Bring the datafile online first or use the IMMEDIATE option when taking the tablespace offline.
Cause: At least two redo log files from at least one thread must be specified in the CREATE CONTROLFILE command line.
Action: Find the missing redo log files and retry the command with the newly found redo log files included in the command line.
Cause: An attempt was made to perform media recovery on a file, but a different copy of the file now exists since the last media recovery. Perhaps an invalid backup of the file was restored.
Action: Find the correct version of the file, then retry media recovery.
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the file consistent. The named file was not closed cleanly when it was last opened by the database. The most likely cause of this message is forgetting to restore the file from a backup before doing incomplete recovery.
Action: The file must be recovered to a time when it was not being updated. Either apply more redo logs until the file is consistent or restore the file from an older backup and repeat recovery.
For more information about recovery, see the index entry "recovery" in the Oracle8 Server Administrator's Guide.
Cause: An incomplete recovery session was started, but an insufficient number of redo logs were applied to make the file consistent. The reported file is an online backup that must be recovered to the time the backup ended.
Action: Either apply more redo logs until the file is consistent or restore the file from an older backup and repeat the recovery.
For more information about online backup, see the index entry "online backups" in the Oracle8 Server Administrator's Guide.
Cause: The file was being recovered but the recovery did not terminate normally. This left the file in an inconsistent state. No more recovery was successfully completed on this file.
Action: Either apply more logs until the file is consistent or restore the backup again and repeat recovery.
For more information about media recovery, see the index entry, "media recovery" in the Oracle8 Server Administrator's Guide.
Cause: During a CREATE CONTROLFILE statement, all threads represented in the redo logs must be represented by at least two redo logs: a last redo log and a second redo log. The named thread does not contain two redo logs.
Action: Either find more redo logs from the named thread or remove all references to redo logs from that thread, then retry the command.
Cause: File sizes must be given for all redo log files if doing a CREATE CONTROLFILE with the RESETLOGS option.
Action: Retry the command with the appropriate redo log file size.
Cause: Attempting to end an online backup for a file that is not in online backup.
Action: Do not enter command since it is not needed.
Cause: The size of the file, as returned by the operating system, is smaller than the size of the file as indicated in the file header and the control file. Somehow the file has been truncated.
Action: Restore a good copy of the datafile from a backup and perform recovery as needed.
Cause: An I/O error was reported for the file header. The error was trapped and a second attempt will be made.
Action: The file probably will require recovery. Further error messages will indicate what is needed.
Cause: The creation time in the file header is not the same as the creation time in the control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the datafile and perform recovery as needed.
Cause: The creation change number in the file header is not the same as the creation change number in the control file. This is probably a copy of a file that was dropped.
Action: Restore a current copy of the datafile and perform recovery as needed.
Cause: The file number in the file header is not correct. This is probably a restored backup of the wrong file, but from the same database.
Action: Restore a copy of the correct datafile and perform recovery as needed.
Cause: The file type in the header is not correct for a datafile. This is probably a redo log file or control file.
Action: Restore a copy of the correct datafile and perform recovery as needed.
Cause: The database ID in the file header does not match the database ID in the control file. The file may be from a different database, or it may not be a datafile at all. If the database was rebuilt, this may be a file from before the rebuild.
Action: Restore a copy of the correct datafile and perform recovery as needed.
Cause: The control file change sequence number in the datafile is greater than the number in the control file. This implies that the wrong control file is being used.
Note: If this message occurs repeatedly, by opening the database many times, the message may stop occurring without the problem being corrected. Every attempt to open the database will advance the control file change sequence number until it is great enough.
Action: Use the current control file or perform cancel-based recovery to make the control file current. Be sure to follow all restrictions on performing a cancel-based recovery.
Cause: The checkpoint in the file header is less recent than in the control file. If opening a database that is already open by another instance or if another instance just caused this file to be placed online, then the database is probably looking at a different version of the file. Otherwise, a backup of the file was probably restored while the file was still in use.
Action: Make correct file available to database. Then either open the database or do ALTER DATABASE CHECK.
Cause: The reset redo log data in the file header does not match the control file. If the database is closed or the file is offline, this is an old backup that was taken before the last ALTER DATABASE OPEN RESETLOGS command. If opening a database that is already open by another instance or if another instance just put this file online, then we are probably looking at a different version of the file. Otherwise a backup of the file was probably restored while the file was in use.
Action: Make the correct file available to the database. Then either open the database or issue an ALTER DATABASE CHECK statement.
Cause: The file header block is internally inconsistent. The beginning of the block has a header with a checksum and other data for insuring the consistency of the block. It is possible that the last disk write did not operate correctly. The most likely problem is that this is not a datafile for any database.
Action: Make the correct file available to the database. Refer to any trace file generated after this message for more information. If the trace file indicates that the checksum is wrong, restore the file from a backup and perform media recovery.
Cause: The file is not a copy of the file LAST used under Oracle7. This datafile is either a backup taken from before the migration, or the database was opened by Oracle7 after the migration utility was run. When converting a database from Oracle7 to Oracle8, the migration program MUST be the LAST utility to access the database under Oracle7. Only the datafiles that were current when the migration was done may be accessed by Oracle8.
Action: Have operating system make correct data file available to database, or repeat the Oracle7 to Oracle8 migration. Make sure that database is NOT opened after migration utility is run.
Cause: The value specified for MAXLOGMEMBERS is too large.
Action: Retry the command with a smaller value for MAXLOGMEMBERS.
Cause: The value specified for MAXINSTANCES is too large.
Action: Retry the command with a smaller value for MAXINSTANCES.
Cause: The value specified for MAXLOGHISTORY is too large.
Action: Retry the command with a smaller value for MAXLOGHISTORY.
Cause: A CREATE CONTROLFILE command did not list all of the enabled threads for the database.
Action: Issue the CREATE CONTROLFILE command again and include all of the enabled threads.
Cause: A thread specified in the CREATE CONTROLFILE command was enabled, but the datafiles indicate that the thread should be disabled. This is probably because the redo log files supplied to the CREATE CONTROLFILE command are from a time before the thread was disabled.
Action: This thread is not required for the operation of the database. Retry the command without specifying the thread. If desired, the thread can be re-created after the database has been opened.
Cause: A member of a redo log file group specified in the CREATE CONTROLFILE command is not part of the same group as the previous members.
Action: Group together the correct members of the redo log file group for the CREATE CONTROLFILE command.
Cause: A member of a redo log file group specified in the CREATE CONTROLFILE command is from a different point in time from the previous members. One of the members specified may be an older, possibly a backup copy, version of the redo log.
Action: Find the correct version of the redo log or leave it out of the CREATE CONTROLFILE command.
Cause: A query was issued against an object not recognized as a fixed table or fixed view before the database was opened.
Action: Revise the query to include only fixed objects or open the database.
Cause: A query issued against a fixed table or view required a temporary segment for sorting before the database was open. Only in-memory sorts are supported before the database is open.
Action: Rephrase the query to avoid a large sort and increase the SORT_AREA_SIZE parameter in the initialization parameter file to enable the sort to be done in memory.
Cause: When the database writer opens the datafile, it is accessing a different physical file than the foreground doing the recovery. The time-stamp set in the file header by the foreground was not found by the background. It may be that the background process could not read the file at all.
Action: Look in the DBWR trace file for the error it received when attempting to read the file header. Reconfigure the operating system as needed to have the filename successfully access the same file when opened by a background process.
Cause: An attempt was made to create a database or control file that does not have room for at least two redo logs per thread of redo. A thread of redo must have two online redo logs in order to be enabled. It does not make sense to allow more redo threads than can be supported by the logs.
Action: Either reduce the MAXINSTANCES argument or increase MAXLOGFILES.
Cause: The SET database name option was specified to CREATE CONTROLFILE, but RESETLOGS was not specified. The database name can only be changed when opening the database with RESETLOGS.
Action: Either add the RESETLOGS option or drop the SET option to CREATE CONTROLFILE.
Cause: Group number specified at CREATE CONTROLFILE does not match the group number stored in the header. Most likely the specification is wrong.
Action: Omit the GROUP option or give the correct one.
Cause: The redo log is for a thread greater than the MAXINSTANCES arguments.
Action: Increase the value for MAXINSTANCES and retry the command.
Cause: The redo log file member in the accompanying message is for the same group as the previous members, but other fields in the header are different. Either a file header is corrupted, or some file is a member of a deleted redo log.
Action: Correct the redo log member or omit this member from the command.
For more information about redo logs, see the index entries "redo log" and "redo log files" in the Oracle8 Server Administrator's Guide.
Cause: The redo log file in the accompanying message is inconsistent with the contents of other redo logs given in the CREATE CONTROLFILE command. Either a file header is corrupted, or some file is an old copy rather than the current version. The problem may not be with the redo log listed because all that can be detected is that there is an inconsistency. All redo log files listed in the command must be the current versions of the online redo logs.
Action: Find the correct online redo logs or use the RESETLOGS option.
For more information about redo logs, see the index entries "redo log" and "redo log files" in the Oracle8 Server Administrator's Guide.
Cause: The SET DATABASE option was not included in the CREATE CONTROLFILE command when installing a seed database. The database does not have a database ID because it is intended to be installed at multiple sites, and each site needs to be a different database with its own database ID. Both the SET DATABASE and RESETLOGS options must be specified to create the control file for this database.
Action: Retry the command with the SET DATABASE and RESETLOGS options.
Cause: The datafile in the accompanying message is inconsistent with the contents of the redo logs given in the CREATE CONTROLFILE command. The most likely cause is that one or more of the online redo logs was missing from the command. It is also possible that one or more of the redo logs is an old copy rather than the current version. All online redo log files must be listed in the command and must be the current versions of the online redo logs.
Action: Retry the command with the correct online redo logs or use the RESETLOGS option.
For more information about datafiles, see the index entry "datafiles" in the Oracle8 Server Administrator's Guide.
Cause: An attempt to make a tablespace read-only encountered an offline file.
Action: Bring the file online and retry the operation.
Cause: An attempt to make a tablespace read-write encountered an offline file.
Action: Bring the file online and retry the operation.
Cause: An attempt to start an online backup encountered a read-only file.
Action: Read-only files do not need to be set into online backup mode. Start the backup without using the BEGIN BACKUP command.
Cause: An attempt to do media recovery using a backup control file encountered a read-only file. Typically, read-only files do not need to be recovered. However, if the recovery is using a backup control file, all online files must be recovered.
Action: Take the read-only file offline and bring the tablespace online only after opening the database. Ensure that the backup control file was in use when the currently read-only file was read-write. If such a control file is unavailable, you may be able to re-create it using the CREATE CONTROLFILE command.
Cause: Attempted to end an online backup of file when the file is busy. Some operation such as recovery or rename may be active, or there may still be some instance that has the database open with this file online.
Action: If there is an instance with the database open then the backup can be ended by using the ALTER TABLESPACE command. Otherwise wait for the completion of the other operation.
Cause: One or more of the files in an end backup command failed. Some other files given in the same command may have succeeded.
Action: See the accompanying error messages for the reason the backups could not be ended. Any files not listed in the error messages were successful.
Cause: The indicated error occurred while doing initialization processing of file headers.
Action: The error indicated should be corrected. An attempt is made to recover from this error by using a slower access algorithm.
Cause: An operating system error occurred during the resize.
Action: Fix the cause of the operating system error and retry the command.
Cause: An operating system error occurred during the resize.
Action: The error is ignored, operation continues normally.
Cause: An online file used an external cache, but the database was in NOARCHIVELOG mode. Since an external cache may require media recovery this cannot be allowed.
Action: Change the database to be in ARCHIVELOG mode or do not use an external cache. For more information about ARCHIVELOG, see the index entry on "ARCHIVELOG" in Oracle8 Server SQL Reference.
Cause: The command specified adding more datafiles than can be done in one command. It is necessary to fit all the file names into one log entry, but that would make the entry too large.
Action: If this is a CREATE TABLESPACE command, create with fewer files then add the other files later. If this is an ADD DATAFILE command, break it up into multiple commands. For more information about CREATE TABLESPACE and ADD DATAFILE, see the index entries on "CREATE TABLESPACE" and on "ADD DATAFILE clause, of ALTER TABLESPACE command" in Oracle8 Server SQL Reference.
Cause: The external cache may have been restarted.
Action: Take the file mentioned in the error stack offline, perform media recovery, bring the file online, and retry the attempted operation. You can also restart all instances to make sure they access all datafiles through consistent external caches.
For more information about external caches and the media recovery of datafiles, see the index entries on "caches" and on "datafiles, backups, media recovery and" in Oracle8 Server Concepts.
Cause: The database is in NOARCHIVELOG mode and a database file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the instance.
For more information about media failure, see the index entry on "media failure" in the Oracle8 Server Administrator's Guide. For more information on NOARCHIVELOG, see the index entry on "NOARCHIVELOG" in Oracle8 Server SQL Reference.
Cause: A system tablespace file was detected as inaccessible due to media failure.
Action: Restore accessibility to the file mentioned in the error stack and restart the instance.
For more information about media failure, see the index entry on "media failure" in the Oracle8 Server Administrator's Guide. For more information on tablespaces, see the index entry on "tablespaces" in Oracle8 Server SQL Reference.
Cause: Media recovery with a backup controlfile or a controlfile that was rebuilt encountered the creation of a datafile that was not in the controlfile. An entry has been added to the controlfile for the new datafiles, but with the file name UNNAMEDnum, where num is the file number. Attached errors describe the file names that were originally used to create the files.
Action: Rename the files to valid file names and resume recovery. If necessary, the command ALTER DATABASE CREATE DATAFILE may be used to create a file suitable for recovery and do the rename. If the file is not going to be recovered, then take it offline with the FOR DROP option.
For more information about datafiles and media recovery, see the index entry on "recovery, media, datafile" in Oracle8 Server Concepts and the index entry on "ALTER DATABASE command" in Oracle8 Server SQL Reference.
Cause: An attempt was made to do an OPEN RESETLOGS with a file that will be lost because it is offline. The file was not taken offline with the FOR DROP option.
Action: Either bring the file online and recover it, or take it offline with the FOR DROP option.
For more information about bringing a file online and recovering the file, see the index entry on "redo log files, online, recovery use of" in Oracle8 Server Concepts.
Cause: The files named in the accompanying errors are backups that were made before a tablespace point in time recovery of this tablespace. They cannot be recovered to a time after the point in time recovery.
Action: Restore more recent backups and recover them.
Cause: Recovery of the whole database encountered redo indicating there was a point in time recovery of the tablespace. The new version of the files in the tablespace should be included in the recovery, but that was not done.
Action: If the tablespace should not be recovered, take its file offline for drop. If it should be recovered, take its file offline for drop. If it should be recovered, then restore or rename as needed and restart the recovery.
Cause: Attempting to do a RESETLOGS open with a file entry in the controlfile that was created by switchToCopy, and the file was originally created after the UNTIL time of the incomplete recovery. The file number may be in use for a different file which would be lost if the RESETLOGS was allowed.
Action: If more recovery is desired then apply redo until the creation time of the file is reached. If the file is not wanted and the same file number is not in use at the stop time of the recovery, then the file can be taken offline with the FOR DROP option. Otherwise a different controlfile is needed to allow the RESETLOGS. Another backup can be restored and recovered, or a controlfile can be created via CREATE CONTROLFILE.
Cause: Attempting to archive an online redo log or enable archiving for a clone database.
Action: Do not attempt to archive from a clone. The archive log destination could easily be the same as the primary database destroying its archived logs. If archiving is needed then recreate database as not a clone.
Cause: The indicated error occurred while terminating the processing of file headers. The error was other than a WRITE error.
Action: The indicated error should be corrected.
Cause: Read of the file header returned a record but its version cannot be identified. Either the header has been corrupted, or the file is not a valid database file.
Action: Have the operating system make the correct file available to the database, or recover the file.
