Standby ORA-1110

I had an error today identified from alert log the below:
Errors in file /apps/oracle/admin/XPSPERS/bdump/xpsper_mrp0_19602.trc:
ORA-01110: data file 181: '/oradata1/XPS_DATA/XPSPERS/D1_223YMD4_081100305804_0.dbf'
ORA-00372: file 181 cannot be modified at this time
ORA-01110: data file 181: '/oradata1/XPS_DATA/XPSPERS/D1_223YMD4_081100305804_0.dbf'
Thu Jul 14 10:34:56 2011
MRP0: Background Media Recovery process shutdown (XPSPER)
It turned out that I had a couple tablespaces in read only mode on the physical standby. I'm not sure how it happen or what was sent over from the primary. But to change the tablespace from read only to read write on the standby, I would need to shutdown the standby and open the database in read only before I could make the DDL changes. I'm more concerned if the DDL changes on the primary should get applied on the standby as well automatically?

Below is what was extracted from the trace file.
Media Recovery Log /archive/flash_recovery_area/XPSPERS/archivelog/2011_07_14/o1_mf_1_19431_71woftly_.arc
*** 2011-07-14 10:34:53.006 64208 kcrr.c
MRP0: Background Media Recovery terminated with error 1110
ORA-01110: data file 181: '/oradata1/XPS_DATA/XPSPERS/D1_223YMD4_081100305804_0.dbf'
ORA-00372: file 181 cannot be modified at this time
ORA-01110: data file 181: '/oradata1/XPS_DATA/XPSPERS/D1_223YMD4_081100305804_0.dbf'
*** 2011-07-14 10:34:53.047 64208 kcrr.c
Managed Standby Recovery not using Real Time Apply
----- Redo read statistics for thread 1 -----
Read rate (ASYNC): 171816619Kb in 1857461.96s => 0.09 Mb/sec
Total physical reads: 171875983Kb
Longest record: 735Kb, moves: 0/130781217 (0%)
Change moves: 63847378/189220050 (11%), moved: 146322Mb
Longest LWN: 7501Kb, moves: 36560/873724 (4%), moved: 32256Mb
Last redo scn: 0x0000.0979b1fd (158970365)
*** 2011-07-14 10:34:53.047
Media Recovery drop redo thread 1
*** 2011-07-14 10:34:56.012 1180 krsm.c
Managed Recovery: Not Active posted.
ORA-01110: data file 181: '/oradata1/XPS_DATA/XPSPERS/D1_223YMD4_081100305804_0.dbf'
ORA-00372: file 181 cannot be modified at this time
ORA-01110: data file 181: '/oradata1/XPS_DATA/XPSPERS/D1_223YMD4_081100305804_0.dbf'
ARCH: Connecting to console port...
*** 2011-07-14 10:34:56.055 64208 kcrr.c
MRP0: Background Media Recovery process shutdown
*** 2011-07-14 10:34:56.055 1180 krsm.c

