ORA-00600: internal error code, arguments: [kfnsInstanceReg00]

APPLIES TO:

Oracle Database - Enterprise Edition - Version 11.2.0.3 and later
Information in this document applies to any platform.

SYMPTOMS

After startup database instance crashes with ORA-00600 [kfnsInstanceReg00], [AWRPRD1A:AWRPRD1A]

 

Tue Mar 12 14:23:09 2013
Instance terminated by CKPT, pid = 17571
USER (ospid: 21540): terminating the instance
Instance terminated by USER, pid = 21540
Tue Mar 12 14:23:12 2013
Starting ORACLE instance (normal)

Tue Mar 12 14:28:22 2013
Errors in file /app/oracle/diag/rdbms/awrprd1a/AWRPRD1A/trace/AWRPRD1A_asmb_21646.trc:
ORA-15064: communication failure with ASM instance
ORA-00600: internal error code, arguments: [ORA_NPI_ERROR], [600], [ORA-00600: internal error code, arguments: [kfnsInstanceReg00], [AWRPRD1A:AWRPRD1A], [30000], [], [], [], [], [], [], [], [], []
], [], [], [], [], [], [], [], [], []

 

ASM alert log reports the following error.

 

Errors in file /app/grid/diag/asm/+asm/+ASM/trace/+ASM_ora_20078.trc  (incident=8274):
ORA-00600: internal error code, arguments: [kfnsInstanceReg00], [AWRPRD1A:AWRPRD1A], [30000], [], [], [], [], [], [], [], [], []
Incident details in: /app/grid/diag/asm/+asm/+ASM/incident/incdir_8274/+ASM_ora_20078_i8274.trc
Use ADRCI or Support Workbench to package the incident.
See Note 411.1 at My Oracle Support for error and packaging details.

 

CHANGES

If you do the immediate startup, after the normal shutdown or improper shutdown (abort) , you can see this error.

CAUSE

Unless the DB instance goes down cleanly or otherwise, the UFG process that's started to service this instance will remain on the ASM side and it won't allow another db client startup, it waits for the instance to be fenced.

SOLUTION

We can avoid this error by waiting couple of minutes before next startup.

REFERENCES

The above document has copied from Oracle Support (http://support.oracle.com), Doc ID 1552422.1

Comments