标签云
asm 恢复 asm恢复 bbed bootstrap$ dul In Memory kcbzib_kcrsds_1 kccpb_sanity_check_2 kfed MySQL恢复 ORA-00312 ORA-00607 ORA-00704 ORA-01110 ORA-01555 ORA-01578 ORA-08103 ORA-600 2662 ORA-600 2663 ORA-600 3020 ORA-600 4000 ORA-600 4137 ORA-600 4193 ORA-600 4194 ORA-600 16703 ORA-600 kcbzib_kcrsds_1 ORA-600 KCLCHKBLK_4 ORA-15042 ORA-15196 ORACLE 12C oracle dul ORACLE PATCH Oracle Recovery Tools oracle加密恢复 oracle勒索 oracle勒索恢复 oracle异常恢复 ORACLE恢复 Oracle 恢复 ORACLE数据库恢复 oracle 比特币 OSD-04016 YOUR FILES ARE ENCRYPTED 勒索恢复 比特币加密文章分类
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (100)
- 数据库 (1,603)
- DB2 (22)
- MySQL (70)
- Oracle (1,468)
- Data Guard (50)
- EXADATA (7)
- GoldenGate (21)
- ORA-xxxxx (158)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (13)
- ORACLE 21C (3)
- Oracle 23ai (3)
- Oracle ASM (65)
- Oracle Bug (7)
- Oracle RAC (47)
- Oracle 安全 (6)
- Oracle 开发 (27)
- Oracle 监听 (27)
- Oracle备份恢复 (532)
- Oracle安装升级 (84)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (75)
- PostgreSQL (18)
- PostgreSQL恢复 (6)
- SQL Server (27)
- SQL Server恢复 (8)
- TimesTen (7)
- 达梦数据库 (2)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (36)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (19)
-
最近发表
- WINDOWS 下用dg broker搭建ADG(单机to单机)
- 存储故障后oracle报—ORA-01122/ORA-01207故障处理
- Oracle 23ai rm redo*.log恢复
- Oracle 发布计划—包含Oracle 23ai版本
- Oracle 23ai 变化之—-默认数据文件变为bigfile
- PostgreSQL解析wal日志之—walminer
- Oracle 19c/21c最新patch信息-202404
- PostgreSQL恢复系列:pg_filedump批量处理
- PostgreSQL部分主要字典信息
- PostgreSQL恢复系列:pg_filedump恢复字典构造
- PostgreSQL 16 源码安装
- ORA-00742 ORA-00312 恢复
- 数据库open成功后报ORA-00353 ORA-00354错误引起的一系列问题(本质ntfs文件系统异常)
- ORA-600 ktsiseginfo1故障
- ORA-00600: internal error code, arguments: [16703], [1403], [4] 原因
- 最近遇到几起ORA-600 16703故障(tab$被清空),请引起重视
- ORA-600 2662快速恢复之Patch scn工具
- TNS-12518: TNS:listener could not hand off client connection
- ora.storage无法启动报ORA-12514故障处理
- 断电引起文件scn异常数据库恢复
标签归档:ORA-7445[dbgrmqmqpk_query_pick_key()+0f88]
ORA-07445[dbgrmqmqpk_query_pick_key()+0f88]
alert发现如下错误ORA-07445[dbgrmqmqpk_query_pick_key()+0f88]
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0xB38F0000000049] [PC:0x100213C08, dbgrmqmqpk_query_pick_key()+0f88] Errors in file /oracle/diag/rdbms/sgerp5/sgerp5/trace/sgerp5_m000_7602504.trc (incident=579300): ORA-07445: exception encountered: core dump [dbgrmqmqpk_query_pick_key()+0f88] [SIGSEGV] [ADDR:0xB38F0000000049] [PC:0x100213C08] [Address not mapped to object] [] Incident details in: /oracle/diag/rdbms/sgerp5/sgerp5/incident/incdir_579300/sgerp5_m000_7602504_i579300.trc
trace文件部分信息
Dump file /oracle/diag/rdbms/sgerp5/sgerp5/incident/incdir_579300/sgerp5_m000_7602504_i579300.trc Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options ORACLE_HOME = /oracle/product/11.1.0/db_1 System name: AIX Node name: sgerp5 Release: 1 Version: 6 Machine: 00C8F0564C00 Instance name: sgerp5 Redo thread mounted by this instance: 1 Oracle process number: 138 Unix process pid: 7602504, image: oracle@sgerp5 (m000) --确定是m000进程出现异常,而该进程是awr收集统计信息进程MMON的子进程 *** 2012-05-11 03:52:35.200 *** SESSION ID:(752.5029) 2012-05-11 03:52:35.200 *** CLIENT ID:() 2012-05-11 03:52:35.200 *** SERVICE NAME:(SYS$BACKGROUND) 2012-05-11 03:52:35.200 *** MODULE NAME:(MMON_SLAVE) 2012-05-11 03:52:35.200 *** ACTION NAME:(Auto-Purge Slave Action) 2012-05-11 03:52:35.200 Dump continued from file: /oracle/diag/rdbms/sgerp5/sgerp5/trace/sgerp5_m000_7602504.trc ORA-07445: exception encountered: core dump [dbgrmqmqpk_query_pick_key()+0f88] [SIGSEGV] [ADDR:0xB38F0000000049] [PC:0x100213C08] [Address not mapped to object] [] ----- Incident Context Dump ----- Address: 0x1104bdb68 Incident ID: 579300 Problem Key: ORA 7445 [dbgrmqmqpk_query_pick_key()+0f88] Error: ORA-7445 [dbgrmqmqpk_query_pick_key()+0f88] [SIGSEGV] [ADDR:0xB38F0000000049] [PC:0x100213C08] [Address not mapped to object] [] [] [] [00]: dbgexExplicitEndInc [diag_dde] [01]: dbgeEndDDEInvocationImpl [diag_dde] [02]: dbgeEndDDEInvocation [diag_dde] [03]: ssexhd [] [04]: 47dc []<-- Signaling [05]: dbgrmqmfs_fetch_setup [ams_comp] [06]: dbgrmqmf_fetch_real [ams_comp] [07]: dbgrmqmf_fetch [ams_comp] [08]: dbgrip_fetch_record [ami_comp] [09]: dbgrip_relation_iterator [ami_comp] [10]: dbgripricm_rltniter_wcbf_mt [ami_comp] [11]: dbgripdrm_dmldrv_mt [ami_comp] [12]: dbghmm_delete_info_records [] [13]: dbghmo_purge_hm_schema [] [14]: dbgrupipscb_hm_pgsvc_cbf [diag_adr] [15]: dbgruppm_purge_main [diag_adr] [16]: dbkrapg_auto_purge [rdbms_adr] [17]: kewraps_auto_purge_slave [] [18]: kebm_slave_main [] [19]: ksvrdp [ksv_trace] [20]: opirip [] [21]: opidrv [] [22]: sou2o [] [23]: opimai_real [] [24]: main [] [25]: __start [] MD [00]: 'SID'='752.5029' (0x3) MD [01]: 'ProcId'='138.46' (0x3) MD [02]: 'PQ'='(0, 1336679546)' (0x7) MD [03]: 'Client ProcId'='oracle@sgerp5.7602504_1' (0x0)
MOS关于该问题记录
问题原因
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.
解决方案
- 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.