資料庫異機恢復開啟報錯ORA-36961

yangtingkun發表於2012-08-19

客戶在異機進行資料庫的不完全恢復,用來匯出被誤刪除的表,恢復完成後,開啟資料庫時出現了ORA-36961錯誤。

 

 

資料庫版本為10.2.0.4 for HP-UX,開啟資料庫前臺出現ORA-3113錯誤:

SQL> startup
Total System Global Area 4294967296 bytes
Fixed Size 2073472 bytes
Variable Size 805309568 bytes
Database Buffers 3472883712 bytes
Redo Buffers 14700544 bytes
Database mounted.
ORA-03113: end-of-file on communication channel

在啟動過程中,如果前臺出現ORA-3113錯誤,那麼後臺多半是ORA-600ORA-7445錯誤,檢查告警日誌,卻發現出現了ORA-36961錯誤:

Error in executing triggers on database startup
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15
Error in executing triggers on instance shutdown
ksedmp: internal or fatal error
ORA-00604: error occurred at recursive SQL level 1
ORA-12663: Services required by client not available on the server
ORA-36961: Oracle OLAP is not available.
ORA-06512: at "SYS.OLAPIHISTORYRETENTION", line 1
ORA-06512: at line 15

顯然這個錯誤和OLAP元件的不正常有關。由於是異機恢復,很可能新的ORACLE_HOME安裝的OLAP元件與原始環境不一致,根據文件'Ora-36961 Oracle OLAP is Not Available' error During database Startup [ID 1291894.1],需要啟用OLAP元件。由於OLAP元件所需要的xsyeolap.o檔案缺失,需要從安裝介質中獲取。首先需要從介質盤的目錄中複製Disk1/stage/Patches/oracle.rdbms.olap/10.2.0.5.0/1/DataFiles/filegroup1.1.1.jar檔案到臨時目錄,然後抽取檔案$ORACLE_HOME/jdk/bin/jar -xvf filegroup1.1.1.jar,最後將檔案xsyeolap.o複製到ORACLE_HOME/rdbms/lib

% cd $ORACLE_HOME/rdbms/lib
% make -f ins_rdbms.mk olap_on ioracle

重啟資料庫既可。

 

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

相關文章