Wednesday, September 23, 2009

Learn ORA-00600: internal error code, arguments: [17059]

My Database traced many files with ORA-00600
Errors in file $ORACLE_BASE/admin/db/udump/db1_ora_13255.trc:
ORA-00600: internal error code, arguments: [17059], [0x0D36AD8A8], [], [], [], [], [], []
Checked trace file, I found many sql statements and etc...
KGL recovered in-flux handle for lock 0xd4ee3178
SO: 0xd4ee3178, type: 53, owner: 0xdf985d88, flag: INIT/-/-/0x00
LIBRARY OBJECT LOCK: lock=d4ee3178 handle=0
call pin=(nil) session pin=(nil) hpc=0000 hlc=0000
htl=0xd4ee31f8[0xd4ee31f8,0xd4ee31f8] htb=(nil) ssga=0xaf9cf7e0
user=0 session=0 count=0 flags=[0000] savepoint=0x0
That's a bad thing with oracle bugs, when checked on metalink (138554.1). but still no idea to solve( linux x86_64 RAC).

One thing i can do it now... flush buffer_cache and shared_pool.

I know this's not good idea to do... but it helped(... but may error again, again, ...).
However I still check Memory misconfiguration and SQL statements. Anyway this case made me need Oracle Support as well ;)


Anonymous said...

we also we faced the similar issue
ORA-00600: internal error code, arguments: [17059], [0x248AC0338], [], [], [], [], [], []

The setup detail
OS- RHEL 4 (64 Bit)
Database- Oracle RAC

Please note- Its a extremely critical issue in Oracle database and due to this one of the Datafile went in recover mode and my in-house application started abnormal behavior.

when checked the Oracle metalink then observed its related with max cursor etc. But I believe was the issue related with SGA memory and data flush, hence we restarted the database.
Now system is running last three days and not yet observe any issue and no error reported in Oracle Alert log files.


Surachart said...

Thank You
I reviewed cursors and ... but not be issue. I think my problem depended on library cache. However, A flush could help. but I have changed logic for program...

and everything ok!!!