I once saw a problem like this on an AIX box.  The SA was doing full
backups with the Oracle instance up but no users logged on.  One
controlfile would go out of synch.  Not sure if that's helpful to you.



                                                                                       
    
                    "Fink, Dan"                                                        
    
                    <Dan.Fink            To:     Multiple recipients of list ORACLE-L  
    
                    @mdx.com>            <[EMAIL PROTECTED]>                        
    
                    Sent by: root        cc:                                           
    
                                         Subject:     ORA-214 on VCS Failover          
    
                                                                                       
    
                    07/10/2002                                                         
    
                    03:35 PM                                                           
    
                    Please                                                             
    
                    respond to                                                         
    
                    ORACLE-L                                                           
    
                                                                                       
    
                                                                                       
    





During Veritas  Cluster Failover (Solaris8, Oracle9i, EMC) testing we
encountered the following  scenario...and it has me stumped!

Database failed over  to secondary server...operates without error database
up and  running
Database failed back  to primary server...ORA-214 signalled during ALTER
DATABASE  MOUNT
This indicates that  we have a file that is out of sync (as if we had
restored an old version and not  done a recovery).
In looking at the  database files, our 3rd control file had a time stamp
from the first failover,  where all the other active files (excepting
inactive redo logs) had a timestamp  from the second failover. Residing on
the same disk as the out of sync control  file was the file to the users
tablespace (users01.dbf) that had a timestamp of  the second failover. Once
we replaced the bad controlfile with a good one, the  database could be
mounted and opened.

So, if Oracle could  not read all of the control files, why did it even
update the first one? If it  could not read all 3 controlfiles, why were
the individual database files  touched?
My understanding of  the startup stages don't offer any explanation for
this behaviour. Perhaps it is  an Oracle bug...




-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Thomas Day
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to