如何進(jìn)行ASM實(shí)例出現(xiàn)ORA-4031錯(cuò)誤導(dǎo)致實(shí)例崩潰的分析

這期內(nèi)容當(dāng)中小編將會(huì)給大家?guī)碛嘘P(guān)如何進(jìn)行ASM實(shí)例出現(xiàn)ORA-4031錯(cuò)誤導(dǎo)致實(shí)例崩潰的分析，文章內(nèi)容豐富且以專業(yè)的角度為大家分析和敘述，閱讀完這篇文章希望大家可以有所收獲。

數(shù)據(jù)庫的ASM實(shí)例出現(xiàn)了ORA-4031錯(cuò)誤，導(dǎo)致了數(shù)據(jù)庫實(shí)例的崩潰。

詳細(xì)的錯(cuò)誤信息為：

Wed Jul 25 08:03:45 2012
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_asmb_34668994.trc (incident=808023):
ORA-04031: unable to allocate 3432 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","ASM file")
Incident details in: /u01/app/oracle/diag/rdbms/orcl/ORCL1/incident/incdir_808023/ORCL1_asmb_34668994_i808023.trc
Wed Jul 25 08:03:47 2012
Trace dumping is performing id=[cdmp_20120725080347]
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_asmb_34668994.trc:
ORA-15064: communication failure with ASM instance
ORA-04031: unable to allocate 3432 bytes of shared memory ("shared pool","unknown object","sga heap(1,0)","ASM file")
ASMB (ospid: 34668994): terminating the instance due to error 15064
Wed Jul 25 08:03:47 2012
ORA-1092 : opiodr aborting process unknown ospid (29819058_1)
Wed Jul 25 08:03:48 2012
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_q002_25886884.trc:
ORA-15064: communication failure with ASM instance
Wed Jul 25 08:03:47 2012
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_arc3_36503776.trc:
ORA-15064: communication failure with ASM instance
Wed Jul 25 08:03:47 2012
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_q001_32374808.trc:
ORA-15064: communication failure with ASM instance
Errors in file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_arc3_36503776.trc:
ORA-15064: communication failure with ASM instance
Master archival failure: 15064
Wed Jul 25 08:03:48 2012
ORA-1092 : opiodr aborting process unknown ospid (12058986_1)
Wed Jul 25 08:03:49 2012
ORA-1092 : opitsk aborting process
Wed Jul 25 08:03:49 2012
License high water mark = 334
Instance terminated by ASMB, pid = 34668994
USER (ospid: 35914002): terminating the instance
Instance terminated by USER, pid = 35914002

顯然數(shù)據(jù)庫實(shí)例的出現(xiàn)的崩潰是由于ASM實(shí)例的錯(cuò)誤導(dǎo)致的。根據(jù)Oracle的推薦，在11g中使用MEMORY_TARGET參數(shù)的話，那么MEMORY_TARGET至少應(yīng)該分配256M以上，而且隨著DISK GROUP的容量的增長(zhǎng)，SHARED_POOL所需要的空間也隨著增加。因此對(duì)于磁盤組空間比較大的ASM實(shí)例而言，采用默認(rèn)參數(shù)作為MEMORY_TARGET顯然是不夠的。

對(duì)于當(dāng)前環(huán)境，只需要簡(jiǎn)單的調(diào)整ASM實(shí)例的MEMORY_TARGET參數(shù)，將其擴(kuò)大到500M以上，就可以避免該錯(cuò)誤的產(chǎn)生。

上述就是小編為大家分享的如何進(jìn)行ASM實(shí)例出現(xiàn)ORA-4031錯(cuò)誤導(dǎo)致實(shí)例崩潰的分析了，如果剛好有類似的疑惑，不妨參照上述分析進(jìn)行理解。如果想知道更多相關(guān)知識(shí)，歡迎關(guān)注億速云行業(yè)資訊頻道。