Action
End the first backup before beginning another.
ORA–01147
SYSTEM tablespace file name is offline
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.
ORA–01148
database must be mounted exclusive for this operation
Cause
Database was not mounted exclusive.
Action
Mount the database in exclusive mode and retry the operation.
ORA–01149
cannot shutdown – file name has online backup set Cause
A normal shutdown was attempted while the online backup was in progress.
Action
End the online backup and then shut down.
ORA–01150
cannot prevent writes – file name has online backup set 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.
2 – 92
Oracle7 Server Messages
01100–01250: Oracle Files
ORA–01151
use media recovery to recover block, restore backup if needed
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.
ORA–01152
file name was not restored from a sufficiently old backup 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.
ORA–01153
an incompatible media recovery is active
Cause
An attempt was made to start an incompatible media recovery or to open and reset the redo log files 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
Wait for the completion of or cancel the other media recovery session.
ORA–01154
database busy. Open, Close, mount, and dismount not allowed now 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.
ORA–01155
the database is being opened, closed, mounted, or dismounted
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.
Oracle7 Server Messages
2 – 93
01100–01250: Oracle Files
ORA–01156
recovery in progress may need access to files
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.
ORA–01157
cannot identify datafile name – file not found
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