controlfile ooppppsss

From: Martin Brown <>
Date: Tue, 1 Sep 2009 10:29:24 -0400
Message-ID: <SNT107-W406896EB5A5D91875F5EFBC2F10_at_phx.gbl>

GM, / 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.
Received on Tue Sep 01 2009 - 09:29:24 CDT

Original text of this message