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

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

Today,in  my test machine,I found this error.

Oracle version: 9204 single node

Os version:linux 2.6.23-2smp64G

The detail contents of alert.log like that:

Beginning log switch checkpoint up to RBA [0x357c.2.10], SCN: 0x0aaa.f1da19bf

Thread 1 advanced to log sequence 13692

  Current log# 3 seq# 13692 mem# 0: /zxindata/oracle/redolog/redo03.dbf

Wed Jan  5 14:49:27 2011

Completed checkpoint up to RBA [0x357c.2.10], SCN: 0x0aaa.f1da19bf

Wed Jan  5 15:10:35 2011

Errors in file /home/oracle/zxindbf/admin/zxin/udump/zxin_ora_32362.trc:

ORA-00600: internal error code, arguments: [504], [0x92465800], [32], [1], [session idle bit], [6], [0], [0x0]

Wed Jan  5 15:11:09 2011

Errors in file /home/oracle/zxindbf/admin/zxin/udump/zxin_ora_32421.trc:

ORA-00600: internal error code, arguments: [504], [0x5000646C], [32], [5], [enqueues], [0], [0], [0x5000646C]

As the test machine is very idle,the main content of the alert.log is “switch redo log”.And when ora 600 happen, the oracle instance hands.when I connect the oracle with “conn / as sysdba” command,It also hands. So,I kill the pid of smon

[oracle@localhost ~]$ sqlplus /nolog

SQL*Plus: Release 9.2.0.4.0 - Production on 星期三 1月 5 15:21:06 2011

Copyright (c) 1982, 2002, Oracle Corporation.  All rights reserved.

SQL> conn / as sysdba   ----It hands

From metalink ID 28104.1,we saw that the session is waiting for the latch ,but the latch had hold by another session.

Often,ora 600 504 is a bug,but in my test machine,I have not found the appropriate bug message for it.so,I just kill the oracle process and restart the oracle instance.

Here ,I lay the trace file.

 

来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/14730395/viewspace-683306/，如需转载，请注明出处，否则将追究法律责任。

转载于:http://blog.itpub.net/14730395/viewspace-683306/