Similar Messages

  • OS 명령으로 DATAFILE을 삭제한 경우:ORA-1157, ORA-1110

    제품 : ORACLE SERVER
    작성날짜 : 2004-03-08
    OS 명령으로 DATAFILE을 삭제한 경우 : ORA-1157, ORA-1110
    ======================================================
    [주의] 다음의 경우는 system tablespace에 대해서 적용되지 않는다.
    DATABASE RECOVERY에 앞서 ORACLE INSTANCE(즉, ORACLE RDBMS)의 STARTUP
    단계를 우선 살펴보기로 하자.
    첫번째 단계로 INSTANCE를 START시키며, 여기서는 initORACLE_SID.ora
    화일의 파라미터를 참조하여 SGA(SYSTEM GLOBAL AREA)를 할당하고
    백그라운드 프로세스를 START 시킨다.
    두번째 단계로 DATABASE의 MOUNT이며 파라미터 화일에 명시된 CONTROL
    FILE을 오픈한다. CONTROL FILE로부터 DATABASE NAME과 REDO LOG FILE의
    이름을 읽는다.
    세번째 단계로 CONTROL FILE 내의 정보를 이용하여 모든 데이타 화일을
    오픈한다.
    SVRMGR> CONNECT INTERNAL;
    Connected.
    SVRMGR> STARTUP;
    ORACLE instance started.
    Database mounted.
    Database opened.
    Total System Global Area 1913196 bytes
    Fixed Size 27764 bytes
    Variable Size 1787128 bytes
    Database Buffers 65536 bytes
    Redo Buffers 32768 bytes
    RDBMS의 STARTUP 시 문제의 데이타 화일이 CONTROL FILE 정보에서는 존재하지만,
    실제로 O/S 상에서는 존재하지 않으므로 DATABASE OPEN 단계에서 삭제된 데이타
    화일을 OPEN할 수 없다. 따라서 다음과 같은 데이타 화일 오픈에 관련된 에러가
    발생된다 :
    SVRMGR> STARTUP;
    ORACLE instance started
    Database mounted
    ORA-01157 : cannot identify data file 11 - file not found
    ORA-01110 : data file 11 : '/user1/oracle7/dbs/user2.dbf'
    Attempting to dismount database .... Database dismounted
    Attempting to shutdown instance .... ORACLE instance shut down
    DATABASE OPEN 단계에서 CONTROL FILE에서는 ORA-1157 에러에서 나타난
    11번 데이타 화일이 존재하는 것으로 인식하지만, 실제로 O/S 상의 데이타
    화일 (ORA-1110 에러에 명시된 '/user1/oracle7/dbs/user2.dbf' 화일)이
    삭제된 상태이다.
    이러한 경우에는 DATABASE STARTUP 시 STARTUP MOUNT 단계까지 실행한 후,
    문제의 데이타 화일을 OFFLINE시킨 다음 데이타베이스를 오픈한다.
    단, 데이타베이스 오픈이 정상적으로 수행되면 문제가 발생한 데이타 화일을
    포함하고 있는 TABLESPACE를 DROP하지 않을 경우에는 DATABASE STARTUP 시
    항상 데이타 화일의 오픈 단계에서 에러가 발생된다.
    따라서, 문제의 데이타 화일의 OFFLINE과 TABLESPACE의 DROP 전에 반드시 해당
    TABLESPACE를 사용하고 있는 USER의 데이타 백업을 수행해야 한다.
    데이타 화일의 OFFLINE과 관련된 명령은 다음과 같다.
    먼저 SVRMGR을 Line Mode로 기동시킨다.
    $ svrmgrl
    SVRMGR> CONNECT INTERNAL;
    SVRMGR> STARTUP MOUNT;
    ORACLE instance started.
    Database mounted.
    SVRMGR> ALTER DATABASE DATAFILE '/user1/oracle7/dbs/user2.dbf'
    OFFLINE DROP;
    Statement processed.
    SVRMGR> ALTER DATABASE OPEN;
    Statement processed.
    SVRMGR> DROP TABLESPACE tablespace_name INCLUDING CONTENTS;
    Statement processed.
    (이와 같이 offline drop된 datafile을 포함하는 tablespace는 drop하여야 한다.
    이 tablespace에 다른 datafile도 포함되어 있다면 export를 받아낸 후
    tablespace를 drop하고 재생성 후 import하도록 한다.)
    정상적으로 DATABASE가 Open된 후 CONTROL FILE로부터의 데이타베이스
    정보를 갖는 DATA DICTIONARY TABLE인 V$DATAFILE(SYS USER에서 액세스
    가능)의 내용과 데이타베이스 화일에 관한 정보를 가지고 있는 DATA
    DICTIONARY VIEW인 DBA_DATA_FILES(SYSTEM USER)을 조회하면 아래와 같은
    내용을 확인할 수 있다 :
    (1) SQL> SELECT * FROM V$DATAFILE ;
    FILE# STATUS NAME
    9 ONLINE /user1/oracle7/dbs/tools.dbf
    10 ONLINE /user1/oracle7/dbs/user1.dbf
    11 RECOVER /user1/oracle7/dbs/user2.dbf
    (2) SQL> SELECT * FROM DBA_DATA_FILES ;
    FILE_NAME FILE_ID TABLESPACE_NAME STATUS
    /user1/oracle7/dbs/tools.dbf 9 TOOLS AVAILABLE
    /user1/oracle7/dbs/user1.dbf 10 TEST AVAILABLE
    /user1/oracle7/dbs/user2.dbf 11 TEST AVAILABLE

    제품 : ORACLE SERVER
    작성날짜 : 2004-03-08
    OS 명령으로 DATAFILE을 삭제한 경우 : ORA-1157, ORA-1110
    ======================================================
    [주의] 다음의 경우는 system tablespace에 대해서 적용되지 않는다.
    DATABASE RECOVERY에 앞서 ORACLE INSTANCE(즉, ORACLE RDBMS)의 STARTUP
    단계를 우선 살펴보기로 하자.
    첫번째 단계로 INSTANCE를 START시키며, 여기서는 initORACLE_SID.ora
    화일의 파라미터를 참조하여 SGA(SYSTEM GLOBAL AREA)를 할당하고
    백그라운드 프로세스를 START 시킨다.
    두번째 단계로 DATABASE의 MOUNT이며 파라미터 화일에 명시된 CONTROL
    FILE을 오픈한다. CONTROL FILE로부터 DATABASE NAME과 REDO LOG FILE의
    이름을 읽는다.
    세번째 단계로 CONTROL FILE 내의 정보를 이용하여 모든 데이타 화일을
    오픈한다.
    SVRMGR> CONNECT INTERNAL;
    Connected.
    SVRMGR> STARTUP;
    ORACLE instance started.
    Database mounted.
    Database opened.
    Total System Global Area 1913196 bytes
    Fixed Size 27764 bytes
    Variable Size 1787128 bytes
    Database Buffers 65536 bytes
    Redo Buffers 32768 bytes
    RDBMS의 STARTUP 시 문제의 데이타 화일이 CONTROL FILE 정보에서는 존재하지만,
    실제로 O/S 상에서는 존재하지 않으므로 DATABASE OPEN 단계에서 삭제된 데이타
    화일을 OPEN할 수 없다. 따라서 다음과 같은 데이타 화일 오픈에 관련된 에러가
    발생된다 :
    SVRMGR> STARTUP;
    ORACLE instance started
    Database mounted
    ORA-01157 : cannot identify data file 11 - file not found
    ORA-01110 : data file 11 : '/user1/oracle7/dbs/user2.dbf'
    Attempting to dismount database .... Database dismounted
    Attempting to shutdown instance .... ORACLE instance shut down
    DATABASE OPEN 단계에서 CONTROL FILE에서는 ORA-1157 에러에서 나타난
    11번 데이타 화일이 존재하는 것으로 인식하지만, 실제로 O/S 상의 데이타
    화일 (ORA-1110 에러에 명시된 '/user1/oracle7/dbs/user2.dbf' 화일)이
    삭제된 상태이다.
    이러한 경우에는 DATABASE STARTUP 시 STARTUP MOUNT 단계까지 실행한 후,
    문제의 데이타 화일을 OFFLINE시킨 다음 데이타베이스를 오픈한다.
    단, 데이타베이스 오픈이 정상적으로 수행되면 문제가 발생한 데이타 화일을
    포함하고 있는 TABLESPACE를 DROP하지 않을 경우에는 DATABASE STARTUP 시
    항상 데이타 화일의 오픈 단계에서 에러가 발생된다.
    따라서, 문제의 데이타 화일의 OFFLINE과 TABLESPACE의 DROP 전에 반드시 해당
    TABLESPACE를 사용하고 있는 USER의 데이타 백업을 수행해야 한다.
    데이타 화일의 OFFLINE과 관련된 명령은 다음과 같다.
    먼저 SVRMGR을 Line Mode로 기동시킨다.
    $ svrmgrl
    SVRMGR> CONNECT INTERNAL;
    SVRMGR> STARTUP MOUNT;
    ORACLE instance started.
    Database mounted.
    SVRMGR> ALTER DATABASE DATAFILE '/user1/oracle7/dbs/user2.dbf'
    OFFLINE DROP;
    Statement processed.
    SVRMGR> ALTER DATABASE OPEN;
    Statement processed.
    SVRMGR> DROP TABLESPACE tablespace_name INCLUDING CONTENTS;
    Statement processed.
    (이와 같이 offline drop된 datafile을 포함하는 tablespace는 drop하여야 한다.
    이 tablespace에 다른 datafile도 포함되어 있다면 export를 받아낸 후
    tablespace를 drop하고 재생성 후 import하도록 한다.)
    정상적으로 DATABASE가 Open된 후 CONTROL FILE로부터의 데이타베이스
    정보를 갖는 DATA DICTIONARY TABLE인 V$DATAFILE(SYS USER에서 액세스
    가능)의 내용과 데이타베이스 화일에 관한 정보를 가지고 있는 DATA
    DICTIONARY VIEW인 DBA_DATA_FILES(SYSTEM USER)을 조회하면 아래와 같은
    내용을 확인할 수 있다 :
    (1) SQL> SELECT * FROM V$DATAFILE ;
    FILE# STATUS NAME
    9 ONLINE /user1/oracle7/dbs/tools.dbf
    10 ONLINE /user1/oracle7/dbs/user1.dbf
    11 RECOVER /user1/oracle7/dbs/user2.dbf
    (2) SQL> SELECT * FROM DBA_DATA_FILES ;
    FILE_NAME FILE_ID TABLESPACE_NAME STATUS
    /user1/oracle7/dbs/tools.dbf 9 TOOLS AVAILABLE
    /user1/oracle7/dbs/user1.dbf 10 TEST AVAILABLE
    /user1/oracle7/dbs/user2.dbf 11 TEST AVAILABLE

  • Logical standby: ORA-01031: insufficient privileges

    Dear Colleagues,
    Today in my Logical Standby don't apply archivelogs and I see an error in alert.log:
    ORA-26808: Apply process AS01 died unexpectedly.
    ORA-01031: insufficient privileges
    Also I see next logs in trace files:
    h4.
    1)
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Data Mining and Real Application Testing options
    ORACLE_HOME = /ora/Ora11203
    System name: Linux
    Node name: base
    Release: 2.6.18-308.20.1.el5
    Version: #1 SMP Tue Nov 6 04:38:29 EST 2012
    Machine: x86_64
    Instance name: oracle
    Redo thread mounted by this instance: 1
    Oracle process number: 43
    Unix process pid: 16634, image: oracle@base (AS01)
    *** 2013-04-04 16:58:47.062
    *** SESSION ID:(146.16811) 2013-04-04 16:58:47.062
    *** CLIENT ID:() 2013-04-04 16:58:47.062
    *** SERVICE NAME:(SYS$USERS) 2013-04-04 16:58:47.062
    *** MODULE NAME:(Streams) 2013-04-04 16:58:47.062
    *** ACTION NAME:( - Apply Server) 2013-04-04 16:58:47.062
    knasplcr: eager error was not rolled back
    ++ LCR Dump Begin: 0x2b0cf2a6d168 - ddl
    op: 5, Original op: 5, baseobjn: 0, objn: 0, objv: 0
    DF: 0x00000002, DF2: 0x00000010, MF: 0x00020810, MF2: 0x00000000
    PF: 0x00000000, PF2: 0x08000000
    MergeFlag: 0x00, FilterFlag: 0x00
    Id: 0, iotPrimaryKeyCount: 0, numChgRec: 1
    NumCrSpilled: 0
    RedoThread#: 1, rba: 0x0213d7.00023455.01ac
    scn: 0x0002.fc0f8769, (scn: 0x0000.00000000, scn_sqn: 0, lcr_sqn: 0)xid: 0x0019.00e.0007f8d9, parentxid: 0x0019.00e.0007f8d9, proxyxid: 0x0000.000.00000000
    ncol: 0 newcount: 24, oldcount: 0
    LUBA: 0x4.1000ad1.e.0.0
    ++ LCR Dump Begin: 0x59b1afdc8 - commit
    op: 7, Original op: 7, baseobjn: 0, objn: 0, objv: 0
    DF: 0x00000002, DF2: 0x00000010, MF: 0x00220000, MF2: 0x02000000
    PF: 0x00100000, PF2: 0x08040000
    MergeFlag: 0x03, FilterFlag: 0x00
    Id: 3, iotPrimaryKeyCount: 0, numChgRec: 0
    NumCrSpilled: 0
    RedoThread#: 1, rba: 0x0213d7.00023456.0108
    scn: 0x0002.fc0f876b, (scn: 0x0002.fc0f876b, scn_sqn: 1, lcr_sqn: 1)xid: 0x0019.00e.0007f8d9, parentxid: 0x0019.00e.0007f8d9, proxyxid: 0x0000.000.00000000
    ncol: 0 newcount: 0, oldcount: 0
    LUBA: 0x4.1000ad1.e.0.0
    Apply Slave is exiting due to error ORA-1031KSV 1031 error in slave process
    *** 2013-04-04 16:58:47.067
    ORA-01031: insufficient privileges
    OPIRIP: Uncaught error 447. Error stack:
    ORA-00447: fatal error in background process
    ORA-01031: insufficient privileges
    h4.
    2)
    Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
    With the Partitioning, Data Mining and Real Application Testing options
    ORACLE_HOME = /ora/Ora11203
    System name: Linux
    Node name: base
    Release: 2.6.18-308.20.1.el5
    Version: #1 SMP Tue Nov 6 04:38:29 EST 2012
    Machine: x86_64
    Instance name: oracle
    Redo thread mounted by this instance: 1
    Oracle process number: 30
    Unix process pid: 16404, image: oracle@base (LSP0)
    *** 2013-04-04 16:41:58.401
    *** SESSION ID:(294.35251) 2013-04-04 16:41:58.401
    *** CLIENT ID:() 2013-04-04 16:41:58.401
    *** SERVICE NAME:(SYS$BACKGROUND) 2013-04-04 16:41:58.401
    *** MODULE NAME:() 2013-04-04 16:41:58.401
    *** ACTION NAME:() 2013-04-04 16:41:58.401
    knahcapplymain: encountered error=26808
    *** 2013-04-04 16:41:58.401
    dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)
    ----- Error Stack Dump -----
    ORA-26808: Apply process AS02 died unexpectedly.
    ORA-01031: insufficient privileges
    KNACDMP: *******************************************************
    KNACDMP: Dumping apply coordinator's context at 25487cb0
    KNACDMP: Apply Engine # 0
    KNACDMP: Apply Engine name
    KNACDMP: Coordinator's Watermarks ------------------------------
    KNACDMP: Apply High Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Apply Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Recovery Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Fetch Low Watermark = 0002fc0f876b (SCN=0x0002.fc0f876b)
    KNACDMP: Fetch Low Watermark Time = 811857327
    KNACDMP: Oldest SCN = (SCN=0x0000.00000000)
    KNACDMP: Oldest XID =
    KNACDMP: Oldest Create Time = 0
    KNACDMP: Last replicant syncpoint SCN = 0x0000.00000000
    KNACDMP: Last syncpoint at primary SCN = 0x0002.fc0f875f
    KNACDMP: First partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
    KNACDMP: Last partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
    KNACDMP: Last processed = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Conservative pos = 0002fc0f8cb2 (SCN=0x0002.fc0f8cb2)
    KNACDMP: Recovery start pos = (SCN=0x0000.00000000)
    KNACDMP: Recovery high watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Spill LWM = (SCN=0x0000.00000000)
    KNACDMP: Spill LWM Create Time = 0
    KNACDMP: Coordinator's constants -------------------------------
    KNACDMP: number of apply slaves = 5
    KNACDMP: min number of apply slaves = 5
    KNACDMP: max number of apply slaves = 5
    KNACDMP: safety level (K) = 1
    KNACDMP: max txns in memory = 400
    KNACDMP: max constraints per table = 620
    KNACDMP: hash table size (in entries) = 10000000
    KNACDMP: Coordinator's intervals -------------------------------
    KNACDMP: syncpoint interval (ms) = 0
    KNACDMP: write low watermark interval(ms)= 1
    KNACDMP: Coordinator's timers/counters -------------------------
    KNACDMP: current time = 1365082918
    KNACDMP: low watermark timer = 0
    KNACDMP: syncpoint timer = 1365082918
    KNACDMP: txnbufsize timer = 1365082220
    KNACDMP: Coordinator's txn counts -------------------------
    KNACDMP: total txns applied = 0
    KNACDMP: number of unassigned comp txns = 0
    KNACDMP: number of unassigned incomp txns= 0
    KNACDMP: avg number of unassigned txns = 0.00
    KNACDMP: total applied at last plwm write= 0
    KNACDMP: apply prog. entries below plwm = 0
    KNACDMP: total unassigned lcrs = 0
    KNACDMP: Coordinator's State/Flags -----------------------------
    KNACDMP: Coordinator's State = KNACST_APPLY_UNTIL_END
    KNACDMP: Coordinator's Flags = 0x408004
    KNACDMP: Slave counts ------------------------------------------
    KNACDMP: number of reserved slaves = 0
    KNACDMP: number of admin slaves = 0
    KNACDMP: number of slaves in wait cmt = 1
    KNACDMP: number of slaves suspended = 0
    KNACDMP: number of safe slaves = 1
    KNACDMP: avg number of idle slaves = 0.00
    KNACDMP: number of slaves initializing = 0
    KNACDMP: number of slaves terminating = 0
    KNACDMP: Slave Lists -------------------------------------------
    KNACDMP: Dumping All Slaves :-
    Slave id = 0, State = 8, Flags = 0, Not Assigned 0 txns 0 lcrs
    Slave id = 1, State = 9, Flags = 2, Assigned Xid = 0x001e.006.0005d213 1 txns 0 lcrs
    Slave id = 2, State = 5, Flags = 1, Assigned Xid = 0x0019.00e.0007f8d9 1 txns 0 lcrs
    Slave id = 3, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
    Slave id = 4, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
    Slave id = 5, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
    KNACDMP: End dumping all slaves
    KNACDMP: syncdep slaves = { }
    KNACDMP: cont chunk slaves = { }
    KNACDMP: cont slaves = { }
    KNACDMP: exec txn slaves = { }
    KNACDMP: Active slaves (2) = { 1 2 }
    KNACDMP: Idle slaves (3) = { 3 4 5 }
    KNACDMP: Txn Lists ---------------------------------------------
    KNACDMP: Dumping all txns :-
    XID = 0x001e.006.0005d213 Commit pos = 0002fc06718c (SCN=0x0002.fc06718c) State = 0
    Lcr cnt = 0
    Assigned to slavid = 1
    Fetched chunks = 142
    depslaves = { } wm depslaves = { }
    XID = 0x0019.00e.0007f8d9 Commit pos = 0002fc0f876b (SCN=0x0002.fc0f876b) State = 1
    Lcr cnt = 0
    Assigned to slavid = 2
    Fetched chunks = 1
    depslaves = { } wm depslaves = { }
    KNACDMP: End dumping all txns.
    KNACDMP: Complete txns = { 0x0019.00e.0007f8d9 ** NO UNASS ** }
    KNACDMP: Unassigned txns = { }
    KNACDMP: *******************************************************
    Warning: Apply error received: ORA-26714: User Error encountered during apply process. Clearing.
    knahcapplymain: encountered error=26808
    *** 2013-04-04 16:58:47.073
    dbkedDefDump(): Starting a non-incident diagnostic dump (flags=0x0, level=0, mask=0x0)
    ----- Error Stack Dump -----
    ORA-26808: Apply process AS01 died unexpectedly.
    ORA-01031: insufficient privileges
    KNACDMP: *******************************************************
    KNACDMP: Dumping apply coordinator's context at 25487cb0
    KNACDMP: Apply Engine # 0
    KNACDMP: Apply Engine name
    KNACDMP: Coordinator's Watermarks ------------------------------
    KNACDMP: Apply High Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Apply Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Recovery Low Watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Fetch Low Watermark = 0002fc0f876b (SCN=0x0002.fc0f876b)
    KNACDMP: Fetch Low Watermark Time = 811857327
    KNACDMP: Oldest SCN = (SCN=0x0000.00000000)
    KNACDMP: Oldest XID =
    KNACDMP: Oldest Create Time = 0
    KNACDMP: Last replicant syncpoint SCN = 0x0000.00000000
    KNACDMP: Last syncpoint at primary SCN = 0x0002.fc0f875f
    KNACDMP: First partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
    KNACDMP: Last partition max pos = 0002fc10fab4 (SCN=0x0002.fc10fab4)
    KNACDMP: Last processed = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Conservative pos = 0002fc0f8cb2 (SCN=0x0002.fc0f8cb2)
    KNACDMP: Recovery start pos = (SCN=0x0000.00000000)
    KNACDMP: Recovery high watermark = 0002fc0f875f (SCN=0x0002.fc0f875f)
    KNACDMP: Spill LWM = (SCN=0x0000.00000000)
    KNACDMP: Spill LWM Create Time = 0
    KNACDMP: Coordinator's constants -------------------------------
    KNACDMP: number of apply slaves = 5
    KNACDMP: min number of apply slaves = 5
    KNACDMP: max number of apply slaves = 5
    KNACDMP: safety level (K) = 1
    KNACDMP: max txns in memory = 400
    KNACDMP: max constraints per table = 620
    KNACDMP: hash table size (in entries) = 10000000
    KNACDMP: Coordinator's intervals -------------------------------
    KNACDMP: syncpoint interval (ms) = 0
    KNACDMP: write low watermark interval(ms)= 1
    KNACDMP: Coordinator's timers/counters -------------------------
    KNACDMP: current time = 1365083926
    KNACDMP: low watermark timer = 0
    KNACDMP: syncpoint timer = 1365083926
    KNACDMP: txnbufsize timer = 1365083218
    KNACDMP: Coordinator's txn counts -------------------------
    KNACDMP: total txns applied = 0
    KNACDMP: number of unassigned comp txns = 0
    KNACDMP: number of unassigned incomp txns= 1
    KNACDMP: avg number of unassigned txns = 0.00
    KNACDMP: total applied at last plwm write= 0
    KNACDMP: apply prog. entries below plwm = 0
    KNACDMP: total unassigned lcrs = 0
    KNACDMP: Coordinator's State/Flags -----------------------------
    KNACDMP: Coordinator's State = KNACST_APPLY_UNTIL_END
    KNACDMP: Coordinator's Flags = 0x8204
    KNACDMP: Slave counts ------------------------------------------
    KNACDMP: number of reserved slaves = 0
    KNACDMP: number of admin slaves = 0
    KNACDMP: number of slaves in wait cmt = 0
    KNACDMP: number of slaves suspended = 0
    KNACDMP: number of safe slaves = 1
    KNACDMP: avg number of idle slaves = 0.00
    KNACDMP: number of slaves initializing = 0
    KNACDMP: number of slaves terminating = 0
    KNACDMP: Slave Lists -------------------------------------------
    KNACDMP: Dumping All Slaves :-
    Slave id = 0, State = 8, Flags = 0, Not Assigned 0 txns 0 lcrs
    Slave id = 1, State = 5, Flags = 1, Assigned Xid = 0x0019.00e.0007f8d9 1 txns 0 lcrs
    Slave id = 2, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
    Slave id = 3, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
    Slave id = 4, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
    Slave id = 5, State = 0, Flags = 0, Not Assigned 0 txns 0 lcrs
    KNACDMP: End dumping all slaves
    KNACDMP: syncdep slaves = { }
    KNACDMP: cont chunk slaves = { }
    KNACDMP: cont slaves = { }
    KNACDMP: exec txn slaves = { }
    KNACDMP: Active slaves (1) = { 1 }
    KNACDMP: Idle slaves (4) = { 2 3 4 5 }
    KNACDMP: Txn Lists ---------------------------------------------
    KNACDMP: Dumping all txns :-
    XID = 0x001e.006.0005d213 Commit pos = 0002fc06718c (SCN=0x0002.fc06718c) State = 0
    Lcr cnt = 0
    Not Assigned
    Fetched chunks = 142
    depslaves = { } wm depslaves = { }
    XID = 0x0019.00e.0007f8d9 Commit pos = 0002fc0f876b (SCN=0x0002.fc0f876b) State = 1
    Lcr cnt = 0
    Assigned to slavid = 1
    Fetched chunks = 1
    depslaves = { } wm depslaves = { }
    KNACDMP: End dumping all txns.
    KNACDMP: Complete txns = { 0x0019.00e.0007f8d9 ** NO UNASS ** }
    KNACDMP: Unassigned txns = { 0x001e.006.0005d213 }
    KNACDMP: *******************************************************
    *** 2013-04-04 16:58:47.513
    Warning: Apply error received: ORA-26714: User Error encountered during apply process. Clearing.
    I watched this link http://docs.oracle.com/cd/E11882_01/server.112/e17069/strms_trapply.htm#i1014714 and I checked grants of schemas owners. These grants identical as on Primary DB Server.
    I don't know what I need to do. It's very critical Server. Please help me.

    So, my problem is solved very easy.
    Logical Standby didn't work because I added grant SYSDBA to temporary user and revoked this grant at once and I didn't change orapwSID file on Logical Standby from Primary.
    http://docs.oracle.com/cd/E11882_01/server.112/e25608/create_ps.htm#SBYDB00424Note:
    Whenever you grant or revoke the SYSDBA or SYSOPER privileges or change the login password of a user who has these privileges, you must replace the password file at each physical or snapshot standby database in the configuration with a fresh copy of the password file from the primary database.
    >
    So, I deleted temporary user on Logical Standby and it solved the problem.
    Thanks a lot to all who helped me!

  • Manual\DGMGRL Switchover Standby ora-01033 error

    I have created a standby server for my SAP application as a part of test Disaster Recovery scenario. I can see the redo logs getting applied from primary to standby. However when I manually switchover the roles i encounters ORA -01033 error at NEW PRIMARY server and logs are also not getting applied in this scenario.
    When i again changes the roles it works fine. I am not sure what is cause of ORA -01033 error. Here are the detailed tnsnames.ora of both sites.
    Primary Server
    P11.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11.WORLD)
    TO_STANDBY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.102)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = TO_STANDBY.WORLD)
    TO_PRIMARY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = TO_PRIMARY.WORLD)
    LISTENER_P11.WORLD=(address=(protocol= tcp)(host=10.0.1.104)(port= 1527))
    Standby Site
    TO_PRIMARY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = TO_PRIMARY.WORLD)
    P11.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11.WORLD)
    TO_STANDBY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.102)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = TO_STANDBY.WORLD)
    LISTENER_P11.WORLD=(address=(protocol= tcp)(host=10.0.1.104)(port= 1527))
    Now , when i enable the DGMGRL configuration and add standby database at primary the " log_archive_dest_2=''" goes empty . Here is the pfile of primary after enable of the DGMGRL.
    pfile of Primary
    *._B_TREE_BITMAP_PLANS=FALSE
    *._IN_MEMORY_UNDO=FALSE
    *._INDEX_JOIN_ENABLED=FALSE
    *._OPTIM_PEEK_USER_BINDS=FALSE
    *._OPTIMIZER_MJC_ENABLED=FALSE
    *._SORT_ELIMINATION_COST_RATIO=10
    *._TABLE_LOOKUP_PREFETCH_SIZE=0
    *.archive_lag_target=0
    *.background_dump_dest='D:\oracle\P11\saptrace\background'
    *.compatible='10.2.0'
    *.control_file_record_keep_time=30
    *.control_files='D:\oracle\P11\origlogA\cntrl\cntrlP11.dbf','D:\oracle\P11\origlogB\cntrl\cntrlP11.dbf','D:\oracle\P11\sapdata1\cntrl\cntrlP11.dbf'
    *.core_dump_dest='D:\oracle\P11\saptrace\background'
    *.db_block_size=8192
    *.db_cache_size=260938137
    *.db_files=254
    *.db_name='P11'
    *.db_unique_name='P11_primary'
    *.dg_broker_start=TRUE
    *.dml_locks=4000
    *.event='10191 trace name context forever, level 1'
    *.FAL_Client='to_primary'
    *.FAL_Server='to_standby'
    *.FILESYSTEMIO_OPTIONS='setall'
    *.job_queue_processes=1
    *.log_archive_config='nodg_config'
    *.log_archive_dest_1='LOCATION=C:\oracle\P11\oraarch\P11arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=P11_primary'
    p11.log_archive_dest_1='location="C:\oracle\P11\oraarch\P11arch"','valid_for=(ONLINE_LOGFILE,ALL_ROLES)'
    *.log_archive_dest_2=''
    *.log_archive_dest_state_1='enable'
    p11.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    p11.log_archive_format='ARC%S_%R.%T'
    *.log_archive_max_processes=10
    *.log_archive_min_succeed_dest=1
    p11.log_archive_trace=0
    *.log_buffer=1048576
    *.log_checkpoint_interval=0
    *.log_checkpoints_to_alert=true
    *.open_cursors=800
    *.parallel_execution_message_size=16384
    *.pga_aggregate_target=347917516
    *.processes=80
    *.query_rewrite_enabled='false'
    *.recyclebin='off'
    *.remote_login_passwordfile='exclusive'
    *.remote_os_authent=true
    *.replication_dependency_tracking=false
    *.sessions=96
    *.sga_max_size=521876275
    *.shared_pool_reserved_size=26093813
    *.shared_pool_size=300938137
    *.sort_area_retained_size=0
    *.sort_area_size=2097152
    p11.standby_archive_dest=''
    *.standby_file_management='AUTO'
    *.star_transformation_enabled='true'
    *.undo_management='AUTO'
    *.undo_retention=43200
    *.undo_tablespace='PSAPUNDO'
    *.user_dump_dest='D:\oracle\P11\saptrace\usertrace'
    pfile of standy DB
    *._B_TREE_BITMAP_PLANS=FALSE
    *._IN_MEMORY_UNDO=FALSE
    *._INDEX_JOIN_ENABLED=FALSE
    *._OPTIM_PEEK_USER_BINDS=FALSE
    *._OPTIMIZER_MJC_ENABLED=FALSE
    *._SORT_ELIMINATION_COST_RATIO=10
    *._TABLE_LOOKUP_PREFETCH_SIZE=0
    *.background_dump_dest='D:\oracle\P11\saptrace\background'
    *.compatible='10.2.0'
    *.control_file_record_keep_time=30
    *.control_files='D:\oracle\P11\origlogA\cntrl\control01.ctl','D:\oracle\P11\origlogB\cntrl\control02.ctl','D:\oracle\P11\sapdata1\cntrl\control03.ctl'
    *.core_dump_dest='D:\oracle\P11\saptrace\background'
    *.db_block_size=8192
    *.db_cache_size=155870822
    *.db_files=254
    *.db_name='P11'
    *.db_unique_name='P11_disaster'
    *.dg_broker_start=TRUE
    *.dml_locks=4000
    *.event='10191 trace name context forever, level 1'
    *.FAL_Client='to_standby'
    *.FAL_Server='to_primary'
    *.FILESYSTEMIO_OPTIONS='setall'
    *.job_queue_processes=1
    *.log_archive_config='DG_CONFIG= (P11_primary, P11_disaster)'
    *.log_archive_dest_1='LOCATION=C:\oracle\P11\oraarch\P11arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=P11_disaster'
    *.log_archive_dest_2='SERVICE=to_primary LGWR ASYNC DELAY=5 VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=P11_primary'
    *.log_archive_dest_state_1='enable'
    *.log_archive_dest_state_2='enable'
    *.log_archive_max_processes=10
    *.log_buffer=1048576
    *.log_checkpoint_interval=0
    *.log_checkpoints_to_alert=true
    *.open_cursors=800
    *.parallel_execution_message_size=16384
    *.pga_aggregate_target=207827763
    *.processes=80
    *.query_rewrite_enabled='false'
    *.recyclebin='off'
    *.remote_login_passwordfile='exclusive'
    *.remote_os_authent=true
    *.replication_dependency_tracking=false
    *.sessions=96
    *.sga_max_size=311741644
    *.shared_pool_reserved_size=15587082
    *.shared_pool_size=300870822
    *.sort_area_retained_size=0
    *.sort_area_size=2097152
    *.standby_file_management='AUTO'
    *.star_transformation_enabled='true'
    *.undo_management='AUTO'
    *.undo_retention=43200
    *.undo_tablespace='PSAPUNDO'
    *.user_dump_dest='D:\oracle\P11\saptrace\usertrace'
    Here are the alert logs of primary DB.
    LTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=PROD102)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=p11_disaster_XPT)(INSTANCE_NAME=p11)(SERVER=dedicated)))"',' ARCH SYNC NOAFFIRM delay=5 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="p11_disaster" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Sat Jul 02 16:29:22 2011
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Sat Jul 02 16:29:22 2011
    ALTER SYSTEM SET log_archive_trace=0 SCOPE=BOTH SID='p11';
    Sat Jul 02 16:29:22 2011
    ALTER SYSTEM SET log_archive_format='ARC%S_%R.%T' SCOPE=SPFILE SID='p11';
    Sat Jul 02 16:29:22 2011
    ALTER SYSTEM SET standby_archive_dest='' SCOPE=BOTH SID='p11';
    Sat Jul 02 16:29:22 2011
    ALTER SYSTEM SET log_archive_dest_1='location="C:\oracle\P11\oraarch\P11arch"','valid_for=(ONLINE_LOGFILE,ALL_ROLES)' SCOPE=BOTH SID='p11';
    Sat Jul 02 16:29:23 2011
    ALTER SYSTEM SET log_archive_dest_state_1='ENABLE' SCOPE=BOTH SID='p11';
    Sat Jul 02 16:29:23 2011
    ALTER SYSTEM SET standby_file_management='AUTO' SCOPE=BOTH SID='*';
    Sat Jul 02 16:29:23 2011
    ALTER SYSTEM SET archive_lag_target=0 SCOPE=BOTH SID='*';
    Sat Jul 02 16:29:23 2011
    ALTER SYSTEM SET log_archive_max_processes=10 SCOPE=BOTH SID='*';
    Sat Jul 02 16:29:23 2011
    ALTER SYSTEM SET log_archive_min_succeed_dest=1 SCOPE=BOTH SID='*';
    Sat Jul 02 16:29:27 2011
    Beginning log switch checkpoint up to RBA [0x3b7.2.10], SCN: 7939485
    Thread 1 advanced to log sequence 951
    Current log# 4 seq# 951 mem# 0: D:\ORACLE\P11\ORIGLOGB\LOG_G14M1.DBF
    Current log# 4 seq# 951 mem# 1: C:\ORACLE\P11\MIRRLOGB\LOG_G14M2.DBF
    Sat Jul 02 16:29:28 2011
    ALTER SYSTEM SET log_archive_dest_2='service="(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=PROD102)(PORT=1521)))(CONNECT_DATA=(SERVICE_NAME=p11_disaster_XPT)(INSTANCE_NAME=p11)(SERVER=dedicated)))"',' ARCH SYNC NOAFFIRM delay=5 OPTIONAL max_failure=0 max_connections=1 reopen=300 db_unique_name="p11_disaster" register net_timeout=180 valid_for=(online_logfile,primary_role)' SCOPE=BOTH;
    Sat Jul 02 16:29:28 2011
    ALTER SYSTEM SET log_archive_dest_state_2='ENABLE' SCOPE=BOTH;
    Beginning log switch checkpoint up to RBA [0x3b8.2.10], SCN: 7939487
    Thread 1 advanced to log sequence 952
    Current log# 2 seq# 952 mem# 0: D:\ORACLE\P11\ORIGLOGB\LOG_G12M1.DBF
    Current log# 2 seq# 952 mem# 1: C:\ORACLE\P11\MIRRLOGB\LOG_G12M2.DBF
    Sat Jul 02 16:29:29 2011
    Error 12541 received logging on to the standby
    Check whether the listener is up and running.
    Sat Jul 02 16:29:29 2011
    Errors in file d:\oracle\p11\saptrace\background\p11_arc1_2396.trc:
    ORA-12541: TNS:no listener
    FAL[server, ARC1]: Error 12541 creating remote archivelog file '(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=tcp)(HOST=PROD102)(PORT=1521)))(CONNECT_DATA=
    Here is the Alert log of standby
    RFS[2]: Identified database type as 'physical standby'
    Sat Jul 02 16:21:00 2011
    RFS[3]: Assigned to RFS process 1620
    RFS[3]: Identified database type as 'physical standby'
    Sat Jul 02 16:21:00 2011
    RFS[2]: Archived Log: 'C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00947_0755040789.001'
    Sat Jul 02 16:21:00 2011
    RFS[3]: Archived Log: 'C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00948_0755040789.001'
    Sat Jul 02 16:21:00 2011
    Media Recovery Log C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00947_0755040789.001
    Identified End-Of-Redo for thread 1 sequence 947
    Sat Jul 02 16:21:01 2011
    Media Recovery End-Of-Redo indicator encountered
    Sat Jul 02 16:21:01 2011
    Media Recovery Applied until change 7934481
    Media Recovery archivelogs detected beyond End-Of-REDO
    Resetting standby activation ID 1369083708 (0x519a8f3c)
    Completed: Alter Database Recover Managed Standby Database
    Sat Jul 02 16:21:29 2011
    Alter Database Recover Managed Standby Database Disconnect
    MRP0 started with pid=28, OS id=996
    Managed Standby Recovery not using Real Time Apply
    parallel recovery started with 2 processes
    Clearing online redo logfile 1 D:\ORACLE\P11\ORIGLOGA\LOG_G11M1.DBF
    Clearing online log 1 of thread 1 sequence number 949
    Sat Jul 02 16:21:36 2011
    Completed: Alter Database Recover Managed Standby Database Disconnect
    Sat Jul 02 16:21:37 2011
    Clearing online redo logfile 1 complete
    Clearing online redo logfile 2 D:\ORACLE\P11\ORIGLOGB\LOG_G12M1.DBF
    Clearing online log 2 of thread 1 sequence number 946
    Clearing online redo logfile 2 complete
    Clearing online redo logfile 3 D:\ORACLE\P11\ORIGLOGA\LOG_G13M1.DBF
    Clearing online log 3 of thread 1 sequence number 944
    Clearing online redo logfile 3 complete
    Clearing online redo logfile 4 D:\ORACLE\P11\ORIGLOGB\LOG_G14M1.DBF
    Clearing online log 4 of thread 1 sequence number 945
    Clearing online redo logfile 4 complete
    Media Recovery Log C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00948_0755040789.001
    Media Recovery Waiting for thread 1 sequence 949
    Sat Jul 02 16:22:37 2011
    RFS[1]: No standby redo logfiles created
    RFS[1]: Archived Log: 'C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00949_0755040789.001'
    Sat Jul 02 16:22:37 2011
    RFS[1]: Archive log thread 1 sequence 949 available in 5 minute(s)
    Sat Jul 02 16:22:37 2011
    Redo Shipping Client Connected as PUBLIC
    -- Connected User is Valid
    RFS[4]: Assigned to RFS process 2200
    RFS[4]: Identified database type as 'physical standby'
    Primary database is in MAXIMUM PERFORMANCE mode
    Primary database is in MAXIMUM PERFORMANCE mode
    RFS[4]: No standby redo logfiles created
    Sat Jul 02 16:22:38 2011
    Media Recovery Delayed for 5 minute(s) (thread 1 sequence 949)
    Sat Jul 02 16:27:38 2011
    Media Recovery Log C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00949_0755040789.001
    Media Recovery Waiting for thread 1 sequence 950 (in transit)
    Sat Jul 02 16:29:42 2011
    RFS[4]: Possible network disconnect with primary database
    Aborting archivelog file creation: C:\ORACLE\P11\ORAARCH\P11ARCH\ARC00950_0755040789.001
    If this a network disconnect, then this archivelog will be fetched again
    by GAP resolution mechanism.
    Please advice as i am not sure of i have created something in listener file for DGMGRL configuration..
    Regards

    DGMGRL> show configuration
    Configuration
    Name: my_dg
    Enabled: YES
    Protection Mode: MaxPerformance
    Fast-Start Failover: DISABLED
    Databases:
    P11_primary - Primary database
    P11_disaster - Physical standby database
    Current status for "my_dg":
    Warning: ORA-16607: one or more databases have failed
    DGMGRL> SHOW DATABASE 'P11_primary' 'StatusReport';
    STATUS REPORT
    INSTANCE_NAME SEVERITY ERROR_TEXT
    p11 ERROR ORA-16737: the redo transport service for standby database "P11_disaster" has an error
    p11 WARNING ORA-16715: redo transport-related property LogXptMode of standby database "P11_disaster" is inconsistent
    DGMGRL> SHOW DATABASE 'P11_primary' 'LogXptStatus';
    LOG TRANSPORT STATUS
    PRIMARY_INSTANCE_NAME STANDBY_DATABASE_NAME STATUS
    p11 P11_disaster ORA-12541: TNS:no listener
    After this when i check the status of listener at P11_disaster site it was up . I restarted the listener and found following message in listener log at standby ( p11_primary) . These are the last lines of listener log.
    03-JUL-2011 13:36:40 * (CONNECT_DATA=(SID=P11)(GLOBAL_NAME=TO_STANDBY.WORLD)(CID=(PROGRAM=d:\oracle\p11\102\bin\ORACLE.EXE)(HOST=PROD104)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.104)(PORT=2244)) * establish * P11 * 0
    03-JUL-2011 13:36:40 * (CONNECT_DATA=(SID=P11)(GLOBAL_NAME=TO_STANDBY.WORLD)(CID=(PROGRAM=d:\oracle\p11\102\bin\ORACLE.EXE)(HOST=PROD104)(USER=SYSTEM))) * (ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.104)(PORT=2245)) * establish * P11 * 0
    03-JUL-2011 13:45:25 * ping * 0
    No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11.WORLDipc)))
    No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11ipc)))
    No longer listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.102)(PORT=1527)))
    Listener completed notification to CRS on stop
    03-JUL-2011 13:45:34 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=p11adm))(COMMAND=stop)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169869824)) * stop * 0
    TNSLSNR for 64-bit Windows: Version 10.2.0.2.0 - Production on 03-JUL-2011 13:45:42
    Copyright (c) 1991, 2005, Oracle. All rights reserved.
    System parameter file is D:\oracle\P11\102\network\admin\listener.ora
    Log messages written to D:\oracle\P11\102\network\log\listener.log
    Trace information written to D:\oracle\P11\102\network\trace\listener.trc
    Trace level is currently 0
    Started with pid=624
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11.WORLDipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(PIPENAME=\\.\pipe\P11ipc)))
    Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=10.0.1.102)(PORT=1527)))
    Listener completed notification to CRS on start
    TIMESTAMP * CONNECT DATA [* PROTOCOL INFO] * EVENT [* SID] * RETURN CODE
    03-JUL-2011 13:45:46 * (CONNECT_DATA=(CID=(PROGRAM=)(HOST=)(USER=p11adm))(COMMAND=status)(ARGUMENTS=64)(SERVICE=LISTENER)(VERSION=169869824)) * status * 0
    I am sure this is some configuration issue , however does not have clue :(

  • Standby ORA-12505 error

    I have tried to create the standby without the DG broker .However , I am getting this error in alert log at primary which I am not able to resolve.
    PING[ARC6]: Heartbeat failed to connect to standby 'to_standby'. Error is 12505.
    Mon Jul 04 12:41:35 2011
    Error 12505 received logging on to the standby
    Mon Jul 04 12:41:35 2011
    Errors in file d:\oracle\p11\saptrace\background\p11_arc6_1904.trc:
    ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
    PING[ARC6]: Heartbeat failed to connect to standby 'to_standby'. Error is 12505.
    Pfile of Primary Server
    *._B_TREE_BITMAP_PLANS=FALSE
    *._IN_MEMORY_UNDO=FALSE
    *._INDEX_JOIN_ENABLED=FALSE
    *._OPTIM_PEEK_USER_BINDS=FALSE
    *._OPTIMIZER_MJC_ENABLED=FALSE
    *._SORT_ELIMINATION_COST_RATIO=10
    *._TABLE_LOOKUP_PREFETCH_SIZE=0
    *.archive_lag_target=0
    *.background_dump_dest='D:\oracle\P11\saptrace\background'
    *.compatible='10.2.0'
    *.control_file_record_keep_time=30
    *.control_files='D:\oracle\P11\origlogA\cntrl\cntrlP11.dbf','D:\oracle\P11\origlogB\cntrl\cntrlP11.dbf','D:\oracle\P11\sapdata1\cntrl\cntrlP11.dbf'
    *.core_dump_dest='D:\oracle\P11\saptrace\background'
    *.db_block_size=8192
    *.db_cache_size=260938137
    *.db_files=254
    *.db_name='P11'
    *.db_unique_name='P11_primary'
    *.dml_locks=4000
    *.event='10191 trace name context forever, level 1'
    *.FAL_Client='to_primary'
    *.FAL_Server='to_standby'
    *.FILESYSTEMIO_OPTIONS='setall'
    *.job_queue_processes=1
    *.local_listener='(ADDRESS = (PROTOCOL = TCP)(HOST = 10.0.1.104)(PORT = 1521))'
    *.log_archive_config='dg_config=(P11_disaster,P11_primary)'
    *.log_archive_dest_1='LOCATION=C:\oracle\P11\oraarch\P11arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=P11_primary'
    *.log_archive_dest_2='SERVICE=to_standby LGWR ASYNC DELAY=5 VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=P11_disaster'
    *.log_archive_dest_state_1='enable'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_max_processes=10
    *.log_archive_min_succeed_dest=1
    *.log_buffer=1048576
    *.log_checkpoint_interval=0
    *.log_checkpoints_to_alert=true
    *.open_cursors=800
    *.parallel_execution_message_size=16384
    *.pga_aggregate_target=347917516
    *.processes=80
    *.query_rewrite_enabled='false'
    *.recyclebin='off'
    *.remote_login_passwordfile='exclusive'
    *.remote_os_authent=true
    *.replication_dependency_tracking=false
    *.sessions=96
    *.sga_max_size=521876275
    *.shared_pool_reserved_size=26093813
    *.shared_pool_size=300938137
    *.sort_area_retained_size=0
    *.sort_area_size=2097152
    *.standby_file_management='AUTO'
    *.star_transformation_enabled='true'
    *.undo_management='AUTO'
    *.undo_retention=43200
    *.undo_tablespace='PSAPUNDO'
    *.user_dump_dest='D:\oracle\P11\saptrace\usertrace'
    Pfile of Standby Server
    *._B_TREE_BITMAP_PLANS=FALSE
    *._IN_MEMORY_UNDO=FALSE
    *._INDEX_JOIN_ENABLED=FALSE
    *._OPTIM_PEEK_USER_BINDS=FALSE
    *._OPTIMIZER_MJC_ENABLED=FALSE
    *._SORT_ELIMINATION_COST_RATIO=10
    *._TABLE_LOOKUP_PREFETCH_SIZE=0
    *.background_dump_dest='D:\oracle\P11\saptrace\background'
    *.compatible='10.2.0'
    *.control_file_record_keep_time=30
    *.control_files='D:\oracle\P11\origlogA\cntrl\control01.ctl','D:\oracle\P11\origlogB\cntrl\control02.ctl','D:\oracle\P11\sapdata1\cntrl\control03.ctl'
    *.core_dump_dest='D:\oracle\P11\saptrace\background'
    *.db_block_size=8192
    *.db_cache_size=155870822
    *.db_files=254
    *.db_name='P11'
    *.db_unique_name='P11_disaster'
    *.dml_locks=4000
    *.event='10191 trace name context forever, level 1'
    *.FAL_Client='to_standby'
    *.FAL_Server='to_primary'
    *.FILESYSTEMIO_OPTIONS='setall'
    *.job_queue_processes=1
    *.local_listener='(ADDRESS = (PROTOCOL = TCP)(HOST = 10.0.1.102)(PORT = 1521))'
    *.log_archive_config='DG_CONFIG= (P11_primary, P11_disaster)'
    *.log_archive_dest_1='LOCATION=C:\oracle\P11\oraarch\P11arch VALID_FOR=(ALL_LOGFILES,ALL_ROLES) DB_UNIQUE_NAME=P11_disaster'
    *.log_archive_dest_2='SERVICE=to_primary LGWR ASYNC DELAY=5 VALID_FOR=(ONLINE_LOGFILES, PRIMARY_ROLE) DB_UNIQUE_NAME=P11_primary'
    *.log_archive_dest_state_1='enable'
    *.log_archive_dest_state_2='enable'
    *.log_archive_max_processes=10
    *.log_buffer=1048576
    *.log_checkpoint_interval=0
    *.log_checkpoints_to_alert=true
    *.open_cursors=800
    *.parallel_execution_message_size=16384
    *.pga_aggregate_target=207827763
    *.processes=80
    *.query_rewrite_enabled='false'
    *.recyclebin='off'
    *.remote_login_passwordfile='exclusive'
    *.remote_os_authent=true
    *.replication_dependency_tracking=false
    *.sessions=96
    *.sga_max_size=311741644
    *.shared_pool_reserved_size=15587082
    *.shared_pool_size=300870822
    *.sort_area_retained_size=0
    *.sort_area_size=2097152
    *.standby_file_management='AUTO'
    *.star_transformation_enabled='true'
    *.undo_management='AUTO'
    *.undo_retention=43200
    *.undo_tablespace='PSAPUNDO'
    *.user_dump_dest='D:\oracle\P11\saptrace\usertrace'
    TNSnames of Primary File
    # Filename......: tnsnames.ora
    # Created.......: created by SAP AG, R/3 Rel. >= 6.10
    # Name..........:
    # Date..........:
    # @(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $
    P11.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11.WORLD)
    TO_STANDBY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.102)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11_DISASTER.WORLD)
    TO_PRIMARY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11_PRIMARY.WORLD)
    LISTENER_P11.WORLD=(address=(protocol= tcp)(host=10.0.1.104)(port= 1527))
    Listener.ora of Primary
    # Filename......: listener.ora
    # Created.......: created by SAP AG, R/3 Rel. >= 6.10
    # Name..........:
    # Date..........:
    # @(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $
    ADMIN_RESTRICTIONS_LISTENER = on
    LISTENER =
    (ADDRESS_LIST =
    (ADDRESS =
    (PROTOCOL = IPC)
    (KEY = P11.WORLD)
    (ADDRESS=
    (PROTOCOL = IPC)
    (KEY = P11)
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = prod104)
    (PORT = 1527)
    STARTUP_WAIT_TIME_LISTENER = 0
    CONNECT_TIMEOUT_LISTENER = 10
    TRACE_LEVEL_LISTENER = OFF
    Tnsnames.ora of Standby
    # Filename......: tnsnames.ora
    # Created.......: created by SAP AG, R/3 Rel. >= 6.10
    # Name..........:
    # Date..........:
    # @(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $
    # Filename......: tnsnames.ora
    # Created.......: created by SAP AG, R/3 Rel. >= 6.10
    # Name..........:
    # Date..........:
    # @(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/TNSNAMES.ORA#4 $
    P11.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11.WORLD)
    TO_STANDBY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.102)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11_STANDBY.WORLD)
    TO_PRIMARY.WORLD=
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.104)
    (PORT = 1527)
    (CONNECT_DATA =
    (SID = P11)
    (GLOBAL_NAME = P11_PRIMARY.WORLD)
    LISTENER_P11.WORLD=(address=(protocol= tcp)(host=10.0.1.102)(port= 1527))
    Listener.ora of Standby
    # Filename......: listener.ora
    # Created.......: created by SAP AG, R/3 Rel. >= 6.10
    # Name..........:
    # Date..........:
    # @(#) $Id: //bc/700-1_REL/src/ins/SAPINST/impl/tpls/ora/ind/LISTENER.ORA#4 $
    ADMIN_RESTRICTIONS_LISTENER = on
    LISTENER =
    (ADDRESS_LIST =
    (ADDRESS =
    (PROTOCOL = IPC)
    (KEY = P11.WORLD)
    (ADDRESS=
    (PROTOCOL = IPC)
    (KEY = P11)
    (ADDRESS =
    (COMMUNITY = SAP.WORLD)
    (PROTOCOL = TCP)
    (HOST = 10.0.1.102)
    (PORT = 1527)
    STARTUP_WAIT_TIME_LISTENER = 0
    CONNECT_TIMEOUT_LISTENER = 10
    TRACE_LEVEL_LISTENER = OFF
    Please advice.
    Regards
    Edited by: dharm.singh on Jul 4, 2011 12:33 AM

    It is working now after adding this entry
    SID_LIST_LISTENER=(SID_LIST=(SID_DESC=(SID_NAME=P11)(ORACLE_HOME=D:\oracle\P11\102))) and also able to connect to primary to standby.
    using command
    sqlplus sys/****@to_standby as sysdba
    However , the Primary alter log is showing many errors
    MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
    Mon Jul 04 14:56:05 2011
    SMON: enabling cache recovery
    Mon Jul 04 14:56:07 2011
    Incremental checkpoint up to RBA [0x3e4.3.0], current log tail at RBA [0x3e4.3.0]
    Mon Jul 04 14:56:08 2011
    Error 1033 received logging on to the standby
    Mon Jul 04 14:56:08 2011
    Errors in file d:\oracle\p11\saptrace\background\p11_arc0_1532.trc:
    ORA-01033: ORACLE initialization or shutdown in progress
    Mon Jul 04 14:56:08 2011
    LGWR: Setting 'active' archival for destination LOG_ARCHIVE_DEST_2
    Error 1033 received logging on to the standby
    Mon Jul 04 14:56:08 2011
    Errors in file d:\oracle\p11\saptrace\background\p11_lns1_400.trc:
    ORA-01033: ORACLE initialization or shutdown in progress
    LGWR: Error 1033 creating archivelog file 'to_standby'
    LNS: Failed to archive log 2 thread 1 sequence 996 (1033)
    Mon Jul 04 14:56:08 2011
    FAL[server, ARC0]: Error 1033 creating remote archivelog file 'to_standby'
    FAL[server, ARC0]: FAL archive failed, see trace file.
    Mon Jul 04 14:56:09 2011
    Errors in file d:\oracle\p11\saptrace\background\p11_arc0_1532.trc:
    ORA-16055: FAL request rejected
    ARCH: FAL archive failed. Archiver continuing
    Mon Jul 04 14:56:09 2011
    Successfully onlined Undo Tablespace 1.
    Mon Jul 04 14:56:09 2011
    SMON: enabling tx recovery
    Mon Jul 04 14:56:10 2011
    Database Characterset is UTF8
    Starting background process QMNC
    QMNC started with pid=26, OS id=180
    Mon Jul 04 14:56:16 2011
    Completed: ALTER DATABASE OPEN
    Mon Jul 04 14:57:00 2011
    Shutting down archive processes
    Mon Jul 04 14:57:05 2011
    ARCH shutting down
    ARCa: Archival stopped
    Mon Jul 04 15:02:06 2011
    Errors in file d:\oracle\p11\saptrace\background\p11_arc2_500.trc:
    ORA-16143: RFS connections not allowed during or after terminal recovery
    Mon Jul 04 15:02:06 2011
    PING[ARC2]: Heartbeat failed to connect to standby 'to_standby'. Error is 16143.
    p11arc0_1532.trc log file_
    Dump file d:\oracle\p11\saptrace\background\p11_lns1_400.trc
    Mon Jul 04 14:56:04 2011
    ORACLE V10.2.0.2.0 - 64bit Production vsnsta=0
    vsnsql=14 vsnxtr=3
    Oracle Database 10g Enterprise Edition Release 10.2.0.2.0 - 64bit Production
    With the Partitioning, OLAP and Data Mining options
    Windows Server 2003 Version V5.2 Service Pack 2
    CPU : 2 - type 8664, 1 Physical Cores
    Process Affinity : 0x0000000000000000
    Memory (Avail/Total): Ph:2627M/3319M, Ph+PgF:9964M/11161M
    Instance name: p11
    Redo thread mounted by this instance: 1
    Oracle process number: 26
    Windows thread id: 400, image: ORACLE.EXE (LNS1)
    *** SERVICE NAME:() 2011-07-04 14:56:03.968
    *** SESSION ID:(73.1) 2011-07-04 14:56:03.968
    *** 2011-07-04 14:56:03.968 57032 kcrr.c
    LNS1: initializing for LGWR communication
    LNS1: connecting to KSR channel
    Success
    LNS1: subscribing to KSR channel
    Success
    *** 2011-07-04 14:56:04.031 57085 kcrr.c
    LNS1: initialized successfully ASYNC=1
    Destination is specified with ASYNC=61440
    *** 2011-07-04 14:56:08.203 70857 kcrr.c
    Sending online log thread 1 seq 996 [logfile 2] to standby
    Opening logfile [logno 2]
    LGWR: Archivelog for thread 1 sequence 996 will NOT be compressed
    Redo shipping client performing standby login
    OCISessionBegin failed -1
    .. Detailed OCI error val is 1033 and errmsg is 'ORA-01033: ORACLE initialization or shutdown in progress
    *** 2011-07-04 14:56:08.812 60639 kcrr.c
    Error 1033 received logging on to the standby
    Error 1033 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'to_standby'
    Error 1033 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'to_standby'
    ORA-01033: ORACLE initialization or shutdown in progress
    *** 2011-07-04 14:56:08.843 60639 kcrr.c
    LGWR: Error 1033 creating archivelog file 'to_standby'
    *** 2011-07-04 14:56:08.859 58901 kcrr.c
    kcrrfail: dest:2 err:1033 force:0 blast:1
    *** 2011-07-04 14:56:11.296
    *** 2011-07-04 14:56:11.296 70857 kcrr.c
    Sending online log thread 1 seq 996 [logfile 2] to standby
    Opening logfile [logno 2]
    LGWR: Archivelog for thread 1 sequence 996 will NOT be compressed
    *** 2011-07-04 14:56:11.796 70982 kcrr.c
    Shutting down [due to no more ASYNC destination]
    LNS1: Doing a channel reset for next time around...
    Edited by: dharm.singh on Jul 4, 2011 2:31 AM

  • ERROR in 9i standby - ORA-01153

    Hi,
    I am getting error while firing
    "recover standby database " command in my 9i standby.
    We are manually moving the archivelogs to standby from production, and firing the above command. All are done thru scheduled scripts .
    We have a recovery_run log file, with the detailed description of the recovery process running at standby.
    ----------The following is an extract from the alert log file.---------------
    Media Recovery Log /oracle/P71/saparch/P71arch1_334825.dbf
    Wed Dec 7 13:46:16 2005
    ALTER DATABASE RECOVER standby database
    Wed Dec 7 13:46:16 2005
    ORA-1153 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Dec 7 13:46:18 2005
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Dec 7 13:46:18 2005
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log /oracle/P71/saparch/P71arch1_334826.dbf
    Wed Dec 7 13:47:03 2005
    ALTER DATABASE RECOVER standby database
    Wed Dec 7 13:47:03 2005
    ORA-1153 signalled during: ALTER DATABASE RECOVER standby database ...
    Wed Dec 7 13:47:27 2005
    ORA-279 signalled during: ALTER DATABASE RECOVER CONTINUE DEFAULT ...
    Wed Dec 7 13:47:27 2005
    --------The following is an extract from the Recovery_run log file.----------
    SQL*Plus: Release 9.2.0.5.0 - Production on Wed Dec 7 13:51:29 2005
    SQL> Connected.
    SQL> ORA-01153: an incompatible media recovery is active
    SQL> SP2-0042: unknown command "auto" - rest of line ignored.
    SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.5.0 - Production
    Wed Dec 7 13:51:31 NFT 2005
    SQL*Plus: Release 9.2.0.5.0 - Production on Wed Dec 7 13:52:00 2005
    SQL> Connected.
    SQL> ORA-01153: an incompatible media recovery is active
    SQL> SP2-0042: unknown command "auto" - rest of line ignored.
    SQL> Disconnected from Oracle9i Enterprise Edition Release 9.2.0.5.0 - 64bit Production
    With the Partitioning option
    JServer Release 9.2.0.5.0 - Production
    Wed Dec 7 13:52:01 NFT 2005
    -------------The following is extract from the script that fires the recovery command-------------
    auto_recover()
    echo "connect / as sysdba" > /tmp/reco.sql
    echo "recover standby database " >> /tmp/reco.sql
    echo "auto" >> /tmp/reco.sql
    echo "exit" >> /tmp/reco.sql
    su - ${ORAUSER} -c sqlplus "/NOLOG" < /tmp/reco.sql | grep -v "Corpo" | grep -v "Manager"
    i checked the v$lock, and found that there is only one active session, which is holding the MR locks.
    It was working fine, and today we started getting this error
    Any idea about what is happening over here?
    Thanks in advance,
    Don

    At the standby, i also checked
    SQL> select max(sequence#) from v$log_history;
    And the max sequence number is getting incremented.
    That means, the archive logs are getting applied in the standby perfectly... right?
    But, how can that happen, since we are getting error while this command is run from the script?
    please help me out , to solve this issue.
    Thanks in advance,
    Don

  • 32bit Primary to 64bit Standby-"ORA-00704: bootstrap process failure"

    Hello All,
    As per the Doc ID 414043.1 it is possible to use mixed word size primary-standby configurations since 10g and better in 11g.
    So i created my test env:-
    OS: Linux 5.5 64bit
    DB Name: TEST
    Primary  - TEST32 on 32bit Oracle Home
    Standby-  TEST64 on 64bit Oracle Home
    I could apply TEST32's archive logs(manually) on TEST64 without any problem, but when i tried to migrate to 64bit it kept failed with "ORA-00704: bootstrap process failure ORA-39700: database must be opened with UPGRADE option"
    What i did on TEST64 is:
    1) Activate physical standby
    2) Startup Upgrade
    3)@?/rdbms/admin/utlirp.sql
    4)@?/rdbms/admin/utlrp.sql
    5)Shutdown
    6)Startup
    When i issue startup(step 6); it fails with
    <pre>
    SQL> startup;
    ORACLE instance started.
    Total System Global Area 1670221824 bytes
    Fixed Size 2227072 bytes
    Variable Size 419431552 bytes
    Database Buffers 1241513984 bytes
    Redo Buffers 7049216 bytes
    Database mounted.
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Process ID: 22712
    Session ID: 126 Serial number: 5
    SQL> exit
    </pre>
    Did i go wrong somewhere ?
    TIA,
    JJ

    What i did on TEST64 is:
    1) Activate physical standby
    2) Startup Upgrade
    3)@?/rdbms/admin/utlirp.sql
    4)@?/rdbms/admin/utlrp.sql
    5)Shutdown
    6)Startup
    SQL> startup;
    ORA-01092: ORACLE instance terminated. Disconnection forced
    ORA-00704: bootstrap process failure
    ORA-39700: database must be opened with UPGRADE option
    Process ID: 22712
    Session ID: 126 Serial number: 5SQL> Startup upgrade.

  • Heartbeat failed to connect to standby ORA-12160: TNS:internal error: Bad e

    <msg time='2010-09-03T11:37:46.548+06:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='DC-DB-01' host_addr='192.168.100.101' module=''
    pid='24310'>
    <txt>Error 12160 received logging on to the standby
    </txt>
    </msg>
    <msg time='2010-09-03T11:37:46.548+06:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='DC-DB-01' host_addr='192.168.100.101' module=''
    pid='24310'>
    <txt>Errors in file /u01/app/oracle/diag/rdbms/bddipdc/bddipdc1/trace/bddipdc1_arcq_24310.trc:
    ORA-12160: TNS:internal error: Bad error number
    </txt>
    </msg>
    <msg time='2010-09-03T11:37:46.548+06:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    host_id='DC-DB-01' host_addr='192.168.100.101' module=''
    pid='24310'>
    <txt>PING[ARCq]: Heartbeat failed to connect to standby &apos;bddipdrs&apos;. Error is 12160.
    </txt>
    </msg>
    From trace file,
    [oracle@DC-DB-01 ~]$ less /u01/app/oracle/diag/rdbms/bddipdc/bddipdc1/trace/bddipdc1_arcq_24310.trc
    Redo shipping client performing standby login
    OCIServerAttach failed -1
    .. Detailed OCI error val is 12160 and errmsg is 'ORA-12160: TNS:internal error:
    Bad error number
    OCIServerAttach failed -1
    .. Detailed OCI error val is 12160 and errmsg is 'ORA-12160: TNS:internal error:
    Bad error number
    OCIServerAttach failed -1
    .. Detailed OCI error val is 12160 and errmsg is 'ORA-12160: TNS:internal error:
    Bad error number
    *** 2010-09-03 11:37:46.548 4132 krsh.c
    Error 12160 received logging on to the standby
    *** 2010-09-03 11:37:46.548 869 krsu.c
    Error 12160 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'bddipdrs'
    Error 12160 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'bddipdrs'
    ORA-12160: TNS:internal error: Bad error number
    *** 2010-09-03 11:37:46.548 4132 krsh.c
    PING[ARCq]: Heartbeat failed to connect to standby 'bddipdrs'. Error is 12160.
    *** 2010-09-03 11:37:46.548 2747 krsi.c
    krsi_dst_fail: dest:2 err:12160 force:0 blast:1

    SQL> select
    2 substr(local.name,1,50) "Archive Name",
    case when remote.sequence# is null then 'NOT TRANSMITTED'
    3 4 else 'transmitted'
    5 end,
    6 local.sequence#,
    7 local.thread#
    8 from
    9 (select * from v$archived_log where dest_id = 1) local
    10 left join
    11 (select * from v$archived_log where dest_id = 2) remote
    12 on local.sequence# = remote.sequence# and
    13 local.thread# = remote.thread#
    14 order by local.sequence#;
    Archive Name CASEWHENREMOTE. SEQUENCE# THREAD#
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         1       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         2       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         3       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         4       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s transmitted             5       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         6       2
    +RECOVERY/bddipdc/archivelog/2010_08_31/thread_1_s NOT TRANSMITTED         6       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         7       2
    +RECOVERY/bddipdc/archivelog/2010_08_31/thread_1_s NOT TRANSMITTED         7       1
    +RECOVERY/bddipdc/archivelog/2010_08_31/thread_1_s NOT TRANSMITTED         8       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         8       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED         9       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED         9       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        10       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        10       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s transmitted            11       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        11       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        12       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        12       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        13       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        13       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        14       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        14       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        15       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        15       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        16       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        16       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        17       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        17       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        18       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        18       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        19       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        19       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        20       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        20       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        21       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        21       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        22       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        22       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        23       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        23       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        24       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        24       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        25       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        25       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        26       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        26       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        27       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        27       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        28       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        28       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        29       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        29       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        30       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        30       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        31       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        31       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        32       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        32       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        33       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        33       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        34       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        34       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        35       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        35       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        36       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        36       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        37       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        37       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        38       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        38       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        39       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        39       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        40       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        40       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        41       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        41       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        42       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        42       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        43       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        43       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        44       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        44       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        45       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        45       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        46       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        46       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        47       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        47       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        48       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        48       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        49       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        49       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        50       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        50       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        51       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        51       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        52       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        52       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        53       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_2_s NOT TRANSMITTED        53       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        54       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        54       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        55       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        55       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        56       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        56       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        57       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        57       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        58       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        58       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        59       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        59       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        60       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        60       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        61       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        61       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        62       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        62       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        63       2
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        63       1
    +RECOVERY/bddipdc/archivelog/2010_09_01/thread_1_s NOT TRANSMITTED        64       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        64       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        65       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        65       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        66       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        66       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        67       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        67       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        68       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        68       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        69       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        69       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        70       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        70       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        71       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        71       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        72       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        72       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        73       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        73       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        74       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        74       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        75       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        75       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        76       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        76       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        77       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        77       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        78       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        78       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        79       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        79       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        80       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        80       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        81       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        81       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        82       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        82       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        83       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        83       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        84       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        84       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        85       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        85       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        86       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        86       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        87       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        87       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        88       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        88       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        89       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        89       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        90       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        90       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        91       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        91       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        92       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        92       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        93       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        93       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_2_s NOT TRANSMITTED        94       2
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        94       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        95       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        96       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        97       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        98       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED        99       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       100       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       101       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       102       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       103       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       104       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       105       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       106       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       107       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       108       1
    Archive Name CASEWHENREMOTE. SEQUENCE# THREAD#
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       109       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       110       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       111       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       112       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       113       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       114       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       115       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       116       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       117       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       118       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       119       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       120       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       121       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       122       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       123       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       124       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       125       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       126       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       127       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       128       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       129       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       130       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       131       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       132       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       133       1
    +RECOVERY/bddipdc/archivelog/2010_09_02/thread_1_s NOT TRANSMITTED       134       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       135       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       136       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       137       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       138       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       139       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       140       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       141       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       142       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       143       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       144       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       145       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       146       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       147       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       148       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       149       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       150       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       151       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       152       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       153       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       154       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       155       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       156       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       157       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       158       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       159       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       160       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       161       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       162       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       163       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       164       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       165       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       166       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       167       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       168       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       169       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       170       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       171       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       172       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       173       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       174       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       175       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       176       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       177       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       178       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       179       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       180       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       181       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       182       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       183       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       184       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       185       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       186       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       187       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       188       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       189       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       190       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       191       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       192       1
    +RECOVERY/bddipdc/archivelog/2010_09_03/thread_1_s NOT TRANSMITTED       193       1
    282 rows selected.

  • ORA-01122, ORA-1110 and ORA--12-3

    Dear All,
    I have restored the oracle database with the backup. When starting the database, I am getting below errors:
    ORA-01122: data file 1 failed verification check
    ORA-01110: data file 1: 'G:\oracle\ABP\SAPDATA1\SYSMTEM_1\SYSTEM.DATA1'
    ORA-01203: wrong incarnation of this file - wrong creation SCN
    Can anybody please help me in solving this isue?
    Would be a great help.
    Regards,
    Faisal

    Hi,
    Sorry for the delay in pasting the result of the query you suggested.
    Please find below the result of it:
    SQL> select file#,name,creation_change# from v$d
    FILE#
    NAME
    CREATION_CHANGE#
    1
    G:\ORACLE\ABP\SAPDATA1\SYSTEM_1\SYSTEM.DATA1
    10
    2
    G:\ORACLE\ABP\SAPDATA1\UNDO_1\UNDO.DATA1
    6450
    FILE#
    NAME
    CREATION_CHANGE#
    3
    G:\ORACLE\ABP\SAPDATA1\SYSAUX_1\SYSAUX.DATA1
    6623
    4
    G:\ORACLE\ABP\SAPDATA2\SR3_1\SR3.DATA1
    FILE#
    NAME
    CREATION_CHANGE#
    161311
    5
    G:\ORACLE\ABP\SAPDATA2\SR3_2\SR3.DATA2
    161361
    6
    FILE#
    NAME
    CREATION_CHANGE#
    G:\ORACLE\ABP\SAPDATA2\SR3_3\SR3.DATA3
    161410
    7
    G:\ORACLE\ABP\SAPDATA2\SR3_4\SR3.DATA4
    161572
    FILE#
    NAME
    CREATION_CHANGE#
    8
    G:\ORACLE\ABP\SAPDATA3\SR3700_1\SR3700.DATA1
    161628
    9
    G:\ORACLE\ABP\SAPDATA3\SR3700_2\SR3700.DATA2
    161677
    FILE#
    NAME
    CREATION_CHANGE#
    10
    G:\ORACLE\ABP\SAPDATA3\SR3700_3\SR3700.DATA3
    161725
    11
    G:\ORACLE\ABP\SAPDATA3\SR3700_4\SR3700.DATA4
    FILE#
    NAME
    CREATION_CHANGE#
    161776
    12
    G:\ORACLE\ABP\SAPDATA4\SR3USR_1\SR3USR.DATA1
    161808
    12 rows selected.
    NOTE: This was captured after replacing the backup data files which were causing problem the database to come up with the latest data files and recovering
    Please suggest.

  • Ora-1666 on standby database

    Hi All,
    I have configured data guard on windows server 2003 platform with primary on 1 server and standby on another server. Oracle is of version 9i with exact release 9.2.0.6.0. I have enabled archived log on primary, modified init file with log_destinations, created password file, created control file and copied all these dbf files, redo log files, archived log files, control file, password files to standby server while the primary db is down. After copying all the required files on standby i tried to mount the standby but getting an error as ORA-01666: controlfile is for a standby database on the standby.
    Where as in the primary db alert log file an error is logged as Errors in file d:\oracle\admin\primary\bdump\primary_arc0_4240.trc: ORA-12500: TNS:listener failed to start a dedicated server process but i can do tnsping successfully from primary to standby and vice-versa and on standby ORA-1666 signalled during: ALTER DATABASE MOUNT...
    The things I suspect are Standby redo logs, Instance_name. I haven't created any standby logs on primary and i doubt whether it's mandatory to create on primary and standby db's or only in primary db pls let me know, i am confused of the standby logs because of these lines in document +(CREATE STANDBY REDO LOG FILES, IF NECESSARY (PRI+SEC)
    In this customer’s case, the customer chose not to use standby redo logs (SRLs), which are not required in Maximum Performance mode. However, if you decide to use SRLs, you would create them on both sites. You cannot create them on the primary database prior to the backup used to create the standby database because the SRLs on the standby must be empty of primary database redo data.)+.
    Instance_name parameter: we don't have this parameter in oracle10g where db_name and db_unique_name plays the role. Here in oracle9i is this Instance_name needs to be same on both primary and standby db's (i.e. primary on both db's or primary for primary and standby for standby?)
    Earlier i have configured this dataguard setup in solaris platform of oracle version 10g where i have created standby logs on primary db alone and logs are applying on standby and it's working fine.
    * please review the below parameters and let me know if i am missing something*
    tnsping from primary
    C:\Documents and Settings\Administrator>tnsping standby
    TNS Ping Utility for 32-bit Windows: Version 9.2.0.6.0 - Production on 25-JAN-20
    12 20:15:48
    Copyright (c) 1997 Oracle Corporation. All rights reserved.
    Used parameter files:
    D:\oracle\ora92\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
    (HOST = standbyIP )(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = standby)))
    OK (110 msec)
    tnsping from standby
    C:\Documents and Settings\Administrator>tnsping primary
    TNS Ping Utility for 32-bit Windows: Version 9.2.0.6.0 - Production on 25-JAN-20
    12 20:17:17
    Copyright (c) 1997 Oracle Corporation. All rights reserved.
    Used parameter files:
    D:\oracle\ora92\network\admin\sqlnet.ora
    Used TNSNAMES adapter to resolve the alias
    Attempting to contact (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)
    (HOST = primaryIP )(PORT = 1521))) (CONNECT_DATA = (SERVICE_NAME = primary)))
    OK (110 msec)
    Primary init file
    *.aq_tm_processes=0
    *.background_dump_dest='D:\oracle\admin\primary\bdump'
    *.compatible='9.2.0.0.0'
    *.control_files='D:\oracle\oradata\primary\control01.ctl','D:\oracle\oradata\primary\control02.ctl','D:\oracle\oradata\primary\control03.ctl'
    *.core_dump_dest='D:\oracle\admin\primary\cdump'
    *.db_block_size=16384
    *.db_cache_size=83886080
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_files=96
    *.db_name='primary'
    *.dg_broker_start=TRUE
    *.enqueue_resources=2000
    *.fal_client='primary'
    *.fal_server='standby'
    *.fast_start_mttr_target=300
    *.hash_join_enabled=TRUE
    *.instance_name='primary'
    *.java_pool_size=115343360
    *.job_queue_processes=10
    *.large_pool_size=0
    *.log_archive_dest_1='LOCATION=D:\oracle\archive-logs\primary\archivelog'
    *.log_archive_dest_2='SERVICE=standby LGWR ASYNC'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='ENABLE'
    *.log_archive_format='log_%t_%s.arc'
    *.max_enabled_roles=128
    *.nls_date_format='DD-MON-RRRR'
    *.nls_date_language='AMERICAN'
    *.nls_language='AMERICAN'
    *.nls_numeric_characters='.,'
    *.open_cursors=200
    *.optimizer_mode='CHOOSE'
    *.os_authent_prefix='OPS$'
    *.pga_aggregate_target=25165824
    *.processes=150
    *.query_rewrite_enabled='FALSE'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.remote_os_authent=TRUE
    *.shared_pool_size=115343360
    *.sort_area_size=3000000
    *.star_transformation_enabled='FALSE'
    *.timed_statistics=TRUE
    *.undo_management='AUTO'
    *.undo_retention=10800
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\oracle\admin\primary\udump'
    *.utl_file_dir='*'
    * standby init file*
    *.aq_tm_processes=0
    *.background_dump_dest='D:\oracle\admin\standby\bdump'
    *.compatible='9.2.0.0.0'
    *.control_files='D:\oracle\oradata\standby\standby.ctl'
    *.core_dump_dest='D:\oracle\admin\standby\cdump'
    *.db_block_size=16384
    *.db_cache_size=83886080
    *.db_domain=''
    *.db_file_multiblock_read_count=16
    *.db_files=96
    *.db_name='primary'
    *.dg_broker_start=TRUE
    *.enqueue_resources=2000
    *.fal_client='standby'
    *.fal_server='primary'
    *.fast_start_mttr_target=300
    *.hash_join_enabled=TRUE
    *.instance_name='standby'
    *.java_pool_size=115343360
    *.job_queue_processes=10
    *.large_pool_size=0
    *.log_archive_dest_1='LOCATION=D:\oracle\archive-logs\standby\archivelog'
    *.log_archive_dest_2='SERVICE=primary LGWR ASYNC'
    *.log_archive_dest_state_1='ENABLE'
    *.log_archive_dest_state_2='DEFER'
    *.log_archive_format='log_%t_%s.arc'
    *.max_enabled_roles=128
    *.nls_date_format='DD-MON-RRRR'
    *.nls_date_language='AMERICAN'
    *.nls_language='AMERICAN'
    *.nls_numeric_characters='.,'
    *.open_cursors=200
    *.optimizer_mode='CHOOSE'
    *.os_authent_prefix='OPS$'
    *.pga_aggregate_target=25165824
    *.processes=150
    *.query_rewrite_enabled='FALSE'
    *.remote_login_passwordfile='EXCLUSIVE'
    *.remote_os_authent=TRUE
    *.shared_pool_size=115343360
    *.sort_area_size=3000000
    *.star_transformation_enabled='FALSE'
    *.timed_statistics=TRUE
    *.undo_management='AUTO'
    *.undo_retention=10800
    *.undo_tablespace='UNDOTBS1'
    *.user_dump_dest='D:\oracle\admin\standby\udump'
    *.utl_file_dir='*'
    Regards
    Hari

    Primary output
    SQL> select error_code,message from v$dataguard_status;
    ERROR_CODE
    MESSAGE
    0
    ARC0: Archival started
    0
    ARC1: Archival started
    0
    Creating archive destination LOG_ARCHIVE_DEST_2: 'standby'
    ERROR_CODE
    MESSAGE
    12500
    LGWR: Error 12500 creating archivelog file 'standby'
    0
    LGWR: Completed archiving log 3 thread 1 sequence 7
    0
    ARC0: Evaluating archive log 2 thread 1 sequence 6
    ERROR_CODE
    MESSAGE
    0
    ARC0: Beginning to archive log 2 thread 1 sequence 6
    0
    Creating archive destination LOG_ARCHIVE_DEST_1: 'D:\ORACLE\ARCHIVE-LOGS\primary\A
    RCHIVELOG\LOG_1_6.ARC'
    0
    ARC0: Completed archiving log 2 thread 1 sequence 6
    ERROR_CODE
    MESSAGE
    9 rows selected.
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    THREAD# MAX(SEQUENCE#)
    1 6
    standby
    SQL> select thread#,max(sequence#) from v$archived_log group by thread#;
    no rows selected
    SQL> select thread#,max(sequence#) from v$archived_log where applied='YES' group
    by thread#;
    no rows selected
    SQL>
    trace file:
    Dump file d:\oracle\admin\primary\bdump\primary_arc0_4240.trc
    Wed Jan 25 19:45:07 2012
    ORACLE V9.2.0.6.0 - Production vsnsta=0
    vsnsql=12 vsnxtr=3
    Windows 2000 Version 5.2 Service Pack 2, CPU type 586
    Oracle9i Enterprise Edition Release 9.2.0.6.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.6.0 - Production
    Windows 2000 Version 5.2 Service Pack 2, CPU type 586
    Instance name: primary
    Redo thread mounted by this instance: 1
    Oracle process number: 11
    Windows thread id: 4240, image: ORACLE.EXE
    *** 2012-01-25 19:45:07.598
    *** SESSION ID:(11.1) 2012-01-25 19:45:07.364
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 19:45:07.676
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 19:51:07.987
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 19:51:08.049
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 19:57:08.261
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 19:57:08.355
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 19:59:08.563
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 19:59:08.626
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 20:01:08.820
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 20:01:08.883
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 20:06:09.190
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 20:06:09.253
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 20:12:09.698
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 20:12:09.776
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 20:18:10.069
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 20:18:10.132
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process
    *** 2012-01-25 21:02:11.811
    Error 12500 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Error 12500 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'standby'
    Heartbeat failed to connect to standby 'standby'. Error is 12500.
    *** 2012-01-25 21:02:11.889
    kcrrfail: dest:2 err:12500 force:0
    ORA-12500: TNS:listener failed to start a dedicated server process

  • Logical Standby SQL Apply Using Incorrect Decode Statement

    We are seeing statements erroring out on our logical standby that have been rewritten (presumably by sql apply) with decode statements that don't appear to be correct. For example, here is one of the rewritten statements.
    update /*+ streams restrict_all_ref_cons */ "CADPROD"."OMS_SQL_STATEMENT" p
    set *"APPLICATION"=decode(:1,'N',"APPLICATION",:2)*,
    "STATEMENT"=dbms_reputil2.get_final_lob(:3,"STATEMENT",:4)
    where (:5='N' or(1=1 and (:6='N' or(dbms_lob.compare(:7,"STATEMENT")=0)or(:7 is null and "STATEMENT" is null)))) and(:8="APPLICATION")
    The problem comes in, we believe, with the attempt to write the value "APPLICATION" to the application column which is only a 10 character field. the value for the :1 bind variable is "N" and the value for :2 is null.
    We see the following error on the logical standby:
    ORA-00600: internal error code, arguments: [kgh_heap_sizes:ds], [0x01FCDBE60], [], [], [], [], [], []
    ORA-07445: exception encountered: core dump [ACCESS_VIOLATION] [kxtoedu+54] [PC:0x2542308] [ADDR:0xFFFFFFFFFFFFFFFF] [UNABLE_TO_READ] []
    ORA-12899: value too large for column "CADPROD"."OMS_SQL_STATEMENT"."APPLICATION" (actual: 19576, maximum: 10)
    Is this a configuration issue or is it normal for SQL Apply to convert statements from logminer into decode statements?
    We have an Oracle 10.2.0.4 database running on windows 2003 R2 64-bit os. We have 3 physical and 2 logical standby's, no problems on the physical standbys.

    Hello;
    I noticed some of your parameters seem to be wrong.
    fal_client - This is Obsolete in 11.2
    You have db_name='test' on the Standby, it should be 'asadmin'
    fal_server=test is set like this on the standby, it should be 'asadmin'
    I might consider changing VALID_FOR to this :
    VALID_FOR=(ONLINE_LOGFILES,ALL_ROLES)Would review 4.2 Step-by-Step Instructions for Creating a Logical Standby Database of Oracle Document E10700-02
    Document 278371.1 is showing its age in my humble opinion.
    -----Wait on this until you fix your parameters----------------------
    Try restarting the SQL Apply
    ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATEI don't see the parameter MAX_SERVERS, try setting it to 8 times the number of cores.
    Use these statements to trouble shoot :
    SELECT NAME, VALUE, UNIT FROM V$DATAGUARD_STATS;
    SELECT NAME, VALUE FROM V$LOGSTDBY_STATS WHERE NAME LIKE ;TRANSACTIONS%';
    SELECT COUNT(1) AS IDLE_PREPARERS FROM V$LOGSTDBY_PROCESS WHERE
    TYPE = 'PREPERER' AND STATUS_CODE = 16166;Best Regards
    mseberg
    Edited by: mseberg on Feb 14, 2012 7:37 AM

  • ORACLE8I에서 STANDBY DB 구성 및 관리 방법

    제품 : ORACLE SERVER
    작성날짜 : 2004-08-16
    database crash 시 backup받아둔 datafile과 archive file을 모두 restore하고,
    recover하는 작업은 경우에 따라 고객의 요구 사항보다 길어지는 경우가 종종
    있다.
    이런 경우 미리 standy db를 구성하여 standby db에 recovery를 진행해 두고,
    piramry db crash시 바로 stadnby db와 연결하면, db down time을 최소화하는데
    많은 도움이 된다.
    Oracle 8.1부터 이 standby db에 새로운 기능이 추가되어, 이전 version에서,
    주기적으로 archive file 적용 및 recover 작업을 수행해야 하는 필요를 덜어
    주었다.
    단, Automated Standby database Feature는 8i~10g Standard Edition에서는
    지원하지 않는다.
    이 문서에서 자세한 설정 방법 및 추가된 기능들을 확인한다.
    1. 추가된 기능 정리
    (1) primary db에서 archive file생성시 standby db에도 자동 전달
    (2) standby db에 전달된 archive file이 자동으로 standby db에 적용
    (3) standby db activate없이, standy db를 read only mode로 open
    2. 구성 절차
    (1) standby db가 구성될 system에 oracle을 primary db와 동일한 version으로
    install한다.
    - OS는 primary db와 동일해야 한다.
    - database는 install할 필요없이, software만 install하면 된다.
    - datafile, controlfile, redo log file이 생성될 directory를 만들어
    둔다.
    (가능하면 primary db와 동일한것이 좋다),
    (2) primary db의 init.ora를 standby db에 copy한다.
    - primary db의 $ORACLE_HOME/dbs/initSID.ora file을 standby db에
    copy한다.
    - initSID.ora file에 ifile=로 정의된 file이 있다면 그 file도 해당
    directory에 copy한다.
    - 이러한 initial parameter중 background_dump_dest, user_dump_dest,
    core_dump_dest, archive_log_dest 등에 지정된 directory도 standby 쪽,
    server에 생성해둔다.
    (3) primary db에 multiple archive destination을 위한 parameter지정
    다음과 같은 형태로 primary db를 위한 archive parameter외에,
    standby db쪽에 자동으로 archive file이 생성되도록 destination을
    initSID.ora file에 지정한다.
    log_archive_start = true
    log_archive_dest_1 = "location=/user/oradata/archive"
    log_archive_format = arch%s.arc
    log_archive_dest_2 = 'SERVICE=sby OPTIONAL REOPEN=60'
    log_archive_dest_state_2 = ENABLE
    - 이 예에서 sby라는 것은 primary db의 tnsnames.ora file에 미리
    정의되어 있어야 하며, standby db에 대한 description을 가져야 한다.
    - REOPEN은 standby db쪽으로 archive가 실패한경우 지정된 초만큼 후에
    다시 archive를 시도하라는 의미이다.
    - OPTIONAL의 의미는 지정된 archive가 실패하는 경우라도 primary db의
    log_archive_dest_1에 지정된 곳에 archive만 성공하면 archive작업을
    중단없이 계속 진행하라는 것이다.
    (4) standby db의 initSID.ora file 수정
    primary db에서 자동으로 전달되어온 archive file이 위치하게 될
    destination과 datafile이나 redo log file이 위치할 directory 구조가
    primary db와 다른 경우를 대비한 parameter를 다음 예와 같이 설정한다.
    standby_archive_dest=/user/oradata/archive
    log_archive_start = true
    log_archive_dest_1 = "location=/user/oradata/archive"
    log_archive_format = arch%S.ARC
    db_file_name_convert="PROD","SBY"
    log_file_name_convert="PROD","SBY"
    - standby_archive_dest는 primary db에서 multiple archive destination을
    지정하는 경우 자동으로 생성될 archive file의 위치를 나타낸다.
    - standby_archive_dest뒤에는 log_archive_dest와 같은 location=은
    적으면 안된다. 적을시엔 자동으로 archive가 전달되지 않고, primary db의
    alert.log에 오류가 기록된다.
    - 실제 recover시나 이후 open되어 archive가 생성되는 시에는
    log_archive_dest 부분이 참조된다.
    - db_file_name_conver나 log_file_name_convert의 경우는, primary db와
    standby db간에 datafile, redo log file이 위치하는 directory가 다른
    경우 directory 이름중 다른 부분을 치환하도록 하는 것이다.
    이 경우 primary db는 /user/oradata/PROD directory에 file이 존재하고,
    standby db는 /user/oradata/SBY directory에 위치하는 경우에 대한 예이다.
    - 만약 datafile이 여러군데 나뉘어져 있어 이런 변경 부분이 더 필요하다면
    다음과 같이 할 수 있다.
    db_file_name_convert=('/dbs/t1/','/dbs/t1/s_','dbs/t2/','dbs/t2/s_')
    - WindowsNT의 경우는 반드시 directory이름을 반드시 대문자로 하여야 한다.
    (5) standby db용 controlfile을 생성
    다음 문장을 primary db에서 수행한다. 이후 이렇게 생성된 file은
    standby db쪽으로 옮겨질 것이다.
    SQL> alter database create standby controlfile as
    '/user/oradata/temp/control01.ctl';
    (5) primary db의 datafile을 backup받아둔다.
    db를 shutdown 시켜 cold backup을 받거나, hot backup을 받는다.
    tape등에 backup받는 대신 바로 ftp 등으로 standby db disk로
    옮겨도 된다.
    (6) 위의 (4),(5)에서 만들어진 controlfile과 datafile을 standby db쪽으로
    옮긴다.
    (7) standby db에서 다음과 같이 수행한다.
    os> sqlplus internal
    SQL> startup nomount
    SQL> alter database mount standby database;
    SQL> recover managed standby database;
    - 만약 recover managed standby database대신에 그냥
    recover standby database하면, ora-279, 280, 289가 발생하면서,
    생성된 archive를 manual하게 적용하면 된다.
    (8) standby db에서 primary db가 운영중에 test나 다른 목적으로 data를 읽고자
    한다면 read only로 open가능
    SQL>alter database open read only;
    (9) primary db가 crash가 발생하여 standby db를 운영하고자 한다면 다음과 같이
    activate시켜야 하며, 이렇게 한 이후로는 이 standby db는 standby 의 속성은
    잃게 되며, 이후에 다시 standby db로 구축하려면 다시 (5)번부터 작업을
    재수행하여 구축하여야 한다.
    SQL>alter database activate standy database;
    SQL>shutdown
    SQL>startup
    - shutdown후 이제는 더 이상 standby db가 아니므로 primary성격의 multiple
    archive destination지정 등을 원하는 경우 parameter를 추가하면 된다.
    3. managed recover, read only mode open 관리
    (1) managed recover
    recover managed database를 수행한 창은 계속 새로 전달되온 archive file을
    자동으로 recovery를 시켜준다.
    이때 필요에 의해 이 자동 recovery를 중단하고자 한다면,
    standby에서 다른 session을 연결하여 다음과 같이 수행하면 된다.
    SQL>alter database recover managed standby database cancel;
    이렇게 하면,
    recover managed standby 상태의 창에서,
    ora-283, ora-16037 메시지와 함께, managed recovery가 중단되고,
    SQL혹은 SVRMGR prompt상태가 된다.
    recover managed standby database와 일반, recover standby database는 필요에
    따라, 선택하여 사용하면 되며, recover managed standby databse의 경우 이
    문장을 실행한 이후에 생성된 archive file만을 자동 recovery한다.
    즉, recover managed standby database문장 수행전에 미리 전달되어 온 archive
    file이 있다면, 일단 먼저 recover standby database문장을 통해 recovery를
    수행한 이후에, recovey managed standby database문장을 수행하여야 한다.
    (2) read only mode open
    standby db를 standby db 속성은 그대로 유지하면서 dml 외에 data나 dictionary
    조회가 필요한 상황에서는
    alter database open read only문장을 수행하여 read only mode로 open할 수 있다.
    이렇게 조회후에, 다른 작업없이 recover 문장을 수행하면 다시 mount상태가 되는
    것이며, 필요하면 다시 open read only를 하여야 한다.
    standby db는 운영 중에 shutdown가 mount, open을 마음대로 할 수 있으나
    그 때마다 반드시,
    startup nomount;
    alter database mount standby database;
    (필요한 경우 alter database open read only)
    문장을 통해 mount나 open 상태가 되도록 하여야 한다.
    Reference Documents
    <Note:74185.1> Standby Database and Oracle 8.1
    <Note:70233.1> How to Create a Oracle 8i Standby Database

  • ORA-01242: data file suffered media failure - ORA-01208: data file is an

    Hi,
    I am running Oracle 9.2.0.5 and if fails almost on a daily basis.
    I get the following errors:
    *** 2008-04-09 09:31:46.334
    *** SESSION ID:(4.1) 2008-04-09 09:31:46.318
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 11 failed verification check
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\MYDB\MYDB.ORA'
    ORA-01208: data file is an old version - not accessing current version
    error 1242 detected in background process
    ORA-01242: data file suffered media failure: database in NOARCHIVELOG mode
    ORA-01122: database file 11 failed verification check
    ORA-01110: data file 11: 'E:\ORACLE\ORADATA\MYDB\MYDB.ORA'
    ORA-01208: data file is an old version - not accessing current version
    I run the following SQL and DB is recovered but I can't keep doing this everytime it crashes:
    sqlplus>startup nomount;
    sqlplus>alter database mount;
    sqlplus>alter database recover;
    sqlplus> alter database open;
    Any ideas how can I resolve this problem.
    Regards
    Spiros

    Refer to this metalink note:
    ORA-1242, ORA-1122, ORA-1110 & ORA-1208 Errors Occurring Intermittently
    Doc ID: Note:471280.1
    Werner

  • ORA-01157: cannot identify/lock data file 13 - see DBWR trace file

    Hi all,
    I've a Oracle Database 11g Release 11.1.0.6.0 - 64bit Production With the Real Application Clusters option.
    I'm using ASM.
    Yesterday I added new disks and then I changed the +/etc/udev/rules.d/98-oracle.rules+ file.
    Now it looks like this (the bolded are the new ones):
    # Oracle Configuration Registry
    KERNEL=="emcpowerd1", OWNER="root", GROUP="oinstall", MODE="640", NAME="ocr"
    # Voting Disks
    KERNEL=="emcpowerr1", OWNER="oracle", GROUP="oinstall", MODE="640", NAME="voting"
    # Spfile ASM+
    KERNEL=="emcpowers1", OWNER="oracle", GROUP="dba", MODE="660", NAME="spfileASM"
    # ASM Devices
    KERNEL=="emcpowerj1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm0" #onlineredo asm disk
    KERNEL=="emcpowern1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm1" #data asm disk
    KERNEL=="emcpowerh1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm2" #data asm disk
    KERNEL=="emcpowerq1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm3" #data asm disk
    KERNEL=="emcpowere1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm4" #data asm disk
    KERNEL=="emcpowerg1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm5" #data asm disk
    KERNEL=="emcpowerl1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm6" #data asm disk
    KERNEL=="emcpowero1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm7" #data asm disk
    KERNEL=="emcpowerf1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm8" #data asm disk
    KERNEL=="emcpowerm1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm9" #data asm disk
    KERNEL=="emcpoweri1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm10" #data asm disk
    KERNEL=="emcpowerp1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm11" #data asm disk
    KERNEL=="emcpowerk1", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm12" #data asm disk
    KERNEL=="emcpowert", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm210" #data asm disk SATA
    KERNEL=="emcpowerc", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm211" #data asm disk SATA
    KERNEL=="emcpowerb", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm212" #data asm disk SATA
    KERNEL=="emcpowera", OWNER="oracle", GROUP="dba", MODE="660", NAME="asm213" #data asm disk SATA
    It's the same on both RAC nodes.
    The operating system, a RedHat 5.4, see the new devices (both nodes):
    ls -ltr /dev/asm*
    brw-rw---- 1 oracle dba 120, 16 May 18 10:03 /dev/asm212
    brw-rw---- 1 oracle dba 120, 304 May 18 10:03 /dev/asm210
    brw-rw---- 1 oracle dba 120, 32 May 18 10:03 /dev/asm211
    brw-rw---- 1 oracle dba 120, 0 May 18 10:03 /dev/asm213
    brw-rw---- 1 oracle dba 120, 209 May 18 10:05 /dev/asm1
    brw-rw---- 1 oracle dba 120, 81 May 18 13:40 /dev/asm8
    brw-rw---- 1 oracle dba 120, 97 May 18 13:40 /dev/asm5
    brw-rw---- 1 oracle dba 120, 193 May 18 13:40 /dev/asm9
    brw-rw---- 1 oracle dba 120, 161 May 18 13:40 /dev/asm12
    brw-rw---- 1 oracle dba 120, 241 May 18 13:40 /dev/asm11
    brw-rw---- 1 oracle dba 120, 177 May 18 13:40 /dev/asm6
    brw-rw---- 1 oracle dba 120, 225 May 18 13:40 /dev/asm7
    brw-rw---- 1 oracle dba 120, 65 May 18 13:40 /dev/asm4
    brw-rw---- 1 oracle dba 120, 129 May 18 13:40 /dev/asm10
    brw-rw---- 1 oracle dba 120, 257 May 18 13:40 /dev/asm3
    brw-rw---- 1 oracle dba 120, 113 May 18 13:40 /dev/asm2
    brw-rw---- 1 oracle dba 120, 145 May 18 13:40 /dev/asm0
    Both ASM instance see new devices:
    From ASM1
    SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:43:10 2010
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
    With the Real Application Clusters option
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM1
    SQL> select path from v$asm_disk;
    PATH
    /dev/asm212
    /dev/asm211
    /dev/asm213
    /dev/asm210
    /dev/asm1
    /dev/asm4
    /dev/asm5
    /dev/asm0
    /dev/asm12
    /dev/asm9
    /dev/asm2
    /dev/asm10
    /dev/asm7
    /dev/asm11
    /dev/asm3
    /dev/asm8
    /dev/asm6
    17 rows selected.
    SQL>
    From ASM2
    SQL*Plus: Release 11.1.0.6.0 - Production on Tue May 18 13:42:39 2010
    Copyright (c) 1982, 2007, Oracle. All rights reserved.
    Connected to:
    Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
    With the Real Application Clusters option
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM2
    SQL> select path from v$asm_disk;
    PATH
    /dev/asm213
    /dev/asm211
    /dev/asm210
    /dev/asm212
    /dev/asm8
    /dev/asm7
    /dev/asm6
    /dev/asm11
    /dev/asm4
    /dev/asm12
    /dev/asm5
    /dev/asm9
    /dev/asm1
    /dev/asm3
    /dev/asm10
    /dev/asm2
    /dev/asm0
    17 rows selected.
    SQL>
    Then I created a disk group:
    CREATE DISKGROUP STORE EXTERNAL REDUNDANCY DISK '/dev/asm210';
    Then I created a new tablespace:
    CREATE TABLESPACE store DATAFILE '+STORE';
    I did all this operations from NODE1.
    What is happening now is that everytime I try to read something from new diskgroup FROM NODE2 I get the ORA-01157:
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707
    No problem to read from NODE1.
    The simple query on dba_data_file work from NODE1 and fails from NODE2 with the ORA-01157.
    I found this on the alert log:
    <msg time='2010-05-18T10:06:41.084+00:00' org_id='oracle' comp_id='rdbms'
    client_id='' type='UNKNOWN' level='16'
    module='' pid='11014'>
    <txt>Errors in file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc:
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: &apos;+STORE/evodb/datafile/store.256.719232707&apos;
    </txt>
    </msg>
    And this from the trace:
    Trace file /u01/app/oracle/diag/rdbms/evodb/EVODB2/trace/EVODB2_smon_11014.trc
    Oracle Database 11g Release 11.1.0.6.0 - 64bit Production
    With the Real Application Clusters option
    ORACLE_HOME = /u01/app/oracle/product/11.1.0/db1
    System name: Linux
    Node name: node02
    Release: 2.6.18-128.7.1.el5
    Version: #1 SMP Wed Aug 19 04:00:49 EDT 2009
    Machine: x86_64
    Instance name: EVODB2
    Redo thread mounted by this instance: 2
    Oracle process number: 19
    Unix process pid: 11014, image: oracle@node02 (SMON)
    *** 2010-05-18 10:06:41.084
    *** SESSION ID:(151.1) 2010-05-18 10:06:41.084
    *** CLIENT ID:() 2010-05-18 10:06:41.084
    *** SERVICE NAME:(SYS$BACKGROUND) 2010-05-18 10:06:41.084
    *** MODULE NAME:() 2010-05-18 10:06:41.084
    *** ACTION NAME:() 2010-05-18 10:06:41.084
    DDE rules only execution for: ORA 1110
    ----- START Event Driven Actions Dump ----
    ---- END Event Driven Actions Dump ----
    ----- START DDE Actions Dump -----
    ----- DDE Action: 'DB_STRUCTURE_INTEGRITY_CHECK' (Async) -----
    Successfully dispatched
    ----- (Action duration in csec: 0) -----
    ----- END DDE Actions Dump -----
    *** 2010-05-18 10:06:41.084
    SMON: following errors trapped and ignored:
    ORA-01157: cannot identify/lock data file 13 - see DBWR trace file
    ORA-01110: data file 13: '+STORE/evodb/datafile/store.256.719232707'
    Any suggestion about how to solve the problem?
    Thanks in advance!
    Samuel

    I didn't understand what do you mean with thread...
    But I think you found the problem
    Initialization files of both ASM instance are: SPFILE='/dev/spfileASM'
    that SPFILE is (common for both):
    +ASM2.__oracle_base='/u01/app/oracle'#ORACLE_BASE set from environment
    +ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
    +ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'#Manual Mount
    *.asm_diskstring='/dev/asm*'
    *.cluster_database=true
    *.diagnostic_dest='/u01/app/oracle'
    +ASM1.instance_number=1
    +ASM2.instance_number=2
    *.instance_type='asm'
    *.large_pool_size=12M
    +ASM1.local_listener='LISTENER_ASM'
    +AC
    Then I executed another query:
    From ASM1
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM1
    SQL> select name, state from v$asm_diskgroup;
    NAME STATE
    ARCHIVELOG MOUNTED
    DATA MOUNTED
    ONLINELOG MOUNTED
    STORE MOUNTED
    SQL>
    From ASM2
    SQL> select instance_name from v$instance;
    INSTANCE_NAME
    +ASM2
    SQL> select name, state from v$asm_diskgroup;
    NAME STATE
    ARCHIVELOG MOUNTED
    DATA MOUNTED
    ONLINELOG MOUNTED
    STORE DISMOUNTED
    SQL>
    Than the question is:
    how can I mount the disk group STORE also on ASM2?
    I think the problems is into the spfile lines:
    +ASM2.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA'
    +ASM1.asm_diskgroups='ONLINELOG','ARCHIVELOG','DATA','STORE'
    How can I change the +ASM2.asm_diskgroups value?
    Thanks

  • ORA-01189: file is from a different RESETLOGS than previous files

    Hi,
    I am trying to clone a database A from B.. the cloning is on the same server.. they are both oracle 8i databases... my OS is sun solaris 8...
    I followed the steps outlined in the following article:
    http://www.samoratech.com/TopicOfInterest/swCloneDB.htm
    Now, while creating the control file on target server, i am getting the erorr:
    CREATE CONTROLFILE SET DATABASE "GNXDBT02" RESETLOGS NOARCHIVELOG
    ERROR at line 1:
    ORA-01503: CREATE CONTROLFILE failed
    ORA-01189: file is from a different RESETLOGS than previous files
    ORA-01110: data file 40: '/dbase17/oradata/gnxdbt02/ts_objs_vlarge_06.dbf'
    It means that the file is from a time before a prev. resetlogs and hence is invalid.. I don't have a old copy of this file before prev. reset logs.. so in that case what options can i apply to open the DB and also not lost the data in that datafile?
    thx

    Hi,
    According to documentation:
    Cause: In a CREATE CONTROLFILE command, either this file or all previous
    files were backups from before the last RESETLOGS.
    This also may occur if this is a file that is offline and has been
    offline since before the last RESETLOGS.
    Action: If the file was taken offline normally before the last RESETLOGS and
    is still offline, omit it from the CREATE CONTROLFILE command.
    Rename and online the file after the database is open.
    Otherwise, find the version of the mentioned file consistent with the
    rest of the datafiles and retry the command.
    If is the case, you can try edit the CREATE CONTROLFILE script, omit the erroring datafile listed in the ORA-1110 error, from the CREATE CONTROLFILE script, rerun the CREATE CONTROLFILE script and after the database is open, rename and manually online the erroring datafile.
    Cheers

Maybe you are looking for

  • How do I change text size in auto-page tabs

    Now I'm trying to make the page tabs fit across my page. I've got several pages and will probably have more. I don't want all of them on the bar as they'll be linked in my text. I would also like to make the text smaller and maybe reformat to another

  • Error while doing EHP4 upgrade

    Hello Colleagues, While doing EHP4 upgrade on windows 2008 server in extraction phase, i am getting following error message: Unable to execute the SDT request ABAP operation extract on hostname inmumeucpi instance 00 Extraction of the ABAP upgrade re

  • Creating Key Figures

    Hello everyone, I'm currently trying to build my own AR Aging Report as the standard one does not include a couple extension fields that I need. I've already created my Data Source but the Key Figure Group that is in the standard AR Aging Report is s

  • Multiple logins to wake up MBP

    When I open up my MBP, I log in like normal. Then it acts like its going to let me in, only to go black again, or stall, or ask me to log in again. So I do log in again.  Then it stalls (can't even move the mouse), and sometimes it'll fix itself afte

  • Safari won't open a new page

    When I open Safari on my macbook, all it does is open the window and show me a non-blinking cursor in the address bar. I can't type anything in, and nothing happens. I'm running with all the latest updates installed, and confirmed that through the up