Last updated on OCTOBER 12, 2016
Applies to:Enterprise Manager for Oracle Database - Version 10.1.0.2 to 22.214.171.124.0 [Release 10.1 to 12.1]
Oracle Database - Personal Edition - Version 126.96.36.199 to 188.8.131.52 [Release 9.2 to 12.1]
Oracle Database - Enterprise Edition - Version 184.108.40.206 to 220.127.116.11 [Release 11.2 to 12.1]
Information in this document applies to any platform.
***Checked for relevance on 17-Jul-2014***
In the case of stuck recovery, you have a difficult choice. If the block is relatively unimportant, and if the problem is isolated, then it is better to corrupt the block. But if the problem is not isolated, then it may be better to open the database with the RESETLOGS option.
Because of this situation, Oracle supports trial recovery. A trial recovery applies redo in a way similar to normal media recovery, but it never writes its changes to disk and it always rolls back its changes.
If a trial recovery encounters a stuck recovery or similar problem, then it always marks the data block as corrupt in MEMORY when this action can allow recovery to proceed. Oracle writes errors generated during trial recovery to ALERT.log files. Oracle clearly marks these errors as test run errors.
Like normal media recovery, trial recovery can prompt you for archived log filenames and ask you to apply them
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms