标签云
asm恢复 bbed bootstrap$ dul kcbzib_kcrsds_1 kccpb_sanity_check_2 kcratr_nab_less_than_odr MySQL恢复 obet ORA-00312 ORA-00704 ORA-00742 ORA-01110 ORA-01200 ORA-01555 ORA-01578 ORA-01595 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-600 kcratr_nab_less_than_odr 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 比特币加密文章分类
- MongoDB (1)
- MongoDB恢复 (1)
- Others (2)
- 中间件 (2)
- WebLogic (2)
- 操作系统 (112)
- 数据库 (1,885)
- DB2 (22)
- MySQL (82)
- Oracle (1,710)
- Data Guard (53)
- EXADATA (8)
- GoldenGate (24)
- ORA-xxxxx (168)
- ORACLE 12C (72)
- ORACLE 18C (6)
- ORACLE 19C (15)
- ORACLE 21C (3)
- Oracle 23ai (8)
- Oracle ASM (73)
- Oracle Bug (8)
- Oracle RAC (56)
- Oracle 安全 (6)
- Oracle 开发 (28)
- Oracle 监听 (29)
- Oracle备份恢复 (663)
- Oracle安装升级 (108)
- Oracle性能优化 (62)
- 专题索引 (5)
- 勒索恢复 (91)
- PostgreSQL (37)
- pdu工具 (7)
- PostgreSQL恢复 (13)
- SQL Server (34)
- SQL Server恢复 (14)
- TimesTen (7)
- 达梦数据库 (5)
- 达梦恢复 (3)
- 生活娱乐 (2)
- 至理名言 (11)
- 虚拟化 (2)
- VMware (2)
- 软件开发 (51)
- Asp.Net (9)
- JavaScript (12)
- PHP (2)
- 小工具 (34)
- MongoDB (1)
-
最近发表
- 恢复案例分享:win丢失数据文件恢复
- 记录19c ASM磁盘掉线触发ORA-59048故障处理
- aix平台Oracle数据库由于断电无法启动故障处理
- 断电引起ORA-600 3005故障处理
- 记录一次云存储资源到期之后引起的数据库恢复
- Firebird 损坏数据库数据抢救工具—firebirdext
- Oracle 19c 202610补丁(RUs+OJVM)-19.33
- 由于con$.con#值达到极限,触发数据库增加约束报ORA-600 12807错误
- MongoDB 离线提取工具—mongoext
- .bres勒索病毒加密数据库dmp文件可恢复
- ORA-600 krsm_mrp_rebuild_lf_list.lno_mismatch
- 记录一次0丢失的ORA-00354: 损坏重做日志块标头故障恢复
- 不当数据库恢复操作导致一个月数据丢失
- obet快速修复oracle 位图损坏块
- 不太常见的10.2.0.1的oracle redo损坏恢复
- obet forcecopy功能抢救硬件故障中的数据文件
- kcratr_nab_less_than_odr和system坏块故障处理
- 通过obet 恢复system坏块,打开数据库
- obet dbv功能完整说明
- 分享一例运行在aix上的sap系统数据库恢复过程
分类目录归档:ORA-xxxxx
ORA-07445 [ACCESS_VIOLATION] [UNABLE_TO_READ] []
alert中发现ORA-07445错误
ORA-07445: exception encountered: core dump [PC:0x7FFF65D0] [ACCESS_VIOLATION] [ADDR:0xFFFFFFFF] [PC:0x7FFF65D0] [UNABLE_TO_READ] []错误,导致数据库down掉
Mon May 14 14:34:34 2012
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xFFFFFFFF] [PC:0x7FFF65D0, {empty}]
Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_p001_1280.trc:
ORA-07445: exception encountered: core dump [PC:0x7FFF65D0] [ACCESS_VIOLATION]
[ADDR:0xFFFFFFFF] [PC:0x7FFF65D0] [UNABLE_TO_READ] []
Mon May 14 14:34:35 2012
Trace dumping is performing id=[cdmp_20120514143435]
Mon May 14 14:35:10 2012
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xFFFFFFFF] [PC:0x7FFF65D0, {empty}]
Errors in file d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_smon_1072.trc (incident=164712):
ORA-07445: exception encountered: core dump [PC:0x7FFF65D0] [ACCESS_VIOLATION]
[ADDR:0xFFFFFFFF] [PC:0x7FFF65D0] [UNABLE_TO_READ] []
ORA-12080: Buffer cache miss for IOQ batching
Incident details in: d:\app\administrator\diag\rdbms\orcl\orcl\incident\incdir_164712\orcl_smon_1072_i164712.trc
分析trace文件
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Windows Server 2003 Version V5.2 Service Pack 2
CPU : 8 - type 586, 4 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:4892M/8189M, Ph+PgF:5638M/9795M, VA:925M/4095M
Instance name: orcl
Redo thread mounted by this instance: 1
Oracle process number: 12
Windows thread id: 1072, image: ORACLE.EXE (SMON)
--以上信息得出操作系统和数据库版本2003 sp2+oracle11g(11.1.0.6 32位)
Dump continued from file: d:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_smon_1072.trc
ORA-07445: exception encountered: core dump [PC:0x7FFF65D0] [ACCESS_VIOLATION]
[ADDR:0xFFFFFFFF] [PC:0x7FFF65D0] [UNABLE_TO_READ] []
ORA-12080: Buffer cache miss for IOQ batching
========= Dump for incident 164712 (ORA 7445 [PC:0x7FFF65D0]) ========
----- Beginning of Customized Incident Dump(s) -----
Exception [type: ACCESS_VIOLATION, UNABLE_TO_READ] [ADDR:0xFFFFFFFF] [PC:0x7FFF65D0, {empty}]
--这里的ORA-07445 [ACCESS_VIOLATION][UNABLE_TO_READ]根据经验结合这里的32位的环境,
--怀疑是sga使用的内存太多,ORACLE数据库不能读SGA相关内存导致
--在trace中找出相关参数配置.
[0004]: processes=300
[0004]: sessions=335
[0004]: __shared_pool_size=1124073472
[0004]: __large_pool_size=8388608
[0004]: __java_pool_size=16777216
[0004]: __streams_pool_size=251658240
[0004]: streams_pool_size=251658240
[0004]: sga_target=0
[0004]: __sga_target=1887436800
[0004]: memory_target=3145728000
[0004]: memory_max_target=4722786304
[0004]: db_block_size=8192
[0004]: __db_cache_size=478150656
[0004]: __shared_io_pool_size=0
[0004]: compatible=11.1.0.0.0
[0004]: log_buffer=8851456
[0004]: __pga_aggregate_target=780140544
--这里可以看到sga_target分配了内存为1887436800=1.7578125G
--pga_aggregate_target分配了780140544=0.7265625G
--两者内存之和大于2G,超过了32位ORACLE默认限制
查询MOS发现[1341681.1]
该错误原因
This is a resource issue (memory in particular). 32-bit windows systems, are limited to 2GB of addressable memory so if you are on this platform it's likely you are simply exceeding the capabilities of the 32bit operating system.
解决建议
First recommendation : If you have not already done so, add the /3GB switch to your boot.ini file and reboot the server. The boot.ini will be located in the root directory on the drive where windows is installed. The switch, /3GB, is placed at the end of the line that executes the WinNT loading process. This will allow applications such as oracle access to 3Gb or memory instead of 2Gb. Example: [operating systems] multi(0)disk(0)rdisk(0)partition(2)\WINNT="Windows NT Server Version 4.00" /3GB Second recommendation : You do not want to increase memory target. If anything, this should be decreased. You are limited to under 2GB of addressable memory on 32bit windows (the limit is actually about 1.85GB). This is for both SGA and PGA memory for all instances; you have to reduce the SGA size for the instance. The recommendation is to reduce sga_target, memory_target, and memory_max_target.
9i库遇到ORA-01595/ORA-01594
在alert日志中发现ORA-01595/ORA-01594错误
Sat May 12 21:54:17 2012 Errors in file /oracle/app/admin/prmdb/bdump/prmdb2_smon_483522.trc: ORA-01595: error freeing extent (2) of rollback segment (19)) ORA-01594: attempt to wrap into rollback segment (19) extent (2) which is being freed
分析trace文件
Oracle9i Enterprise Edition Release 9.2.0.8.0 - 64bit Production With the Partitioning, Real Application Clusters, OLAP and Oracle Data Mining options JServer Release 9.2.0.8.0 - Production ORACLE_HOME = /oracle/app/product/9.2.0 System name: AIX Node name: prmsvr2 Release: 3 Version: 5 Machine: 0008585FD600 Instance name: prmdb2 Redo thread mounted by this instance: 2 Oracle process number: 14 Unix process pid: 483522, image: oracle@prmsvr2 (SMON) *** 2011-05-03 15:28:47.858 *** SESSION ID:(17.1) 2011-05-03 15:28:47.843 *** 2011-05-03 15:28:47.858 SMON: Parallel transaction recovery tried *** 2011-07-11 17:13:52.028 SMON: Restarting fast_start parallel rollback *** 2011-07-11 17:28:39.705 SMON: Parallel transaction recovery tried *** 2012-05-12 21:54:17.246 --当前问题时间点 SMON: following errors trapped and ignored: ORA-01595: error freeing extent (2) of rollback segment (19)) ORA-01594: attempt to wrap into rollback segment (19) extent (2) which is being freed --通过trace文件,我们没有获得关于该错误的其他有用信息
查询MOS相关信息[280151.1]
出现该错误原因
This is a known problem and there is an Internal Bug:2181139 for this Issue. The error is signaled because smon is shrinking a rollback segment and this fails because we need an extent to store some rollback information. This is a failure message for the shrinking. Subsequently smon would succeed in doing that. --当smon在shrink rollback segment因为需要一个extent存放rollback
解决建议
Ignore these error messages. Normally adding more undo space should solve the problem, but if space is not correcting the problem, please file an SR for assistance. This error message logging is fixed in 10g. --忽略该错误或者升级到10g
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.

加我微信(17813235971)
加我QQ(107644445)

