compatible相容引數不正確導致DG物理備庫不能應用日誌

2008081036發表於2014-05-23
日誌能傳輸到過來:
SQL> SELECT SEQUENCE#,FIRST_TIME,NEXT_TIME,applied from V$ARCHIVED_LOG ORDER BY SEQUENCE#;

 SEQUENCE# FIRST_TIME         NEXT_TIME          APP
---------- ------------------ ------------------ ---
        21 03-APR-13          03-APR-13          YES
        22 03-APR-13          03-APR-13          YES
        ……
        55 03-APR-13          03-APR-13          YES
        56 03-APR-13          03-APR-13          YES
        57 03-APR-13          03-APR-13          YES
        58 03-APR-13          04-APR-13          NO
        59 04-APR-13          05-APR-13          NO

但MRP0程式不能啟動:
SQL> select process,status,sequence#,block#,blocks from v$managed_standby;

PROCESS   STATUS        SEQUENCE#     BLOCK#     BLOCKS
--------- ------------ ---------- ---------- ----------
ARCH      CONNECTED             0          0          0
ARCH      CLOSING              56     100353        496
……
ARCH      CONNECTED             0          0          0
RFS       IDLE                  0          0          0
RFS       IDLE                  0          0          0


檢視警告日誌:
Thu Apr  4 11:01:48 2013
Media Recovery Log /archive/shanghai/1_58_811768827.arc
Errors with log /archive/shanghai/1_58_811768827.arc
MRP0: Background Media Recovery terminated with error 331
Thu Apr  4 11:01:48 2013
Errors in file /oracle/app/admin/rollup/bdump/rollup_mrp0_8248.trc:
ORA-00331: log version 10.2.0.4.0 incompatible with ORACLE version 10.2.0.1.0
ORA-00334: archived log: '/archive/shanghai/1_58_811768827.arc'
Managed Standby Recovery not using Real Time Apply
Recovery interrupted!
……

原因:
之前對主備庫都作了升級,主庫已經把相容性引數從10.2.0.1.0改到10.2.0.4.0,原以為備庫會應用日誌自動把引數修改,但顯然需要手工修改了。

解決方法:
把備庫的相容性引數修改到10.2.0.4.0:
SQL> alter system set compatible='10.2.0.4.0' scope=spfile;

來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/25465866/viewspace-1168665/,如需轉載,請註明出處,否則將追究法律責任。

相關文章