Skip to Main Content

Oracle Database Discussions

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

ora-00600 internal error codes every hour!

temmAug 25 2017 — edited Aug 25 2017

Hi,

We are having lately trouble with our 10g Database and we are getting ora-600 internal error messages every hour. Database seems to be working, but this is not a good sign.

Fri Aug 25 13:00:40 EEST 2017

Errors in file /opt/oracle/sen/admin/trace/bdump/sen_m000_8697.trc:

ORA-00600: internal error code, arguments: [ktsplbfmb-sync], [], [], [], [], [], [], []

Fri Aug 25 13:00:43 EEST 2017

Errors in file /opt/oracle/sen/admin/trace/bdump/sen_m000_8697.trc:

ORA-00600: internal error code, arguments: [ktsplbfmb-sync], [], [], [], [], [], [], []

Fri Aug 25 13:00:45 EEST 2017

Errors in file /opt/oracle/sen/admin/trace/bdump/sen_j000_8650.trc:

Fri Aug 25 13:00:45 EEST 2017

Errors in file /opt/oracle/sen/admin/trace/bdump/sen_m001_8701.trc:

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

The trace file (sen_m000_8697.trc) looks something like this

*** ACTION NAME:(Auto-Flush Slave Action) 2017-08-25 13:00:38.514

*** MODULE NAME:(MMON_SLAVE) 2017-08-25 13:00:38.514

*** SERVICE NAME:(SYS$BACKGROUND) 2017-08-25 13:00:38.514

*** SESSION ID:(266.792) 2017-08-25 13:00:38.514

Dumping current redo log in thread 1

DUMP OF REDO FROM FILE '/opt/oracle/sen/log/redo02.log'

and the sen_j000_8650.trc file

Unix process pid: 8650, image: oracle@oracleesxi (J000)

*** 2017-08-25 13:00:45.086

*** ACTION NAME:(start) 2017-08-25 13:00:45.086

*** MODULE NAME:(Oracle Enterprise Manager.purge system performan) 2017-08-25 1$

*** SERVICE NAME:(SYS$USERS) 2017-08-25 13:00:45.086

*** SESSION ID:(412.937) 2017-08-25 13:00:45.086

oer 8102.2 - obj# 41419, rdba: 0x00c03cb6(afn 3, blk# 15542)

Automatic Memory Management has been turned on (SGA_TARGET=8GB, SGA_MAX_SIZE=8GB) and STATISTICS_LEVEL parameter is set to TYPICAL

Could this be due to gathering statistics every hour? Even so, why would it produce these errors?

Should we try stopping the automatic memory management? Any other ideas?

Thank you

Oracle Database 10g Release 10.2.0.5.0 - 64bit Production

Red Hat Enterprise Linux Server release 5.11 (Tikanga)

Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Sep 22 2017
Added on Aug 25 2017
11 comments
1,184 views