"To avoid these single point of failure we hold a second copy of the database on a NAS mountpoint."
eh ?So you still had to go out and buy that expensive NAS appliance, because ASM might corrupt the database !
Hemant K Chitale At 03:58 PM Wednesday, fairlie rego wrote:
Hi,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.Thanks Fairlie
Hemant K Chitale http://hemantoracledba.blogspot.com -- http://www.freelists.org/webpage/oracle-l