ORA-07445[dbgrmqmqpk_query_pick_key()]問題處理
故障描述:
- Alert日誌報如下錯誤:
Wed Nov 06 00:14:33 2013
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xFFFFFFFFFFFFFFFF] [PC:0x9155F46, dbgrmqmqpk_query_pick_key()+2014]
ERROR: Unable to normalize symbol name for the following short stack (at offset 199):
dbgexProcessError()+193 Errors in file c:\app\administrator\diag\rdbms\prones1\prones1\trace\prones1_m000_6420.trc (incident=552282):
ORA-07445: 出現異常錯誤: 核心轉儲 [dbgrmqmqpk_query_pick_key()+2014] [ACCESS_VIOLATION] [ADDR:0xFFFFFFFFFFFFFFFF] [PC:0x9155F46] [UNABLE_TO_READ] []
Incident details in: c:\app\administrator\diag\rdbms\prones1\prones1\incident\incdir_552282\prones1_m000_6420_i552282.trc
- Trace日誌報如下錯誤:
Dump file c:\app\administrator\diag\rdbms\prones1\prones1\incident\incdir_552282\prones1_m000_6420_i552282.trc
- Alert日誌報如下錯誤:
Wed Nov 06 00:14:33 2013
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xFFFFFFFFFFFFFFFF] [PC:0x9155F46, dbgrmqmqpk_query_pick_key()+2014]
ERROR: Unable to normalize symbol name for the following short stack (at offset 199):
dbgexProcessError()+193 Errors in file c:\app\administrator\diag\rdbms\prones1\prones1\trace\prones1_m000_6420.trc (incident=552282):
ORA-07445: 出現異常錯誤: 核心轉儲 [dbgrmqmqpk_query_pick_key()+2014] [ACCESS_VIOLATION] [ADDR:0xFFFFFFFFFFFFFFFF] [PC:0x9155F46] [UNABLE_TO_READ] []
Incident details in: c:\app\administrator\diag\rdbms\prones1\prones1\incident\incdir_552282\prones1_m000_6420_i552282.trc
- Trace日誌報如下錯誤:
Dump file c:\app\administrator\diag\rdbms\prones1\prones1\incident\incdir_552282\prones1_m000_6420_i552282.trc
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
Windows NT Version V6.1 Service Pack 1
CPU : 2 - type 8664, 2 Physical Cores
Process Affinity : 0x0x0000000000000000
Memory (Avail/Total): Ph:6678M/16383M, Ph+PgF:22920M/32765M
VM name : VMWare Version (6)
Instance name: prones1
Redo thread mounted by this instance: 1
Oracle process number: 35
Windows thread id: 6420, image: ORACLE.EXE (M000)
*** 2013-11-06 00:14:33.874
*** SESSION ID:(880.1788) 2013-11-06 00:14:33.874
*** CLIENT ID:() 2013-11-06 00:14:33.874
*** SERVICE NAME:(SYS$BACKGROUND) 2013-11-06 00:14:33.874
*** MODULE NAME:(MMON_SLAVE) 2013-11-06 00:14:33.874
*** ACTION NAME:(Auto-Purge Slave Action) 2013-11-06 00:14:33.874
Dump continued from file: c:\app\administrator\diag\rdbms\prones1\prones1\trace\prones1_m000_6420.trc
ORA-07445: 出現異常錯誤: 核心轉儲 [dbgrmqmqpk_query_pick_key()+2014] [ACCESS_VIOLATION] [ADDR:0xFFFFFFFFFFFFFFFF] [PC:0x9155F46] [UNABLE_TO_READ] []
========= Dump for incident 552282 (ORA 7445 [dbgrmqmqpk_query_pick_key()+2014]) ========
----- Beginning of Customized Incident Dump(s) -----
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xFFFFFFFFFFFFFFFF] [PC:0x9155F46, dbgrmqmqpk_query_pick_key()+2014]
Oracle Database 11g Release 11.2.0.1.0 - 64bit Production
Process Id: 0x000006c8 Thread Id : 0x00001914 Time : Wed Nov 06 00:14:33
Excp. Code: 0xc0000005 Excp. Type: ACCESS_VIO Flags: 0x00000000
MOS針對此問題的資訊:Cause
This is due to Bug 9390347 fixed in 12.1 & 11.2.0.2, where a core dump can occur in module dbgrmqmqpk_query_pick_key() whilst purging HM contents from ADR.
Solution
- Either install our 11.2.0.2 patchset
- Or download and apply Patch 9390347 if available for your version/platform.
- On Windows, you can also install Bundle Patch 11.1.0.7.31 or above.
There is no workaround to this error, however the error is not serious and does not cause any harm to your database.
現在還沒有辦法解決這個錯誤,但是錯誤並不嚴重,並不會造成任何傷害到你的資料庫。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/12974804/viewspace-775978/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- ORA-07445 & ORA-00108 問題處理
- ORA-07445 ACCESS_VIOLATION,UNABLE_TO_READ問題處理
- 處理問題的方法
- perl中文處理問題
- 漢字處理問題?
- xml處理的問題XML
- 貨品問題處理
- [git] git問題處理Git
- golang json處理問題GolangJSON
- 併發問題處理方式
- ASMCMD處理問題一則ASM
- mysql的處理能力問題MySql
- RMAN處理split block問題BloC
- mysql問題處理兩則MySql
- Oracle啟動問題處理Oracle
- mysql 問題處理二則MySql
- Oracle壞塊問題處理Oracle
- 資料處理--pandas問題
- 如何處理 No DMARC Record Found 問題
- PHP 開發版本問題處理PHP
- MySQL:亂碼問題處理流程MySql
- JVM問題分析處理手冊JVM
- Linux 問題處理集錦Linux
- 處理SQLServer errorlog滿問題SQLServerError
- 如何處理HTTP 503故障問題?HTTP
- gc buffer busy acquire問題處理GCUI
- 記憶體分配問題處理記憶體
- RDSforMySQLMysqldump常見問題和處理ORMMySql
- ORA-00942問題處理
- crontab 問題檢查與處理
- ORA-38760 問題處理方法
- 一個NBU問題的處理
- Lotus notes問題與處理
- HTML + CSS處理常見問題HTMLCSS
- Java 大資料量處理問題Java大資料
- mysql的處理能力問題(2)MySql
- crontab對oracle操作問題處理Oracle
- 【問題處理】“NOT IN”與“NULL”的邂逅Null