Skip to main content

Analysis of ORA-00600: internal error code, arguments: [kxfxsStatus: nojoin but already sent joinOK]

Hi all,

In the alert log we found the below ORA-600 internal error. 

Alert log Error is below:

ORA-00600: internal error code, arguments: [kxfxsStatus: nojoin but already sent joinOK], [197888], [], [], [], [], [], [], [], [], [], []

We had to report this error with our analysis to our manager. We had searched the related document for this error in Oracle support website and found the following document.

Bug 9785632 - Parallel query fails with OERI[kxfxsstatus: nojoin but already sent joinok] (Doc ID 9785632.8)

As per above Doc ID 9785632.8,

Affects::
Versions confirmed as being affected
·         11.2.0.1
·         11.1.0.7

Fixed:
This issue is fixed in        
·         12.1.0.1 (Base Release)
·         11.2.0.2 (Server Patch Set)
·         11.2.0.1 Bundle Patch 8 for Exadata Database

Symptoms:
·         Internal Error May Occur (ORA-600)
·         ORA-600 [kxfxsStatus: nojoin but already sent joinOK]

Description:
ORA-600:[kxfxsStatus: nojoin but already sent joinOK]. can occur attempting to use parallel query.

We sent these details with the error to our manager to inform customer. But We got a reply mail from our manager stating that "But I don't see the parallel hint used. Are you sure, can you verify?"

Now i'm in a situation to relate the description mentioned in the document to our issue. Hence i had decided to take explain plan of the SQL statement in which we could see whether the query is running in parallel or not. 

I used below query to get explain plan of the SQL statement which caused this ORA-600 internal error.

select * from TABLE(DBMS_XPLAN.DISPLAY_AWR('&sql_id',null,null,'ALL'));


From the output, i was able to see some parallel query keywords like PX COORDINATOR,PX SEND QC (RANDOM),PX BLOCK ITERATOR,PX RECEIVE,PX SEND HASH,PX SEND BROADCAST in it. 
Then I sent the explain plan to my manager to confirm that SQL statement is trying to run in parallel only. 

This is how i made it on that day. Hope you'll also find it is helpful.

Comments

Post a Comment

Popular posts from this blog

SQL queries which is using more CPU resources

Here we'll see how to find heavy or more cpu consumed sql query in oracle We are facing high CPU load on Linux servers daily at times. Whenever CPU load is high, we'll get the TOP output and if the load is due to oracle database, we'll track currently running sql queries which is using more CPU on database & update the customer when they ask RCA report of high CPU load on servers. The below query is to find the sql queries which is causing CPU load on server & using more CPU resources currently. sessions based on cpu usage : ----------------------------------------- set pages 1000 set lines 1000 col OSPID for a06 col SID for 99999 col SERIAL# for 999999 col SQL_ID for a14 col USERNAME for a15 col PROGRAM for a23 col MODULE for a18 col OSUSER for a10 col MACHINE for a25 select * from ( select p.spid "ospid", (se.SID),ss.serial#,ss.SQL_ID,ss.username,substr(ss.program,1,22) "program",ss.module,ss.osuser,ss.MACHINE,ss.status, ...
2 comments
Read more

Cloud Control EM13c - Loader Throughput (rows per second) for Loader_D crossed the critical threshold and Total Loader Runtime in the Last Hour (seconds) for Loader_D crossed the critical threshold

Hello Guys, Here is an another post related to Cloud Control EM13c - Real-time Scenario. Suddenly We were receiving the following warning and critical alerts from EM13c Cloud Control during the time slot between 12 AM and 04:00 AM daily. 1)  Message= Loader Throughput (rows per second) for Loader_D crossed the critical threshold (xx). Current value: xx.xx 2)  Message= Total Loader Runtime in the Last Hour (seconds) for Loader_D crossed the critical threshold (x,xxx). Current value: xxxx.xx 3)  ORA-error stack (3,136) and ORA-error stack (609) were also logged in alert log 4)  Message= Incident (BEA-310003 [LowMemory]) detected in $OMS_HOME/gc_inst/user_projects/domains/GCDomain/servers/EMGC_OMS1/adr/diag/ofm/GCDomain/EMGC_OMS1/alert/log.xml at time/line number: When we analyzed the AWR reports of EM PDB repository database, we found there were few PL/SQL statements given below causing this issue with wait event  SQL*Net Break/reset To Client...
Post a Comment
Read more

Export and import multiple schema using expdp/impdp (Data Pump utility)

Use the below sql query to export and import multiple schema: expdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp exclude=statistics logfile=expdpschemas120514.log impdp schemas=schema1,schema2,schema3 directory=DATA_PUMP_DIR dumpfile=schemas120514bkp.dmp logfile=impdpschemas120514.log sql query to export and import a schema: expdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp exclude=statistics logfile=expdpschema120514.log impdp schemas=schema directory=DATA_PUMP_DIR dumpfile=schema120514bkp.dmp logfile=expdpschema120514.log Parameter STATISTICS=NONE can either be used in export or import. No need to use the parameter in both. To export meta data only to get ddl of the schemas: expdp schemas=schema1,schema2,schema3 directory=TEST_DIR dumpfile=content.dat content=METADATA_ONLY exclude=statistics To get the DDL in a text file: impdp directory=TEST_DIR sqlfile=sql.dat logfile=sql.log dumpfil...
3 comments
Read more