Dataguard - Failed Switchover

System Specs: Win 2000, Oracle 9.2, Running in High Availability
I am really at a loss. I have been on this problem for almost a week now.
Primary switches over fine.
On Standby I issue the command: alter database commit to switchover to primary with session shutdown
I am getting this error:
ERROR at line 1:
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
I have checked and rechecked the path and existence of these files that are located on the former primary server. They exists! Are they not being found? or Why would they be locked? The former primary is already converted and mounted as standby.
Here is my DBWR trc File content:
*** 2005-06-14 09:41:30.000
*** SESSION ID:(2.1) 2005-06-14 09:41:30.000
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
*** 2005-06-14 09:46:56.000
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
*** 2005-06-14 09:47:48.000
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
*** 2005-06-14 10:03:06.000
ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
ORA-27041: unable to open file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
These are my filename and log convert parameters on the [current stanby to be converted to primary]:
db_file_name_convert='\oracle\oradata\cescati2\standby','\oracle\oradata\cescati'
log_file_name_convert='\oracle\oradata\cescati2\standby','\oracle\oradata\cescati\archive'
I had the path values switched around to:
db_file_name_convert='\oracle\oradata\cescati','\oracle\oradata\cescati2\standby'
log_file_name_convert='\oracle\oradata\cescati\archive','\oracle\oradata\cescati2\standby'
and I kept getting:
ERROR at line 1:
ORA-00344: unable to re-create online log 'E:\ORACLE\ORADATA\CESCATI\REDO01.LOG'
ORA-27040: skgfrcre: create error, unable to create file
OSD-04002: unable to open file
O/S-Error: (OS 3) The system cannot find the path specified.
I dont know what to do next. Does anyone have a clue what I am missing here?

Guys, This is the OMWB forum and you're not likely to get the response you need here. Try the Database forum for this General Database Discussions
Thanks
Barry

