Re: Rebooted servers and then ASM does not bring up
Date: Wed, 26 Mar 2008 18:58:58 +1100 (EST)
Coincidentally it was the FRA (FLASH_DG) in my case too. Also the customer who initially hit the problem for which the bug was logged also had the corruption in their FRA. So I did what you did and just lost some archivelogs, some flashback logs and the BCT file. You have to re-create the diskgroup (unless someone from Support can use kfed to repair the corruption)
But I have had other corruptions in the DATA_DG (the diskgroup holding the entire database) in which a restore and recover is the only option assuming you cannot switch to a copy in the FRA.
To avoid these single point of failure we hold a second copy of the database on a NAS mountpoint.
Edgar Chupit <chupit_at_gmail.com> wrote:
Thank you for sharing this information, it's very useful for analyzing current risks.
Can you, please, also share what type of diskgroup have you lost, was it flash recovery area disk group as in our case, or it was a diskgroup with the data? How did you resolved this situation, did you recreated diskgroup and restored/recovered lost datafiles or have you used another approach.
On Tue, Mar 25, 2008 at 11:01 PM, fairlie rego wrote:
> Coincidentally I hit the same issue a couple of weeks ago.
> The corruption is noticed during a reconfiguration triggered when an ASM
> instance joins or leaves the cluster. It is seen in the Active Change
> Directory (file#3) which is the part of the ASM disk group analogous to the
> RDBMS redo stream which is used for instance recovery.
> Fairlie Rego
> Senior Oracle Consultant
> M: +61 402 792 405
-- Best regards, Edgar Chupit callto://edgar.chupit Fairlie Rego Senior Oracle Consultant http://el-caro.blogspot.com/ M: +61 402 792 405 --------------------------------- Get the name you always wanted with the new y7mail email address.. -- http://www.freelists.org/webpage/oracle-lReceived on Wed Mar 26 2008 - 02:58:58 CDT