Oracle内部错误:ORA-00600[kfioTranslateIO03]一例

一套Linux x86-64上的11.2.0.2 RAC+ASM系统,其中一个节点出现了ORA-00600[kfioTranslateIO03]内部错误,其具体日志如下:

=============================alert.log=============================== adrci> show alert -tail -f 2011-05-30 20:29:12.657000 +08:00 Starting background process RSMN RSMN started with pid=31, OS id=22084 ORACLE_BASE not set in environment. It is recommended that ORACLE_BASE be set in the environment Reusing ORACLE_BASE from an earlier startup = /s01/orabase ALTER DATABASE MOUNT /* db agent *//* {0:7:3} */ This . . . → Read More: Oracle内部错误:ORA-00600[kfioTranslateIO03]一例

Why ASMLIB and why not?

ASMLIB是一种基于Linux module,专门为Oracle Automatic Storage Management特性设计的内核支持库(kernel support library)。

长久以来我们对ASMLIB的认识并不全面,这里我们来具体了解一下使用ASMLIB的优缺点。

理论上我们可以从ASMLIB API中得到的以下益处:

总是使用direct,async IO 解决了永久性设备名的问题,即便在重启后设备名已经改变的情况下 解决了文件权限、拥有者的问题 减少了I/O期间从用户模式到内核模式的上下文切换,从而可能降低cpu使用率 减少了文件句柄的使用量 ASMLIB API提供了传递如I/O优先级等元信息到存储设备的可能

虽然从理论上我们可以从ASMLIB中得到性能收益,但实践过程中这种优势是几乎可以忽略的,没有任何性能报告显示ASMLIB对比Linux上原生态的udev设备管理服务有任何性能上的优势。在Oracle官方论坛上有一篇<ASMLib and Linux block devices>讨论ASMLIB性能收益的帖子,你可以从中看到”asmlib wouldn’t necessarily give you much of an io performance benefit, it’s mainly for ease of management as it will find/discover the right devices for you, the io effect of asmlib is large . . . → Read More: Why ASMLIB and why not?

Discover Your Missed ASM Disks

经常有网友在构建10g/11g中ASM存储环境的时候遇到ASM磁盘无法识别的问题,虽然已经为存储设备赋予了适当的权限,也为ASM实例修改了asm_diskstring初始化参数,可是在DBCA的ASM Diskgroup创建页面里就是无法显示候选的ASM Disk磁盘。

实际上因为ASM存储方式比起裸设备或GPFS来说更为黑盒,我们也无法利用ASM instance中的一些动态性能视图或内部视图来排查造成这一问题的原因,使得这类问题显得十分棘手。

下面我来介绍一种使用操作系统调用追踪工具来排查ASM无法找到磁盘问题的方法。

[oracle@vrh1 raw]$ cd /dev/rdsk /* 演示中我们要用到的三个裸设备位于/dev/rdsk下 */ [oracle@vrh1 rdsk]$ ls hdisk1 hdisk2 hdisk3 [oracle@vrh1 rdsk]$ sqlplus / as sysdba SQL> select * from v$version; BANNER —————————————————————- Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 – Prod PL/SQL Release 10.2.0.4.0 – Production CORE 10.2.0.4.0 Production TNS for Linux: Version 10.2.0.4.0 – . . . → Read More: Discover Your Missed ASM Disks

Placeholder for AMDU binaries and using with ASM 10g

Applies to:

Oracle Server – Enterprise Edition – Version: 10.1.0.3 to 10.2.0.4 – Release: 10.1 to 10.2 Information in this document applies to any platform. Oracle Server Enterprise Edition – Version: 10.1.0.3 to 10.2.0.4

Purpose

On Oracle 10g the content of a diskgroup can be reviewed if the diskgroup is mounted and there are . . . → Read More: Placeholder for AMDU binaries and using with ASM 10g

Files for Upload When Creating ASM/Storage Service Requests

Purpose

Reduce the back and forth in service request of requesting needed diagnostic information to be able to properly analyze and resolve ASM/Storage service requests.  It is intended to identify the minimum files needed when opening service requests to allow the support engineer to start analysis upon assignment of the service request.

Scope

This is . . . → Read More: Files for Upload When Creating ASM/Storage Service Requests

Collecting Data To Diagnose ASM Disk Header Corruption

Applies to:

Oracle Server – Enterprise Edition – Version: 10.1.0.3 to 11.1.0.7 – Release: 10.1 to 11.1 Information in this document applies to any platform.

Purpose

When an ASM diskgroup is mounted, the correct value for column V$ASM_DISK.HEADER_STATUS is MEMBER.  There are situations where although diskgroup is mounted, the value for the column could be . . . → Read More: Collecting Data To Diagnose ASM Disk Header Corruption

几个关于oracle 11g ASM的问题

Question:

1.11g Oracle Clusterware需要的OCR和Voting disk可以存储在ASM或者集群文件系统或者NFS中。对于全新安装,裸设备不再被支持(是否有办法使用裸设备?)。

2.使用ASM时,若相关存储上的磁盘路径(disk path)名前后不一致,是否仍然可以使用?需要什么调整?

Answer:

1.在11gr2 Grid Infrastructure全新安装时是没有办法使用裸设备的(You cannot install OCR or voting disk files on raw partitions. You can install only on Oracle ASM, or on supported network-attached storage or cluster file systems. The only use for raw devices is as Oracle ASM disks.);但可以通过后续的手段将OCR和VOTING DISK移动到裸设备上,如:

替换OCR: ocrconfig -add rawdevice ocrconfig -replace . . . → Read More: 几个关于oracle 11g ASM的问题

Oracle Database 11g Automatic Storage Management

Storage Challenges for DBAs Layout: Complex, time consuming, error prone Isolation practice: Inefficient, and costly Provisioning: Frequent, often requires new layout Performance: Complex problem determination Custom deployment: Each deployment is different Inflexible: Each configuration is optimized for a specific load NO good solutions out there: Local file systems – too slow RAW – fast but . . . → Read More: Oracle Database 11g Automatic Storage Management