controlfile ooppppsss

GM,

 

10.2.0.3 / 8-node cluster with ASM on a 3par and OMF.

 

I moved the controlfile last night and made a mistake in the spfile. I ommited 
a "/" in the control_files parameter like so:

 

+DG2/orms/controlfilecurrent.256.696390005  <  should be 
+DG2/orms/controlfile/current.256.696390005

 

I did not notice it at the time and the database with all instances came up 
without issue. ASMCMD displays the controlfile in the correct directory 
structure; but I cannot see "+DG2/orms/controlfilecurrent.256.696390005". The 
original controlfile in DG1 did not move. I used it to create the new one via 
RMAN - "restore controlfile to '+DG2' from 
'+DG1/orms/controlfile/current.314.684341227';" methodology. DG2 is a new 
diskgroup with nothing else on it at the moment and ASM opened it correctly and 
the RDBMS database knows of it in the alert log. 

 

I intend to correct this during the next available outage. 

 

I guess my question is "Is ASM and OMF smart enough to know what I was 
intending?" Am I running with 1 controlfile (DG1) or 2?

As I stated, the cluster came up nicely and there are no subsequent errors. 

 

_________________________________________________________________
Get back to school stuff for them and cashback for you.
http://www.bing.com/cashback?form=MSHYCB&publ=WLHMTAG&crea=TEXT_MSHYCB_BackToSchool_Cashback_BTSCashback_1x1

Other related posts:

  • » controlfile ooppppsss - Martin Brown