碰到一个ora600的错误，操作记录如下：
[oracle@rh5 ~]$ export ORACLE_SID=PROD2 [oracle@rh5 ~]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.3.0 Production on Fri Mar 27 12:43:28 2015 Copyright (c) 1982, 2011, Oracle. All rights reserved. Connected. SYS@PROD2 > select status from v$instance 2 / select status from v$instance * ERROR at line 1: ORA-01012: not logged on Process ID: 0 Session ID: 0 Serial number: 0 SYS@PROD2 > conn / as sysdba Connected to an idle instance. SYS@PROD2 > startup ORA-01012: not logged on SYS@PROD2 > conn / as sysdba Connected to an idle instance. SYS@PROD2 > conn system/oracle ERROR: ORA-00600: internal error code, arguments: [ksfdnfy2], [ODM ERR: Calling stubbed version], [], [], [], [], [], [], [], [], [], [] Warning: You are no longer connected to ORACLE. @PROD2 > conn / as sysdba Connected to an idle instance. SYS@PROD2 > shu immediate ORA-24324: service handle not initialized ORA-24323: value not allowed ORA-00600: internal error code, arguments: [ksfdnfy2], [ODM ERR: Calling stubbed version], [], [], [], [], [], [], [], [], [], [] SYS@PROD2 > startup ORA-01031: insufficient privileges SYS@PROD2 > conn / as sysdba Connected to an idle instance. SYS@PROD2 > startup ORA-01012: not logged on SYS@PROD2 > conn / as sysdba Connected to an idle instance. SYS@PROD2 > shu immediate ORA-24324: service handle not initialized ORA-24323: value not allowed ORA-00600: internal error code, arguments: [ksfdnfy2], [ODM ERR: Calling stubbed version], [], [], [], [], [], [], [], [], [], [] SYS@PROD2 > shu abort ORA-01031: insufficient privileges SYS@PROD2 > conn / as sysdba Connected to an idle instance. SYS@PROD2 > shu abort ORACLE instance shut down. SYS@PROD2 > startup ORACLE instance started. Total System Global Area 941600768 bytes Fixed Size 1348860 bytes Variable Size 515902212 bytes Database Buffers 419430400 bytes Redo Buffers 4919296 bytes Database mounted. Database opened. SYS@PROD2 > select status from v$instance; STATUS ------------ OPEN SYS@PROD2 >
直接报600错误。abort重启startup后，数据库正常。在mos上找到原因
A) Before the Database Instance is started, you can verify if DNFS (Direct NFS) is enabled (“ON”) or disabled (“OFF”) as follows: 1) When DNFS is not linked with the Oracle kernel, the next command will report the “ODM ERR: Calling stubbed version” error example: [oracle@asmlnx1 lib]$ make -f ins_rdbms.mk dnfs_off rm -f /u01/app/oracle/product/11.2.0/dbhome_1/lib/libodm11.so; cp /u01/app/oracle/product/11.2.0/dbhome_1/rdbms/lib/libodm11.so.dummy /u01/app/oracle/product/11.2.0/dbhome_1/lib/libodm11.so [oracle@asmlnx1 lib]$ [oracle@asmlnx1 lib]$ strings /u01/app/oracle/product/11.2.0/dbhome_1/lib/libodm11.so | grep -i odm odm_deregisternic odm_registernic odm_destroy odm_deregistermem odm_registermem odm_mname odm_resize odm_cancel odm_ioerror odm_io odm_cleanup odm_unidentify odm_reidentify odm_identify odm_delete odm_abort odm_commit odm_create odm_error odm_fini odm_init odm_discover ODM ERR: Calling stubbed version Stubbed ODM Library, Version: 1.0 2) But if DNFS is linked with the Oracle kernel, then the “ODM ERR: Calling stubbed version” error will not be reported, example: [oracle@asmlnx1 lib]$ make -f ins_rdbms.mk dnfs_on rm -f /u01/app/oracle/product/11.2.0/dbhome_1/lib/libodm11.so; cp /u01/app/oracle/product/11.2.0/dbhome_1/lib/libnfsodm11.so /u01/app/oracle/product/11.2.0/dbhome_1/lib/libodm11.so [oracle@asmlnx1 lib]$ [oracle@asmlnx1 lib]$ [oracle@asmlnx1 lib]$ strings /u01/app/oracle/product/11.2.0/dbhome_1/lib/libodm11.so | grep -i odm kgodm_deregisternic kgodm_registernic kgodm_destroy kgodm_deregistermem kgodm_registermem kgodm_mname kgodm_resize kgodm_cancel kgodm_ioerror kgodm_io kgodm_cleanup kgodm_unidentify kgodm_reidentify kgodm_identify kgodm_readlink kgodm_readdir kgodm_fsinfo kgodm_fsstat kgodm_setattr kgodm_getattr kgodm_rmdir kgodm_mkdir kgodm_delete kgodm_abort kgodm_commit kgodm_create kgodm_error kgodm_fini kgodm_init kgodmfhtr_ kgodm_discover nfs odm heap kgodm event %u set to level %u B) After the Database Instance is started, you can verify if DNFS (Direct NFS) is enabled (“ON”) or disabled (“OFF”) as follows: Look at the database alert.log for the following outputs: . . . Oracle instance running with ODM: Oracle Direct NFS ODM Library Version 3.0 . . Direct NFS: channel id [0] path [celntap3-bc] to filer [celntap3-bc] via local [] is UP Direct NFS: channel id [1] path [celntap3-bc] to filer [celntap3-bc] via local [] is UP . . .