Similar Messages

  • Dataguard - Cannot switchover

    System Specs: Win 2000, Oracle 9.2, Running in High Availability
    I am really at a loss. I have been on this problem for almost a week now.
    Primary switches over fine.
    On Standby I issue the command: alter database commit to switchover to primary with session shutdown
    I am getting this error:
    ERROR at line 1:
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
    I have checked and rechecked the path and existence of these files that are located on the former primary server. They exists! Are they not being found? or Why would they be locked? The former primary is already converted and mounted as standby.
    Here is my DBWR trc File content:
    *** 2005-06-14 09:41:30.000
    *** SESSION ID:(2.1) 2005-06-14 09:41:30.000
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
    ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
    ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
    ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
    ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
    ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
    ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    *** 2005-06-14 09:46:56.000
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
    ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
    ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
    ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
    ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
    ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
    ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    *** 2005-06-14 09:47:48.000
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
    ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
    ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
    ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
    ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
    ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
    ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 1 - see DBWR trace file
    ORA-01110: data file 1: 'E:\ORACLE\ORADATA\CESCATI\SYSTEM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 2 - see DBWR trace file
    ORA-01110: data file 2: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 3 - see DBWR trace file
    ORA-01110: data file 3: 'E:\ORACLE\ORADATA\CESCATI\CWMLITE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    *** 2005-06-14 10:03:06.000
    ORA-01157: cannot identify/lock data file 4 - see DBWR trace file
    ORA-01110: data file 4: 'E:\ORACLE\ORADATA\CESCATI\DRSYS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 5 - see DBWR trace file
    ORA-01110: data file 5: 'E:\ORACLE\ORADATA\CESCATI\EXAMPLE01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 6 - see DBWR trace file
    ORA-01110: data file 6: 'E:\ORACLE\ORADATA\CESCATI\INDX01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 7 - see DBWR trace file
    ORA-01110: data file 7: 'E:\ORACLE\ORADATA\CESCATI\ODM01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 8 - see DBWR trace file
    ORA-01110: data file 8: 'E:\ORACLE\ORADATA\CESCATI\TOOLS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 9 - see DBWR trace file
    ORA-01110: data file 9: 'E:\ORACLE\ORADATA\CESCATI\USERS01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 10 - see DBWR trace file
    ORA-01110: data file 10: 'E:\ORACLE\ORADATA\CESCATI\XDB01.DBF'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 11 - see DBWR trace file
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\CESCATI\TABLES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 12 - see DBWR trace file
    ORA-01110: data file 12: 'E:\ORACLE\ORADATA\CESCATI\INDEXES1.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: 'E:\ORACLE\ORADATA\CESCATI\TABLES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 14 - see DBWR trace file
    ORA-01110: data file 14: 'E:\ORACLE\ORADATA\CESCATI\INDEXES2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    ORA-01157: cannot identify/lock data file 15 - see DBWR trace file
    ORA-01110: data file 15: 'E:\ORACLE\ORADATA\CESCATI\UNDOTBS2.ORA'
    ORA-27041: unable to open file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    These are my filename and log convert parameters on the [current stanby to be converted to primary]:
    db_file_name_convert='\oracle\oradata\cescati2\standby','\oracle\oradata\cescati'
    log_file_name_convert='\oracle\oradata\cescati2\standby','\oracle\oradata\cescati\archive'
    I had the path values switched around to:
    db_file_name_convert='\oracle\oradata\cescati','\oracle\oradata\cescati2\standby'
    log_file_name_convert='\oracle\oradata\cescati\archive','\oracle\oradata\cescati2\standby'
    and I kept getting:
    ERROR at line 1:
    ORA-00344: unable to re-create online log 'E:\ORACLE\ORADATA\CESCATI\REDO01.LOG'
    ORA-27040: skgfrcre: create error, unable to create file
    OSD-04002: unable to open file
    O/S-Error: (OS 3) The system cannot find the path specified.
    I dont know what to do next. Does anyone have a clue what I am missing here?

    Guys, This is the OMWB forum and you're not likely to get the response you need here. Try the Database forum for this General Database Discussions
    Thanks
    Barry

  • Dataguard Post Switchover issue

    Hi All,
    OS:AIX
    DB:11.2.0.3
    I have just performed the switcover from my primary to standby database. The switchover was smooth but the archives are not getting shipped and applied on the new DR. I have checked the process and found that the RFS process is not up. Upon further checking I have found that the alert of my new DR is giving me this line
    Resetting standby activation ID 0 (0x0)
    Please let me know what does this indicates
    Regards

    The message Resetting standby activation ID 0 (0x0)" is a normal message after switchover. It hard to think about a problem with so little details. Check this metalink note, this might help. There was also a similar kind of bug but in 10.2.0.4
    11.2 Data Guard Physical Standby Switchover Best Practices using SQL*Plus (Doc ID 1304939.1)
    There was also a similar kind of bug but in 10.2.0.4.  Workaround is to reboot the database. You can try rebooting the database. It might fix the issue.
    Bug 5476236 - RFS logminer client inoperative after physical standby switchover to primary (Doc ID 5476236.8)

  • Dataguard failed archivelog updates

    Hi all,
    11.2.0.1
    Aix 6.1
    We usually encountered archivelog failure to update the standby database due to voluminous transaction during batch time.
    These usually happened during paydays every 15th or 30th of the month. The voluminous acrhives can not accommodated
    by the network bandwidth so we manually transfer it and apply to the physical standby database.
    Can you share me your scripts that handles this situation?  Someone advised to create a script that checks if acrhive log gaps
    is > 10 . Then zip all the gaps archivelogs and ftp it to the standby server, and unzip, and then apply.
    I am not good in writing scripts and I am also afraid that I might mess the process and might delete the logs erroneously.
    By the way how do you count if gaps is > 10? Can it be queried in the database views?
    Please share your scripts....
    Thanks,
    zxy

    yxes2013 wrote:
    Hi all,
    11.2.0.1
    Aix 6.1
    We usually encountered archivelog failure to update the standby database due to voluminous transaction during batch time.
    These usually happened during paydays every 15th or 30th of the month. The voluminous acrhives can not accommodated
    by the network bandwidth so we manually transfer it and apply to the physical standby database.
    Can you share me your scripts that handles this situation?  Someone advised to create a script that checks if acrhive log gaps
    is > 10 . Then zip all the gaps archivelogs and ftp it to the standby server, and unzip, and then apply.
    I am not good in writing scripts and I am also afraid that I might mess the process and might delete the logs erroneously.
    By the way how do you count if gaps is > 10? Can it be queried in the database views?
    Please share your scripts....
    Thanks,
    zxy
    If you are incapable to do your job, then resign & find a job you are qualified to do.
    why do you expect us to do YOUR job for YOU?
    You get paid to produce such items. We don't!
    All we get from you are lies, mis-truths, & whines.

  • GoldenGate and DataGuard

    Hi,
    How do I integrate GoldenGate with DataGuard when there is failover / switchover..?
    What I mean is that it is not enough just to start the golden gate capture and datapump with the original parameters on the dr site...

    Have you looked at:
    Implementing GoldenGate for DataGuard fail overs (Doc ID 1195995.1) ?
    Good luck,
    -joe

  • Dataguard terms

    hi,
    i am beginner,
    can you explain me dataguard terms
    switchover, failover, physical standby, logical standby , broker etc
    i googled, but i couldnt understand exactly
    thanks in advance.
    pa1

    sachinpawan wrote:
    hi,
    i am beginner,
    can you explain me dataguard terms
    switchover, failover, physical standby, logical standby , broker etcRefer for switchover/failover
    http://www.oracle.com/technetwork/database/features/availability/maa-wp-10gr2-switchoverfailoverbest-128455.pdf
    Refer for logical vs physical
    http://www.orafaq.com/node/957

  • Query on Changing the IP address for Primary and Standby.

    Dear All,
    I have to change the IP address for my Primary system. It is in windows environment with Oracle failsafe.
    i am using the dataguard for switchover process. I changed the IP address in all the files like listener and TNS names and after that i mounted the database and checked the dataguard configuration.
    DGMGRL> show configuration giving success. my problem is when i executed the show database verbose primary_database. it is showing the old IP address in static connect Identifier.
    how to change the IP in static connect Identifier? i updated all the files properly with new IP, but still facing this. will it affect any thing during switchover?
    Thanks.

    Hello;
    The simple solution is remove broker and set it up again.
    How to Safely Remove a Data Guard Broker Configuration (Doc ID 261336.1)
    Best Regards
    mseberg

  • WLC restarting on its own.

    Hi all,
    We've got a pair of WiSMs installed in our Cat6K, running VSS.
    From time to time, the primary WiSM will suddenly fail and secondary will take over.
    Unfortunately when the secondary takes over, NO APs will associate with the WLC. What is the reason? And why would the WiSM just suddenly fail on its on?
    Running version 7.4.121.0 for both, in AP SSO redundancy.
    Switchover History[9]:
    Previous Active = 172.24.x.x, Current Active = 172.24.x.x
    Switchover Reason = Active controller failed, Switchover Time = Wed Jan 28 22:26:54 2015
    Switchover History[10]:
    Previous Active = 172.24.x.x, Current Active = 172.24.x.x
    Switchover Reason = User initiated, Switchover Time = Wed Jan 28 22:35:45 2015
    edit : I can verify that after the secondary WiSM takes over, the licenses also gets adopted by the secondary, but no APs will associate.

    There are multiple BUGs which you can refer :
    https://tools.cisco.com/bugsearch/bug/CSCuo94185
    Symptom:
    WiSM2 on code 7.4.121.0 in HA SSO crashes causing the controllers to constantly fail over and fail back between active and standby controllers.
    Crash seen due to Task Name: nmspRxServerTask
    System Stack
    Frame 0: 0x10012c20 create_crash_dump+7156
    Frame 1: 0x10011a18 create_crash_dump+2540
    Frame 2: 0x10007ab8 sigsegv_handler+6168
    Frame 3: 0x45d803b0 license_xos_thread_create+871837312
    Frame 4: 0x11bdab48 MD5_Update+168
    Frame 5: 0x11bae424 tls1_mac+340
    Frame 6: 0x11baafb0 ssl3_read_bytes+1624
    Frame 7: 0x11ba7f90 ssl3_read+120
    Frame 8: 0x1029a638 doSSLRecvLoop+464
    Frame 9: 0x1029aff0 NetReceiveLoop+424
    Frame 10: 0x1029b3dc locpRxSocket+540
    Frame 11: 0x10b0e858 osapiTaskAppKeySelfSet+304
    Frame 12: 0x120292b0 license_xos_thread_create+2211200
    Frame 13: 0x12089c4c license_xos_thread_create+2606876
    Conditions:
    WiSM2 in HA SSO on code 7.4.121.0
    Workaround:
    None.
    Controller reboots and comes up on its own
    Further Problem Description:
    This is a hospital network
    Issue was first noticed when customer tried to restart services on the primary MSE in the network (MSE in HA)
    This caused a flood of error messages on the controller (error logs attached). It took about two hours for MSEs to come up and stabilize. Shortly after this the active controller crashed, failing over to standby. After some time, the standby WLC crashed failing back to active
    Customer setup has 4 WiSM2's in HA SSO and crash has occured multiple times on two of the controller pairs.
    https://tools.cisco.com/bugsearch/bug/CSCui35807

  • Deleting standby old redologs when make a backup with rman

    Hello friends,
    I like to know how to use the commando delete noprompt obsolete with the standby database using rman, if I use rman says cant use that command with a standby db using dataguard, I switchover to a primary and then lauch the command but always is the same message on RMAN.
    How I can use rman to make a backup and then delete old´s log?, I have no problem with the primary DB, the hard disk is filling with old logs on the standby side and i dont know how to delete in the better place like rman does with the primary with the command delete noprompt obsolete.
    Thanks.

    Hi!
    In the primary database You must continue with Your backup routine, using rman ( backuping archives and then deleting it)
    On the standby database You may use this script to delete applied archived redo logs.
    #!/bin/ksh
    export ORACLE_SID=<SID OF STBY DATABASE>
    role=`
    echo "set echo off";
    echo "set feedback off ";
    echo "set pages 0";
    echo "set head off";
    echo 'select DATABASE_ROLE from v$database;'
    echo "exit";
    } | sqlplus -s '/ as sysdba'
    `
    if [ "$role" = 'PHYSICAL STANDBY' ]; then
    echo "set echo off";
    echo "set feedback off ";
    echo "set pages 0";
    echo "set head off";
    echo "select thread#,sequence# ";
    echo 'from v$archived_log';
    echo "where standby_dest = 'NO' and deleted = 'NO' and APPLIED = 'YES';";
    echo "exit";
    } | sqlplus -s '/ as sysdba' | while read line
    do
    thread=`echo "$line"|awk '{print $1}'`
    sequence=`echo "$line"|awk '{print $2}'`
    echo "crosscheck archivelog sequence $sequence thread $thread;"
    echo "delete noprompt archivelog sequence $sequence thread $thread;"
    done | rman target /
    else
    echo "database not a physcial standby"
    fi
    Regards,
    Cerreia
    Edited by: ecerreia on Sep 22, 2009 2:18 PM

  • Dataguard Broker - Swithover failed

    I have a two node RAC(n1,n2) with one physical standby(n3)
    I have enabled dataguard broker and did a swithover with one instance up in RAC(n1 up)
    Swithover and switchback have worked fine.
    But when trying to do a swithover from the second RAC(n2 up) node it failed and now all the db's are in standby mode.
    When tyring to bring up the RAC instances, alert log shows as standby instances.
    Physical Standby Database mounted.
    Completed: ALTER DATABASE MOUNT
    ALTER DATABASE OPEN
    From sql:
    SQL> select switchover_status from v$database;
    SWITCHOVER_STATUS
    SESSIONS ACTIVE
    On standby:
    SQL> select switchover_status from v$database;
    SWITCHOVER_STATUS
    TO PRIMARY
    Has anyone come accross this situation? How to bring it back to the Primary instance mode?

    On-Standby
    1. alter database commit to switchover to physical standby with session shutdown;
    2. shutdown immediate;
    3. startup nomount;
    4. alter database mount standby database;
    5. alter system set log_archive_dest_state_2=defer;
    6. recover managed standby database disconnect;
    On-Primary
    1. alter database commit to switchover to primary;
    2. alter system set log_archive_dest_stat_2=enable;
    3. shutdown immediate;
    4. startup;

  • Switchover to physical standby failed

    Hi gurus,
    Could anyone pls help for this issue, i'm working on oracle 9i dataguard in solaris box. we succesully switchover our physical standby to primary but when tried to bring back again to physical standby it is throwing an error
    SQL> alter database commit to switchover to physical standby;
    alter database commit to switchover to physical standby
    ERROR at line 1:
    ORA-16014: log 1 sequence# 91775 not archived, no available destinations
    ORA-00312: online log 1 thread 1: '/oracle/u07/oradata/odb/redo_1a.log'
    ORA-00312: online log 1 thread 1: '/oracle/u08/oradata/odb/redo_1b.log'
    ORA-00312: online log 1 thread 1: '/oracle/u09/oradata/odb/redo_1c.log'
    Please advice
    regards,
    shaan

    Hi,
    There is already a thread which you opened Up you can reply back in that..
    switchover to physical standby failed
    - Pavan Kumar N

  • RAC Dataguard Switchover timing taking more than expected time

    I have Dataguard setup in RAC environment and my dataguard is also configured and it is working fine.
    Our goal is to do the switchover using DGMGRL withing the 5 minutes. We have followed the proper setup and MAA tuning document and everything is working fine, Just the switchover timeing is 8 to 10 minutes. which varies depending on some parameters but not meeting our goal of less than 5 minutes.
    The only observation that we have seen is as follow
    After switchover to <db_name> comman in DGMGRL
    1) it will shutdown abort the 2nd instance
    2) transfter all the archivelog ( using LGWR in ASYNC mode) of instance 1
    3) Now it looks for the archive log of 2nd instance, this steps take time upto 4 minutes
    we do not know why it takes that much time and how to tune this??
    4) Now converts primary to standby
    5) Now starts the old standby as new primary
    here All steps are tunined except the step 3, that where our lot of time is going any Idea or explanation
    why it takes such a long time to find the exact archive log 2nd instance (Aborted) to transfer to standby site?
    Can any one give explanation or solution to tune this???
    Regards
    Bhushan

    Hi Robert,
    I am on 10.2.0.4 and we have used "MAA_WP_10gR2_DataGuardNetworkBestPractices.pdf", which is available on oracle site.
    Here are by configuration details
    GMGRL> connect sys@dv01aix
    Password:
    Connected.
    DGMGRL> show configuration;
    Configuration
    Name: dv00aix_dg
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    dv00aix - Physical standby database
    dv01aix - Primary database
    Current status for "dv00aix_dg":
    SUCCESS
    DGMGRL> show database verbose dv00aix
    Database
    Name: dv00aix
    Role: PHYSICAL STANDBY
    Enabled: YES
    Intended State: ONLINE
    Instance(s):
    dv00aix1 (apply instance)
    dv00aix2
    Properties:
    InitialConnectIdentifier = 'dv00aix'
    ObserverConnectIdentifier = ''
    LogXptMode = 'ASYNC'
    Dependency = ''
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '4'
    ReopenSecs = '300'
    NetTimeout = '60'
    LogShipping = 'ON'
    PreferredApplyInstance = 'dv00aix1'
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'AUTO'
    ArchiveLagTarget = '900'
    LogArchiveMaxProcesses = '5'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = ''
    LogFileNameConvert = '+SPARE1/dv01aix/,+SPARE/dv00aix/'
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName(*)
    SidName(*)
    LocalListenerAddress(*)
    StandbyArchiveLocation(*)
    AlternateLocation(*)
    LogArchiveTrace(*)
    LogArchiveFormat(*)
    LatestLog(*)
    TopWaitEvents(*)
    (*) - Please check specific instance for the property value
    Current status for "dv00aix":
    SUCCESS
    DGMGRL> show database verbose dv01aix
    Database
    Name: dv01aix
    Role: PRIMARY
    Enabled: YES
    Intended State: ONLINE
    Instance(s):
    dv01aix1
    dv01aix2
    Properties:
    InitialConnectIdentifier = 'dv01aix'
    ObserverConnectIdentifier = ''
    LogXptMode = 'ASYNC'
    Dependency = ''
    DelayMins = '0'
    Binding = 'OPTIONAL'
    MaxFailure = '0'
    MaxConnections = '4'
    ReopenSecs = '300'
    NetTimeout = '60'
    LogShipping = 'ON'
    PreferredApplyInstance = 'dv01aix1'
    ApplyInstanceTimeout = '0'
    ApplyParallel = 'AUTO'
    StandbyFileManagement = 'AUTO'
    ArchiveLagTarget = '0'
    LogArchiveMaxProcesses = '2'
    LogArchiveMinSucceedDest = '1'
    DbFileNameConvert = '+SPARE/dv00aix/, +SPARE1/dv01aix/'
    LogFileNameConvert = '+SPARE/dv00aix/,+SPARE1/dv01aix/'
    FastStartFailoverTarget = ''
    StatusReport = '(monitor)'
    InconsistentProperties = '(monitor)'
    InconsistentLogXptProps = '(monitor)'
    SendQEntries = '(monitor)'
    LogXptStatus = '(monitor)'
    RecvQEntries = '(monitor)'
    HostName(*)
    SidName(*)
    LocalListenerAddress(*)
    StandbyArchiveLocation(*)
    AlternateLocation(*)
    LogArchiveTrace(*)
    LogArchiveFormat(*)
    LatestLog(*)
    TopWaitEvents(*)
    (*) - Please check specific instance for the property value
    Current status for "dv01aix":
    SUCCESS
    DGMGRL>
    log_archive_dest_2 string service="(DESCRIPTION=(ADDRESS
    _LIST=(ADDRESS=(PROTOCOL=TCP)(
    HOST=*****-vip0)(PORT=1527))
    )(CONNECT_DATA=(SERVICE_NAME=d
    v00aix_XPT)(INSTANCE_NAME=dv00
    aix1)(SERVER=dedicated)))",
    LGWR ASYNC NOAFFIRM delay=0 O
    PTIONAL max_failure=0 max_conn
    ections=4 reopen=300 db_uniq
    ue_name="dv00aix" register net
    NAME TYPE VALUE
    timeout=60  validfor=(online
    logfile,primaryrole)
    NAME TYPE VALUE
    fal_client string (DESCRIPTION=(ADDRESS_LIST=(AD
    DRESS=(PROTOCOL=TCP)(HOST=*****
    -vip0)(PORT=1527)))(CONNECT
    DATA=(SERVICENAME=dv01aix_XP
    T)(INSTANCE_NAME=dv01aix1)(SER
    VER=dedicated)))
    fal_server string (DESCRIPTION=(ADDRESS_LIST=(AD
    DRESS=(PROTOCOL=TCP)(HOST=*****
    -vip0)(PORT=1527))(ADDRESS=
    (PROTOCOL=TCP)(HOST=*****-vi
    p0)(PORT=1527)))(CONNECT_DATA=
    (SERVICE_NAME=dv00aix_XPT)(SER
    VER=dedicated)))
    db_recovery_file_dest string +SPARE1
    db_recovery_file_dest_size big integer 100G
    recovery_parallelism integer 0
    fast_start_parallel_rollback string LOW
    parallel_adaptive_multi_user boolean TRUE
    parallel_automatic_tuning boolean FALSE
    parallel_execution_message_size integer 2152
    parallel_instance_group string
    parallel_max_servers integer 8
    parallel_min_percent integer 0
    parallel_min_servers integer 0
    parallel_server boolean TRUE
    parallel_server_instances integer 2
    parallel_threads_per_cpu integer 2
    recovery_parallelism integer 0

  • Win 2003 Cluster + Oracle Fail Safe + Dataguard (physical & Logical)

    Hello,<br>
    <br>
    It´s my first post (sorry for my bad english)...I am mounting a high availability solution for test purpose. For the moment i mount the following and runs ok, but i´ve a little problem with the logical database:<br>
    <br>
    Configuration<br>
    ESX Server 2.0 with this machines:<br>
    Windows 2003 Cluster (Enterprise Edition R2, 2 nodes)<br>
    * NODE 1 - Oracle 10gR2 + Patch 9 + Oracle Fail Safe 3.3.4<br>
    * NODE 2 - Oracle 10gR2 + Patch 9 + Oracle Fail Safe 3.3.4<br>
    c:/Windows Software<br>
    e:/Oracle Software/ (pfile -> R:/spfile)<br>
    <br>
    Virtual SAN<br>
    * Datafile, Redos.. are in Virtual SAN.<br>
    R:/ Datafiles & Archivers & dump files & spfile<br>
    S:/ , T:/ ,U:/ -> Redos<br>
    V:/ Undo<br>
    <br>
    Data Guard<br>
    * NODE3 Physical Database<br>
    * NODE4 Logical Database<br>
    <br>
    The Oracle Fail Safe and windows cluster run OK, the switchs... <br>
    The physical database runs OK... (redo aply, switchover, failover, all ok) but the logical receives the redos ok but it has a problem when goes to apply the redo.<br>
    <br>
    The error is the following:<br>
    ORA-12801: error señalizado en el servidor P004 de consultas paralelas<br>
    ORA-06550: linea 1, columna 536:<br>
    PLS-00103: se ha encontrado el simbolo "," cuando se esperaba uno de los siguientes:<br>
    (- + case mod new not null <an identifier>
    <a double-quoted delimited-identifier><a bind variable><avg count current exists max min prior sql stddev sum variance execute forall merge time timestamp interval date <a string literal with character set specification><a number> > a single-quoted SQL string> pipe <an alternatively quoted string literal with character set specification> <an alternativel.<br>
    update "SYS"."JOB$" set "LAST_DATE"=TO_DATE('11/09/07','DD/MM/RR'),<br>
    <br>
    This sql statement i saw in dba_logstdby_events and was joined with the error in alert log and dba_logstdby_events.<br>
    <br>
    I´m a bit lost with this error. I don´t understand why the logical database can´t start to apply the redos received from primary database.<br>
    <br>
    The database has two tables with two columns one integer and the other a varchar2(25). She hasn´t rare types of columns.<br>
    <br>
    Thanks a lot for any help,<br>
    Roberto Marotta<br>

    I recreate the logical database OK, no problem, no errors.<br>
    <br>
    The redo aply run ok. I have done logfile switch in primary database and they were applied in logical and standby databases. But...<br>
    <br>
    When I created a tablespace in primary database when i did a switch logfile in primary the changes transfers ok to standby database, but to logical NO!!!, the redo are in they path in logical ok, but when the process tried to apply, reports me the same error.<br>
    <br>
    SQL> select sequence#, first_time, next_time, dict_begin, dict_end, applied from dba_logstdby_log order by 1;<BR>
    <BR>
    SEQUENCE# FIRST_TI NEXT_TIM DIC DIC APPLIED<BR>
    --------- -------- -------- --- --- -------<BR>
    138 14/09/07 14/09/07 NO NO CURRENT<BR>
    139 14/09/07 14/09/07 NO NO CURRENT<BR>
    <br>
    SQL> select event_time, status, event from dba_logstdby_events order by event_time, timestamp, commit_scn;<br>
    <br>
    14/09/07<br>
    ORA-16222: reintento automatico de la base de datos logica en espera de la ultima accion<br>
    14/09/07<br>
    ORA-16111: extraccion de log y configuracion de aplicacion<br>
    14/09/07<br>
    ORA-06550: linea 1, columna 536:<br>
    PLS-00103: Se ha encontrado el simbolo "," cuando se esperaba uno de los siguientes:<br>
    ( - + case mod new not null <an identifier><br>
    <a double-quoted delimited-identifier> <a bind variable> avg<br>
    count current exists max min prior sql stddev sum variance<br>
    execute forall merge time tiemstamp interval date<br>
    <a string literal with character set specification><br>
    <a number><a single-quoted SQL string> pipe
    <an alternatively-quoted string literal with charactert set specificastion><br>
    <an alternativel<br>
    update "SYS"."JOB$" set "LAST_NAME" = TO_DATE('14/09/07','DD/MM/RR'),<br>
    <br>
    The alert.log report the same message that the dba_logstdby_events view.<br>
    <br>
    Any idea¿?<br>
    <br>
    I´m a bit frustrated. It´s the third time that recreate the logical database OK and reproduce the same error when i create a tablespace in primary database, and i haven´t got any idea because of that.

  • DataGuard Continuing to Fail - ORA-16766, ORA-01237 - OPSCODE 17.4

    DataGuard Broker failing every few hours ... have to stop and restart. ORA-16766, ORA-01237. I cannot find any information on the failure apply recovery marker (opscode 17.4).
    The thought would be from the errors that the volume is out of space, we are running NETAPP and the volumes do auto expand but when I looked the volume it was only at 44% full at 1600 yesterday when I restarted and today I it is at 28%.
    These are BIGFILE tablespace. I have restarted multiple times and keep getting the same errors daily and I just end up restarting and everything works again w/o intervention.
    I don't want to daily have to check dataguard. If I don't run dg and just run "recover standby database until cancel auto" ... it just keeps going w/o issue, any ideas on the problem?
    Please advise:
    OS: Solaris 5.10
    RDBMS:Oracle 11.2.0.2 64 bit
    OMF
    BIGFILE Tablespaces
    VLDB - Standby DG Database
    Created via RMAN Duplicate Database
    Dataguard Alert shows the original startup information, does some health check ... becomes quite for a few hours and then I start seeing the Redo Apply is stopped.
    2011-09-28 18:45:20.824 00000000 24342 Operation HEALTH_CHECK canceled during phase 1, error = ORA-16766
    2011-09-28 18:46:20.929 DMON: HEALTH CHECK ERROR: ORA-16766: Redo Apply is stopped
    Alert Log showing 1237 on the extend but volume is not out of space ... bigfile tablespace. I cannot find any information on the failure apply recovery marker (opscode 17.4):
    Errors in file /u02/d002/oracle/bdump/diag/rdbms/DBUNIQNAME/DBNAME/trace/DBNAME_pr00_6331.trc:
    ORA-01237: cannot extend datafile 670
    ORA-01110: data file 670: '/u07/d101/oracle/DBUNIQNAME/datafile/o1_mf_ftk_31_c_784ql3gh_.dbf'
    Managed Standby Recovery not using Real Time Apply
    Wed Sep 28 18:43:57 2011
    Recovery interrupted!
    Wed Sep 28 18:44:29 2011
    Archived Log entry 2805 added for thread 1 sequence 135638 ID 0x249d4159 dest 1:
    Wed Sep 28 18:44:41 2011
    Recovery stopped due to failure in applying recovery marker (opcode 17.4).
    Datafiles are recovered to a consistent state at change 22941677700 but controlfile could be ahead of datafiles.
    Wed Sep 28 18:44:42 2011
    MRP0: Background Media Recovery process shutdown (DBNAME)
    Wed Sep 28 18:46:04 2011
    Trace FIle showing the same problem as the alert ...
    Started Parallel Media Recovery
    *** 2011-09-28 16:14:52.074 4265 krsh.c
    Managed Standby Recovery starting Real Time Apply
    *** 2011-09-28 18:43:08.759 4265 krsh.c
    MRP0: Background Media Recovery terminated with error 1237
    ORA-01237: cannot extend datafile 670
    ORA-01110: data file 670: '/u07/d101/oracle/DBUNIQUNAME/datafile/o1_mf_ftk_31_c_784ql3gh_.dbf'
    *** 2011-09-28 18:43:08.779 4265 krsh.c
    Managed Standby Recovery not using Real Time Apply----- Redo read statistics for thread 1 -----
    Read rate (ASYNC): 54581570Kb in 8888.95s => 6.00 Mb/sec
    Total redo bytes: 54636866Kb Longest record: 81Kb, moves: 49633/139704932 moved: 130Mb (0%)
    Longest LWN: 118127Kb, reads: 45176
    Last redo scn: 0x0005.576e3884 (22941677700)
    Change vector header moves = 18603031/273716057 (6%)
    *** 2011-09-28 18:43:08.816
    Media Recovery drop redo thread 1
    *** 2011-09-28 18:43:56.660
    Completed Media Recovery
    *** 2011-09-28 18:44:00.869
    Checking to start in-flux buffer recovery from SCN 5.1465762230 to SCN (non-inclusive) 5.1466841220
    Influx recovery found in-flux buffers
    *** 2011-09-28 18:44:00.874
    Influx Media Recovery add redo thread 1
    *** 2011-09-28 18:44:36.493
    Resized overflow buffer to 52335K (for 52335K LWN)
    *** 2011-09-28 18:44:38.887
    Resized overflow buffer to 63165K (for 63165K LWN)
    *** 2011-09-28 18:44:41.686
    Managed Recovery: Not Active posted.

    It appears to be a problem that occurs every time an OMF file wants to extend that it kills the dataguard process irrelvant of what volume the file is on.

  • Need Help Understanding GoldenGate DR (Standby) Switchover/Fail-over with DBFS and Fuser

    Hi, Gurus. We are about to embark on GoldenGate DR failover / switchover configuration and testing using DBFS and Fuser. The details are described in Doc ID 1436913.1 and 1322547.1.
    I know the basics of GoldenGate and Oracle DataGuard. But DBFS and Fuser are new concepts to me. I need some help.
    1) Is GoldenGate installed in a DBFS partition on the primary? SO, DBFS has to be configured before it is installed?
    2) Are these GoldenGate files and directories (ggsci, /dirdat, /dirrpt, etc) visible from UNIX level? Will I be able to navigate in the GG mount or is it a closed file system like ASM?
    3) DBFS has to be a part of database. So, what happens if primary database crashes and cannot be mounted? My guess DBFS will not start because the database is down. Or does it run outside of database?
    4) Does DBFS store just links to large files in the Oracle database, but the actual GoldenGate binaries files still reside on OS level? Ot they are INSIDE of the database - both GG binaries and trails?
    5) How does GoldenGate replicates itself to standby? Because it is a part of database and primary archivelogs and redo logs send the changes to the standby? Or it ONLY runs until switchover/failover on the primary, but afterward it is simply unmounted from primary and mounted to standby by the oracle OS user and the scripts? Or is there a datapump and extract that send trails to standby and after the failure those trails are simply being used?
    I guess that is my main question. Why do we bother with DBFS at all? We can simply add a standby extract/datapump to the primary. It will send trails to the standby, that will have only manager running. The manager will accept the trails, periodically deleting all older than lets say one week. At the time of failover/switchover we simply use the same queries as in the docs above to find out if standby became the new primary (the failover had occured). If it did, we can use the same script to get SCN from which this new incarnation started , use a shell script to use an obey file to add the replicat starting from that sequence and voila! Why do we need to bother with fuser and cumbersome DBFS at all? Please let me know what I am missing. If there are alternative to this DBFS DR GoldenGate switchover I would like to use which ever one is the simplest. Thanks.

    Looking at the information provided by you. You have created a flashback restore point and then activated your standby database. As you have flashback restore you can flashback your current primary database(old standby) to standby mode but all your changes made on your database will be lost. And you have not done a switchover. you have activated your standby.

Maybe you are looking for

  • "Buying on behalf" get an error

    Hi, When I'm using the "shop on behalf" procedure, I get the following error after I add an item to the shopping cart: "Business Partner does not exist" message number R1 201. Any idea? Than you, Joseph

  • ILife for the classroom

    Hi all, I'm not real sure which discussion area to post this in, so iMovie is the lucky winner I'm a 4th grade teacher with hopes of using iLife in the classroom. I'm also a musician. What I am NOT is a fluent tech person. I'd like to purchase a camc

  • How to attach screen shot in OTN ?

    Dear Friend, How to attach screen shot in OTN. Thanks

  • How to execute preflight profile using Acrobat Javascript

    Execute a pre-flight profile using acrobat javascript and  call that function in VB.Net.

  • Web Site directories getting too big

    The images folder on my site now contains over 3,000 images of wild flowers and related stuff. These images appear on the relevant but separate web pages of which there are now over 2,000. You find your way round all this using various indexes which