Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Mailing Lists -> Oracle-L -> Self-correcting Oracle Error
A developer called to report the Ora-600 error
Errors in file /opt/oracle/admin/NLCO/udump/nlco_ora_16455.trc: ORA-00600: internal error code, arguments: [kcbgtcr_4], [266008], [1024], [1], [], [], [], []
When issuing select count(*) against a partition table. He then tried renaming the table which also produced the same error.
The alert_log shows
Wed Feb 19 09:34:23 2003
Errors in file /opt/oracle/admin/NLCO/udump/nlco_ora_18469.trc:
ORA-00600: internal error code, arguments: [ktehwugen1], [246907], [266008], [], [], [], [], []
Wed Feb 19 09:35:01 2003
Errors in file /opt/oracle/admin/NLCO/udump/nlco_ora_18469.trc:
ORA-00600: internal error code, arguments: [klapush_10], [201], [], [], [], [], [], []
Wed Feb 19 09:35:06 2003
Errors in file /opt/oracle/admin/NLCO/udump/nlco_ora_18469.trc:
ORA-00600: internal error code, arguments: [26084], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [klapush_10], [201], [], [], [], [], [], []
Wed Feb 19 09:35:54 2003
Errors in file /opt/oracle/admin/NLCO/udump/nlco_ora_16274.trc:
ORA-00600: internal error code, arguments: [kcbgtcr_4], [266008], [1024], [1], [], [], [], []
Wed Feb 19 09:40:39 2003
Errors in file /opt/oracle/admin/NLCO/udump/nlco_ora_16455.trc:
ORA-00600: internal error code, arguments: [kcbgtcr_4], [266008], [1024], [1], [], [], [], []
Wed Feb 19 09:45:36 2003
Errors in file /opt/oracle/admin/NLCO/udump/nlco_ora_16580.trc:
ORA-00600: internal error code, arguments: [kcbgtcr_4], [266008], [1024], [1], [], [], [], []
The kcbgtr_4 error keeps repeating
It seemed that any attempt to access the table or a partition of the table produced the kcbgtr_4 error. DBV was run and the files reported no corruption. I did this for both the table's table space and the system tablespace. The table's structure was verified. I saw something on metalink where a kcbgtcr_4 error had to do with bitmap tablespaces and trying to read dba_segments while a segment was being dropped. Although a completely different problem I decided to run dbms_space_admin to first verify the tablespace and then the segment. After running it against the tablespace, I tried Another "select count(*) from the table." It returned the proper answer. The error went away without my taking any corrective measures.
On the other errors the klapush_10 is probably relating to having more than one process doing direct path inserts. Oracle was supposed to have fixed this problem but it rears its head intermittently and unfortunately fairly often. I have no idea what a ktehwugen1 error is.
Has anyone else seen anything similar?
Ian MacGregor
--
Please see the official ORACLE-L FAQ: http://www.orafaq.net
--
Author: MacGregor, Ian A.
INET: ian_at_SLAC.Stanford.EDU
Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services ---------------------------------------------------------------------To REMOVE yourself from this mailing list, send an E-Mail message to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). Received on Wed Feb 19 2003 - 17:06:30 CST
![]() |
![]() |