Database Reference
In-Depth Information
Here is some sample output:
GROUP# STATUS ARC THREAD# SEQUENCE# FIRST_CHANGE#
------ ---------------- --- -------- ---------- -------------
1 INACTIVE YES 1 86 533781
2 INACTIVE YES 1 85 533778
3 CURRENT NO 1 87 533784
In this case, you can restore Online redo logs:recovery and recover up to, but not including, SCN 533784. Here's
how you would do that:
RMAN> restore database until scn 533784;
RMAN> recover database until scn 533784;
RMAN> alter database open resetlogs;
■
Note
For complete details on incomplete recovery, and/or flashing back your database see Chapter 6.
Losing all members of your current online redo log group is arguably the worst thing that can happen to your
database. If you experience media failure with all members of the current online redo group, then you most likely will
lose any transactions contained in those logs. In this situation, you will have to perform incomplete recovery before
you can open your database.
■
if you are desperate to restore transactions lost in damaged current online redo log files, then contact Oracle
support to explore all options.
Tip
Summary
It's critical that you understand how to handle online redo log failures. Oracle doesn't provide an automated method
for fixing problems when there's a media failure with the online redo logs. Therefore it's important that you know
how to diagnose and troubleshoot any issues that arise. Failures with the online redo logs are rare, but when they do
happen, you'll now be much better prepared to resolve any complications in an efficient and effective manner.
