RE: ORA-600

Speaking from several “bad” experiences, one of which lasted 72 hours and came perilously close to significant loss of revenue data:

Ignore ORA-6xx errors AT YOUR PERIL!

If you have an SR open with Oracle, I would be escalating to a Duty Manager, demanding “follow-the-sun” support and treating it that way internally; at least until you understand it sufficiently to be assured and assure your management, again, at your peril, that “it’s no big deal”.

A quick Google search on ktspgfb-1 turned up two articles in Oracle Support – I assume you’ve looked at those and they do not apply.

Clay Jackson
Database Solutions Sales Engineer
[cid:image001.jpg_at_01DA2C1E.665776A0]<https://www.quest.com/solutions/database-performance-monitoring/> clay.jackson_at_quest.com<mailto:clay.jackson_at_quest.com> office 949-754-1203 mobile 425-802-9603

From: oracle-l-bounce_at_freelists.org <oracle-l-bounce_at_freelists.org> On Behalf Of Amit Saroha Sent: Monday, December 11, 2023 10:18 AM To: ORACLE-L (oracle-l_at_freelists.org) <oracle-l_at_freelists.org> Subject: ORA-600

CAUTION: This email originated from outside of the organization. Do not follow guidance, click links, or open attachments unless you recognize the sender and know the content is safe.

Hi All,

We are experiencing ORA-600 is routinely raised, which is negatively affecting our operations. We've been working with Oracle, but there hasn't been much progress, so I thought I'd ask the specialists here if they might assist.

The problem is always raised on one table in our EBS system, OR_ORDER_LINES_ALL, and this table is heavily used 24 * 7 with a lot of INSERT + UPDATES.

Our database contains 19c. I looked through the alert log and the trace file but couldn't make much sense of it, for example, using the below queries I figured out when the issue occurred and in the enclosed trace file with 3M rows I can see the below rows meaningful as they show an update statement but I don't see anything wrong with the statement and why would it cause ORA-600.

Please offer any insights you have if possible.

SELECT ORIGINATING_TIMESTAMP, DETAILED_LOCATION, MESSAGE_LEVEL, MESSAGE_TEXT, PROBLEM_KEY   FROM V$DIAG_ALERT_EXT
 WHERE MESSAGE_LEVEL = 1
   AND MESSAGE_TEXT LIKE '%ORA-00600%'
 ORDER BY ORIGINATING_TIMESTAMP DESC; SELECT * FROM V$DIAG_TRACE_FILE_CONTENTS WHERE trace_filename = 'cebsprd_ora_165301_i848794.trc' ORDER BY TIMESTAMP;

Best Regards,
AMIT

--
http://www.freelists.org/webpage/oracle-l






(image/jpeg attachment: image001.jpg)