Troubleshooting One RAC node reboot with ora-600 [kjdrisRMnovalid:msgRMno]

今天一套 2节点的11.2.0.3 RAC 数据库计划在0点的维护窗口做一些参数优化,其中包括禁用DRM ,所以在下午提前修改了参数scope=spfile等晚上重启时生效,计划赶不上变化,就在大伙等待0点到来时,突然节点2主机重启,随后节点1跟随instance reboot(主机未重启),在Node1 DB alert.log 发现了ora-600 [kjdrisRMnovalid:msgRMno].

ASM DISKGROUP Migrate to Anotherr SAN (迁移ASM到新存储)

上周刚刚做了ASM Storage的一套13T 2 Nodes 11GR2 database RAC ON AIX 从老的SAN迁移到新的SAN , 迁移的磁盘组包含了DATAFILE 和所有Clusterware 的文件(OCR andvoting disk), ORACLE ASM 的Rebalance特性使这件事情变的非常的容易,随着ASM的逐渐成熟,如果你计划做对已使用了ASM disggroup 做存储的迁移,ASM 的Rebalance 可以做为一套解决方案而且可以做到0 Downtime, 下面简单的分享这个过程。 迁移步骤 1.备份整个数据库和GI文件,并验证备份文件有效性 GI. # ocrcheck # crsctl query css votedisk DB. spfile,controlfile,datafile,logfile,tempfile,archivelog.. select d.name group_name,f.type,count(*) cnt from v$asm_file f join v$asm_diskgroup d on f.group_number=d.group_number group by rollup (d.name,f.type); A 迁移GI … Read more

Troubleshoot ORA-27544,ORA-27300,ORA-27301,ORA-27302,”HPUX-ia64 Error: 23: File table overflow” issue

A product database is 10205 2nodes rac ,our OS is HP-UNIX 11.31,There was a time unable establish new connections, then I check alert log found ORA-27544,ORA-27300,ORA-27301,ORA-27302,”HPUX-ia64 Error: 23: File table overflow” error. The problem seems to be OS related. #alert log Sun Nov 30 15:47:16 EAT 2014 Global Enqueue Services Deadlock detected. More info in … Read more

Autotask(Optimizer statistics gathering) not working in 11.2.0.4(未自动收集统计信息)

有一些表数据发生了很大变化,但是统计信息从初次导入后从没有自动收集过统计信息,导致现在的有些执行计划不成确, 手动收集是可以成功的,如何开启自动收集? oracle 11.2.0.4 RAC ON AIX

Export terminates with ORA-00600 [ksuloget2]

. . exported “ANBOB”.”ANBOB_PROJECT_SCORE” 3.931 GB 46241981 rows
. . exported “ANBOB”.”T1″
EXP-00056 Oracle error 600 encountered
ORA-00600: internal error code, arguments: [ksuloget2], [0xFEBDD104], [0xFEBCEE54], [500], [0xFEBDD128], [], [], [], [], [], [], []
. . exported “ANBOB”.”T2″

The segment header block corrupted cause ORA-08103 issue (段头坏块导致ora-8103)

节前有个网友向我咨询他们的生产库遇到了ora-8103,错误的block 是 SEGMENT HEADER BLOCK, 不可以简单通过rowid 跳过, 也不能像修改data block corruption 那样通过bbed 修改块为 corrupted 然后通过 dbms_repair.skip_corrupt_blocks 跳过该块, 该segment header block上都没有extent 信息(如extent map\HWM)…