标签云
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-00600[kcbshlc_1]导致数据库 down 案例
一台服务器因为ORA-00600[kcbshlc_1]错误引起PMON异常导致数据库down掉
Sun Jul 8 17:20:10 2012 Errors in file /opt/oracle/admin/xff/bdump/xff_pmon_16412.trc: ORA-00600: internal error code, arguments: [kcbshlc_1], [33], [], [], [], [], [], [] Sun Jul 8 17:20:12 2012 Errors in file /opt/oracle/admin/xff/bdump/xff_pmon_16412.trc: ORA-00600: internal error code, arguments: [kcbshlc_1], [33], [], [], [], [], [], [] Sun Jul 8 17:20:12 2012 PMON: terminating instance due to error 472
分析trace文件
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /opt/oracle/product/10.2.0
System name: Linux
Node name: localhost.localdomain
Release: 2.6.9-89.ELsmp
Version: #1 SMP Mon Apr 20 10:33:05 EDT 2009
Machine: x86_64
Instance name: xff
Redo thread mounted by this instance: 1
Oracle process number: 2
Unix process pid: 16412, image: oracle@localhost.localdomain (PMON)
*** 2012-07-08 03:00:11.351
*** SERVICE NAME:(SYS$BACKGROUND) 2012-07-08 03:00:11.338
*** SESSION ID:(1105.1) 2012-07-08 03:00:11.338
wsd 0x1f8169a6c8, sbuf (nil), setid 9, op 0
lcuridx 0, lasz (nil)
freeing in-flux r/w latch for process state: 1fc165d248
... in-flux r/w latch 1fc1fcc9b0 Child cache buffers chains level=1 child#=4753
Location from where latch is held: kcbgtcr: kslbegin excl:
Context saved from call: 113266196
state=busy(exclusive) (val=0x2000000000000071) holder orapid = 113
waiters [orapid (seconds since: put on list, posted, alive check)]:
139 (2, 1341687611, 2)
192 (2, 1341687611, 2)
191 (2, 1341687611, 2)
173 (2, 1341687611, 2)
185 (2, 1341687611, 2)
176 (2, 1341687611, 2)
174 (2, 1341687611, 2)
118 (2, 1341687611, 2)
190 (2, 1341687611, 2)
179 (2, 1341687611, 2)
184 (1, 1341687611, 1)
189 (1, 1341687611, 1)
177 (1, 1341687611, 1)
195 (1, 1341687611, 1)
187 (1, 1341687611, 1)
194 (1, 1341687611, 1)
147 (1, 1341687611, 1)
183 (1, 1341687611, 1)
143 (1, 1341687611, 1)
144 (1, 1341687611, 1)
186 (1, 1341687611, 1)
188 (1, 1341687611, 1)
196 (1, 1341687611, 1)
145 (1, 1341687611, 1)
193 (1, 1341687611, 1)
waiter count=25
*** 2012-07-08 03:50:06.228
wsd 0x1f8169ac20, sbuf 0xac1ffafe8, setid 10, op 3
lcuridx 1, lasz 0x3c1ffc110
*** 2012-07-08 16:30:05.294
freeing in-flux r/w latch for process state: 20406507f0
... in-flux r/w latch 1f81265f28 Child cache buffers chains level=1 child#=14180
Location from where latch is held: kcbgtcr: kslbegin excl:
Context saved from call: 71341989
state=busy(exclusive) (val=0x2000000000000066) holder orapid = 102
waiters [orapid (seconds since: put on list, posted, alive check)]:
121 (2, 1341736205, 2)
116 (2, 1341736205, 2)
125 (2, 1341736205, 2)
140 (2, 1341736205, 2)
145 (2, 1341736205, 2)
waiter count=5
freeing in-flux r/w latch for process state: 1fc165f9d0
... in-flux r/w latch 1f813aec18 Child cache buffers chains level=1 child#=20914
Location from where latch is held: kcbrls: kslbegin:
Context saved from call: 96505705
state=busy(exclusive) (val=0x200000000000007b) holder orapid = 123
*** 2012-07-08 17:20:10.876
wsd 0x1f8169a6c8, sbuf (nil), setid 9, op 0
lcuridx 0, lasz (nil)
*** 2012-07-08 17:20:10.876
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [kcbshlc_1], [33], [], [], [], [], [], []
----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
ksedst()+31 call ksedst1() 000000000 ? 000000001 ?
7FBFFFCEB0 ? 7FBFFFCF10 ?
7FBFFFCE50 ? 000000000 ?
ksedmp()+610 call ksedst() 000000000 ? 000000001 ?
7FBFFFCEB0 ? 7FBFFFCF10 ?
7FBFFFCE50 ? 000000000 ?
ksfdmp()+21 call ksedmp() 000000003 ? 000000001 ?
7FBFFFCEB0 ? 7FBFFFCF10 ?
7FBFFFCE50 ? 000000000 ?
kgerinv()+161 call ksfdmp() 000000003 ? 000000001 ?
7FBFFFCEB0 ? 7FBFFFCF10 ?
7FBFFFCE50 ? 000000000 ?
kgeasnmierr()+163 call kgerinv() 0066876E0 ? 2A97200260 ?
7FBFFFCF10 ? 7FBFFFCE50 ?
000000000 ? 000000000 ?
kcbshlc()+239 call kgeasnmierr() 0066876E0 ? 2A97200260 ?
7FBFFFCF10 ? 7FBFFFCE50 ?
000000000 ? 000000021 ?
kslilcr()+770 call kcbshlc() 0066876E0 ? 1F801DDB28 ?
7FBFFFCF10 ? 7FBFFFCE50 ?
000000000 ? 000000021 ?
ksl_cleanup()+1567 call kslilcr() 7FBFFFCE50 ? 000000000 ?
7FBFFFDCE0 ? 1F801DDB28 ?
0066876E0 ? 000000021 ?
ksuxfl()+492 call ksl_cleanup() 000000000 ? 000000000 ?
000000000 ? 1F801DDB28 ?
0066876E0 ? 000000021 ?
ksuxda()+55 call ksuxfl() 1FC165B8E0 ? 000000000 ?
000000000 ? 1F801DDB28 ?
0066876E0 ? 000000021 ?
ksucln()+1390 call ksuxda() 1FC165B8E0 ? 000000000 ?
000000000 ? 1F801DDB28 ?
0066876E0 ? 000000021 ?
ksbrdp()+794 call ksucln() 060008100 ? 000000000 ?
FFFFFFFF9720ED9F ?
1F801DDB28 ? 0066876E0 ?
000000021 ?
opirip()+616 call ksbrdp() 060008100 ? 000000000 ?
000000001 ? 060008100 ?
0066876E0 ? 000000021 ?
opidrv()+582 call opirip() 000000032 ? 000000004 ?
7FBFFFF698 ? 060008100 ?
0066876E0 ? 000000021 ?
sou2o()+114 call opidrv() 000000032 ? 000000004 ?
7FBFFFF698 ? 060008100 ?
0066876E0 ? 000000021 ?
opimai_real()+317 call sou2o() 7FBFFFF670 ? 000000032 ?
000000004 ? 7FBFFFF698 ?
0066876E0 ? 000000021 ?
main()+116 call opimai_real() 000000003 ? 7FBFFFF700 ?
000000004 ? 7FBFFFF698 ?
0066876E0 ? 000000021 ?
__libc_start_main() call main() 000000003 ? 7FBFFFF700 ?
+219 000000004 ? 7FBFFFF698 ?
0066876E0 ? 000000021 ?
_start()+42 call __libc_start_main() 000713984 ? 000000001 ?
7FBFFFF848 ? 005288D00 ?
000000000 ? 000000003 ?
通过这个trace可以看出数据库运行在LINUX 64操作系统,版本是10.2.0.4。
出现错误的原因:
PMON在清理1fc165d248的时候,因为被orapid = 102持有,导致清理失败.
PMON在清理20406507f0的时候,因为被orapid = 102持有,导致清理失败.
PMON在清理1fc165f9d0的时候,因为被orapid = 123持有,导致清理失败.
查询MOS[443909.1]
发现是unpublished Bug 4723109.处理方法打上Patch 4723109.
DBCA Fails With ORA-15243
今天接到朋友的电话说他们装ORACLE 11G R1 RAC的时候遇到ORA-12801/ORA-15243错误,请求我帮忙解决
具体情况
AIX系统以前装过11G R2 RAC,现因为项目要求11G R1,已经重装了系统,然后安装R1,在安装到DBCA配置ASM的时候,出现ORA-12801/ORA-15243错误
ORA-12801: error signaled in parallel query server PZ99, instance wmsdb1:+ASM1(1) ORA-15243: 11.2.0.0.0 is not a valid version number

通过SQLPLUS登录ASM1实例查询发现该有一个ORADATA磁盘组,包含了一个/dev/rhdisk1.通过询问,得出结论是这个磁盘组以前是安装R2的时候作为存储OCR和VOTINGDISK使用,重装系统的时候未对该磁盘进行处理.
处理思路[想办法清除磁盘中asm信息]
1.尝试通过sqlplus 删除该磁盘组,报该磁盘组处于dismount状态
2.尝试mount该磁盘组,提示版本无效(ORA-15243)[当前的asm程序是11.1而磁盘组信息是11.2 程序当然不一致了]
3.直接使用dd清理该asm disk header信息(dd if=/dev/zero of=/dev/rhdisk1 bs=4096 count=1)
4.重新运行dbca一切工作正常
MOS中相关文章[1460997.1]只适合linux asmlib情况
Applies to: Oracle Server - Enterprise Edition - Version 11.1.0.7 and later Information in this document applies to any platform. Symptoms On : 11.1.0.7 version, STORAGE When attempting to create database or query gv$asm_diskgroup, the following error occurs. ERROR ----------------------- ORA-12801: error signaled in parallel query server PZ99, instance dchilcmsdb2.hq.navteq.com:+ASM2 (2) ORA-15243: 11.2.0.0.0 is not a valid version number STEPS ----------------------- The issue can be reproduced at will with the following steps: 1. Previously had 11GR2 installed and configured. Removed this installation then installed 11.1.0.7 and created diskgroups using some of the same disks previously used. 2. Attempt to create database and receive the errors. Drop the newly created diskgroups and query the view still get same errors. BUSINESS IMPACT ----------------------- The issue has the following business impact: Due to this issue, users cannot create new database. Changes Removed 11.2.0.1 installation and installed 11.1.0.7 software without cleaning up all of the diskgroup information from previous installation. Cause All the current information shows that we are using correct binaries and that the diskgroups that are being used have correct comparability settings. HTML shows that the disks for the old diskgroup are still being discovered. This in conjunction with the text of the error as follows shows that we are picking up 11.2.0.0.0 as version from somewhere. ORA-15243: 11.2.0.0.0 is not a valid version number Problem was caused by the disks that had been used for the OCR/Voting disk diskgroup in 11GR2 installation still being present and accessible. Solution As the root user execute /etc/init.d/oracleasm/deletedisk command against all the disks that were previously used for the OCR/Voting disk diskgroup then try the operation again.
关闭数据库出现ORA-00379错误
关闭数据库出现ORA-00379错误
SQL> shutdown immediate ORA-00604: 递归 SQL 级别 1 出现错误 ORA-00379: 缓冲池 DEFAULT 中无法提供 8K 块大小的空闲缓冲区
查看内存分配
SQL> show parameter sga; NAME TYPE VALUE ------------------------------------ ----------- ----------- lock_sga boolean FALSE pre_page_sga boolean FALSE sga_max_size big integer 412M sga_target big integer 0 SQL> select * from v$sgainfo; NAME BYTES RES -------------------------------- ---------- --- Fixed SGA Size 1333676 No Redo Buffers 6078464 No Buffer Cache Size 104857600 Yes Shared Pool Size 142606336 Yes Large Pool Size 4194304 Yes Java Pool Size 12582912 Yes Streams Pool Size 0 Yes Shared IO Pool Size 0 Yes Granule Size 4194304 No Maximum SGA Size 431038464 No Startup overhead in Shared Pool 46137344 No Free SGA Memory Available 159383552 --spfile中分配情况 orcl.__db_cache_size=104857600 orcl.__java_pool_size=12582912 orcl.__large_pool_size=4194304 orcl.__pga_aggregate_target=104857600 orcl.__sga_target=281018368 orcl.__shared_io_pool_size=0 orcl.__shared_pool_size=142606336 orcl.__streams_pool_size=0 --初始化参数 *.sga_max_size=0 *.sga_target=536870912 *.memory_max_target=536870912 *.memory_target=536870912
alert日志
Mon Jul 02 11:30:19 2012 DIA0 started with pid=8, OS id=1520 Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_dia0_1520.trc (incident=10883): ORA-04030: out of process memory when trying to allocate 29916 bytes (heap_ksdhngreq,msg_body:ksdhng) Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_dia0_1520.trc (incident=10884): ORA-04030: out of process memory when trying to allocate 8204 bytes (diag pga,dbgtbDefaultBucket) ORA-04030: out of process memory when trying to allocate 29916 bytes (heap_ksdhngreq,msg_body:ksdhng) ORA-4030 : opidrv aborting process DIA0 ospid (1348_1520) Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_dia0_1520.trc (incident=12013): ORA-04030: out of process memory when trying to allocate 8204 bytes (diag pga,dbgtbDefaultBucket) ORA-04030: out of process memory when trying to allocate 8204 bytes (diag pga,dbgtbDefaultBucket) ORA-04030: out of process memory when trying to allocate 29916 bytes (heap_ksdhngreq,msg_body:ksdhng) Process debug not enabled via parameter _debug_enable Mon Jul 02 11:33:19 2012 Trace dumping is performing id=[cdmp_20120702113319] Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_smon_1820.trc: ORA-00379: no free buffers available in buffer pool DEFAULT for block size 8K ORA-00379: no free buffers available in buffer pool DEFAULT for block size 8K Mon Jul 02 11:33:49 2012 Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_smon_1820.trc: ORA-00379: no free buffers available in buffer pool DEFAULT for block size 8K Mon Jul 02 11:34:38 2012 Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_smon_1820.trc: ORA-00379: no free buffers available in buffer pool DEFAULT for block size 8K Mon Jul 02 11:37:05 2012 Errors in file e:\app\administrator\diag\rdbms\orcl\orcl\trace\orcl_ora_2400.trc: ORA-00379: 缓冲池 DEFAULT 中无法提供 8K 块大小的空闲缓冲区 ORA-00379: 缓冲池 DEFAULT 中无法提供 8K 块大小的空闲缓冲区 ORA-00379: 缓冲池 DEFAULT 中无法提供 8K 块大小的空闲缓冲区 Tue Jul 03 09:58:06 2012 WARNING: sga_target 432013312 cannot be more than memory_target (432013312) - pga_aggregate_target (104857600/0) or untunable pga 104857600, 73783296
通过这里可以看出,系统的data buffe和pga都有内存不足的报错.
解决问题
问题的原因是由于内存分配不多,导致sga组件被消耗完,现在数据库不能正常关闭,修改了相关的内存参数的配置[避免该bug采用asmm内存管理]也无法生效,现在需要做的任务是重启数据库.导致数据库不能被关闭的原因是因为data buffer中的脏数据不能写入新数据.查询MOS发现是Bug 7702085.正常关闭库解决办法手工刷sga组件,然后升级数据库到11.2.0.1 (Base Release)/11.1.0.7.3 (Patch Set Update)/11.1.0.7 Patch 25 on Windows Platforms
SQL> alter system flush BUFFER_CACHE; System altered. SQL> alter system flush SHARED_POOL; System altered. SQL> shutdown immediate Database closed. Database dismounted. ORACLE instance shut down.

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

