Oracle 11g Error Codes and Solution Suggestions from ORA-10500 to ORA-10600
- ORA-10546: Cannot perform block media recovery; standby database does not have requisite redo.
- Cause: An attempt was made to perform block media recovery on the standby database when the necessary redo was not available.
- Action: Wait until the necessary redo is available and reattempt block media recovery.
- ORA-10547: Cannot perform block media recovery; standby database is not caught up with primary.
- Cause: An attempt was made to perform block media recovery on the standby database up to scn %s, which is greater than the highest scn of %s yet applied at the standby.
- Action: Recover the standby up to scn %s and reattempt block media recovery.
- ORA-10548: Cannot perform block media recovery on a read-only plugged-in datafile.
- Cause: An attempt was made to perform block media recovery on a read-only plugged-in datafile.
- Action: Convert the plugged-in datafile to read/write and reattempt block media recovery.
- ORA-10549: Cannot perform block media recovery using a read-only plugged-in backup datafile.
- Cause: An attempt was made to perform block media recovery using a backup of a read-only plugged-in datafile.
- Action: Reattempt block media recovery using a backup taken after the plugged-in datafile has been converted to read/write.
- ORA-10553: Incompatible UNTIL CONSISTENT clause
- Cause: RECOVER UNTIL CONSISTENT required database-level recovery with a backup control file.
- Action: Omit the UNTIL CONSISTENT clause and retry recovery.
- ORA-10554: Media recovery failed to bring datafile string to a consistent point
- Cause: Media recovery couldn’t recover database to a consistent point due to the specified datafile.
- Action: Restore a backup of the datafile.
- ORA-10560: block type ‘string‘
- Cause: Report block type for details of another error.
- Action: See associated error message.
- ORA-10561: block type ‘string‘, data object# string
- Cause: Report block type and data object number for details of another error.
- Action: See associated error message.
- ORA-10562: Error occurred while applying redo to data block (file# string, block# string)
- Cause: See other errors on error stack.
- Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
- ORA-10563: Test recovery had to corrupt data block (file# string, block# string) in order to proceed
- Cause: Test recovery completed.
- Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
- ORA-10564: tablespace string
- Cause: Report tablespace name for details of another error.
- Action: See associated error message.
- ORA-10565: Another test recovery session is active
- Cause: There can only be one test recovery session at any time. Another test recovery session is active.
- Action: Wait till the other test recovery session completes.
- ORA-10566: Test recovery has used all the memory it can use
- Cause: Test recovery tests redo in memory. It can no longer proceed because it has consumed all the memory it can use.
- Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
- ORA-10567: Redo is inconsistent with data block (file# string, block# string, file offset is string bytes)
- Cause: There are two possible causes of this error: (1) A write issued by Oracle was lost by the underlying OS or storage system. (2) an Oracle internal error.
- Action: Investigate why the error occurred and how important is the data block. Media and standby database recovery usually can continue if user allows recovery to corrupt this data block.
- ORA-10568: Failed to allocate recovery state object: out of SGA memory
- Cause: out of SGA memory
- Action: Restart the instance. If problem persists, call Oracle support.
- ORA-10570: Test recovery complete
- Cause: Test recovery completed.
- Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary result of the test recovery.
- ORA-10571: Test recovery canceled
- Cause: User canceled test recovery.
- Action: No action is needed. Test recovery has ended successfully. See other messages on error stack for a summary of the result of the test recovery.
- ORA-10572: Test recovery canceled due to errors
- Cause: See other errors on the error stack.
- Action: is needed. See other messages on error stack for a summary of the result of the test recovery so far.
- ORA-10573: Test recovery tested redo from change string to string
- Cause: This message show the range of test recovery have tested.
- Action: No action is needed. See other messages on error stack.
- ORA-10574: Test recovery did not corrupt any data block
- Cause: This message summarizes test recovery result.
- Action: No action is needed. See other messages on error stack.
- ORA-10575: Give up restoring recovered datafiles to consistent state: out of memory
- Cause: There were not enough memory to restore recovered datafiles to consistent state
- Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
- ORA-10576: Give up restoring recovered datafiles to consistent state: some error occurred
- Cause: See alert file or other errors on the stack for a cause of the problem.
- Action: This error is just a warning: You may not be able to open the database with resetlogs immediately after this error. However, you may continue media/standby recovery, and that may make the datafiles recovered consistent again.
- ORA-10577: Can not invoke test recovery for managed standby database recovery
- Cause: Test recovery option is used for managed standby database recovery.
- Action: Either remove the test recovery option or invoke manual test standby database recovery.
- ORA-10578: Can not allow corruption for managed standby database recovery
- Cause: You used the allow corruption option for managed standby database recovery.
- Action: Either remove the allow corruption option or invoke manual standby database recovery.
- ORA-10579: Can not modify control file during test recovery
- Cause: To proceed with recovery, test recovery needs to modify the control file. But test recovery is not allowed to modify control file.
- Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
- ORA-10580: Can not modify datafile header during test recovery
- Cause: To proceed with recovery, test recovery needs to modify a datafile header. But test recovery is not allowed to modify datafile headers.
- Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
- ORA-10581: Can not modify redo log header during test recovery
- Cause: To proceed with recovery, test recovery needs to modify a redo log header. But test recovery is not allowed to modify redo log headers.
- Action: No action is needed. Test recovery has ended successfully. It can only go so far in the redo stream.
- ORA-10582: The control file is not a backup control file
- Cause: User requested backup control file test recovery, but the control file is not a backup control file.
- Action: Use a backup control file, or do not use USING BACKUP CONTROLFILE option.
- ORA-10583: Can not recovery file string renamed as missing during test recovery
- Cause: One of the files to be recovered is renamed as missing.
- Action: Rename the file to the correct file or offline it.
- ORA-10584: Can not invoke parallel recovery for test recovery
- Cause: Both test recovery and parallel recovery are requested.
- Action: Drop either one of the two recovery options.
- ORA-10585: Test recovery can not apply redo that may modify control file
- Cause: Test recovery has encountered a special redo that may modify control file.
- Action: No action is needed. Test recovery has proceeded successfully as far as it could from its starting point.
- ORA-10586: Test recovery had to corrupt 1 data block in order to proceed
- Cause: This message summarizes test recovery result: Oracle may have to corrupt one block in order to apply the range of redo tested.
- Action: See alert log for details of the problem.
- ORA-10587: Invalid count for ALLOW n CORRUPTION option
- Cause: The number specified in the ALLOW n CORRUPTION option is too big.
- Action: Use a smaller number.
- ORA-10589: Test recovery had to corrupt string data blocks in order to proceed
- Cause: This message summarizes test recovery result: Oracle may have to corrupt a number of data blocks as specified in the message in order to apply the range of redo tested.
- Action: See alert log for details of the problems.