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

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

Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan

Deal all, Below post content is not my own. It is taken from MOSC document but the example shown below is taken from our environment. I got to know the below topic when we had experienced the bad SQL query performance in one of our production environment during daily batch running time. Hence we had implemented the same mentioned in the title "Pinning execution plan for a sql_id using 'SQL Profile' to consistently reproduce a good plan". Introduction The "cost-based optimizer (CBO or just optimizer) is the part of database software that determines the most efficient means of accessing the specified data (or at least what it "calculates" as the most efficient). The optimizer determines which execution plan is most efficient by considering several sources of information, including query conditions, available access paths, statistics gathered for the system, and hints. Some changes in those conditions may affect the calculations of the plan...
9 comments
Read more

Metrics Process Limit Usage percentage (%) is critical or warning in OEM or Cloud Control 12c or Cloud Control 13c

Please run the below queries to trace details during Metric alert "Process Limit % is >= 75" in OEM or Cloud Control 12c or Cloud Control 13c To check the Metrics Process Limit Usage (%): ***************************************************** set lines 300 col INITIAL_ALLOCATION for a17 col LIMIT_VALUE for a12 select resource_name,current_utilization,max_utilization, INITIAL_ALLOCATION,LIMIT_VALUE,((current_utilization*100)/(INITIAL_ALLOCATION)) as "Process limit %" from v$resource_limit where resource_name in ('processes'); The below query will give you all connected sessions (ACTIVE and INACTIVE) to instance: ******************************************************************************************************* set pages 100 set lines 1000 col SPID heading 'PID' for a06 col SID for 99999 col SERIAL# heading 'serial' for 999999 col SQL_ID for a14 col USERNAME for a10 col PROGRAM for a20 col MODULE for a18 col OSU...
Post a Comment
Read more