My Oracle Support Banner

ORA-00600 error while running FND_STATS.GATHER_SCHEMA_STATS (Doc ID 1452667.1)

Last updated on JANUARY 30, 2022

Applies to:

Oracle Database - Enterprise Edition - Version 11.1.0.7 to 11.2.0.2 [Release 11.1 to 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.

Symptoms

When running FND_STATS.GATHER_SCHEMA_STATS, the following errors are reported in the instance alert log, even though the procedure seems to terminate successfully:

ORA-00600: internal error code, arguments: [17147], [0x2ADDB497F168], [], [], [], [], [], [], [], [], [], []
ORA-00039: error during periodic action
ORA-00600: internal error code, arguments: [17114], [0x2ADDB497F168], [], [], [], [], [], [], [], [], [], []

The SQL statement being executed can look like:

select /*+ parallel(t,10) parallel_index(t,10) dbms_stats cursor_sharing_exact use_weak_name_resl dynamic_sampling(0) no_monitoring no_substrb_pad */count(*), count("SYS_NC00067$"), count(distinct "SYS_NC00067$"), sum(sys_op_opnsize("SYS_NC00067$")), substrb(dump(min("SYS_NC00067$"),16,0,32),1,120), substrb(dump(max("SYS_NC00067$"),16,0,32),1,120), ... from "<SCHEMA>"."<TABLE_NAME>" sample ( 1.0000000000) t

Important information to be found in the SQL statement are the use of parallellism and the reference to the involved table, e.g. GME.GME_RESOURCE_TXNS.

The incident trace file shows errors like:

...
2ADDB497F1E0 B497DD20 00002ADD                    [ ....*..]
  Chunk     2addb497dcd8 sz=     5264  NEXT CHUNK'S PREVIOUS POINTER NOT POINTING TO CURRENT CHUNK   54594c50505553
  freeable  "kxs-heap-w     "  ds=0x2addb44f1368
...

Review of the generated tracefiles reveals a call stack similar to:

... <- kghfrmrg <- kghfre <- kghfrh_internal <- kghfrh <- kxsFreeWorkArea <- kksumc <- opiexe <- kpoal8 <- ...

The plan table reported in the incident trace file shows an execution plan similar to:

-----------------------------------------------------------------------+-----------------------------------+-------------------------+
| Id  | Operation                                   | Name             | Rows  | Bytes | Cost  | Time      |  TQ  |IN-OUT|PQ Distrib |
-----------------------------------------------------------------------+-----------------------------------+-------------------------+
| 0   | SELECT STATEMENT                            |                  |       |       |  6657 |           |      |      |           |
| 1   |  SORT GROUP BY                              |                  |     1 |   161 |       |           |      |      |           |
| 2   |   PX COORDINATOR                            |                  |       |       |       |           |      |      |           |
| 3   |    PX SEND QC (RANDOM)                      | :TQ10001         |     1 |   161 |       |           |:Q1001| P->S |QC (RANDOM)|
| 4   |     SORT GROUP BY                           |                  |     1 |   161 |       |           |:Q1001| PCWP |           |
| 5   |      PX RECEIVE                             |                  |     1 |   161 |       |           |:Q1001| PCWP |           |
| 6   |       PX SEND HASH                          | :TQ10000         |     1 |   161 |       |           |:Q1000| P->P |HASH       |
| 7   |        SORT GROUP BY                        |                  |     1 |   161 |       |           |:Q1000| PCWP |           |
| 8   |         PX BLOCK ITERATOR                   |                  |   79K |   12M |  6657 |  00:01:20 |:Q1000| PCWC |           |
| 9   |          TABLE ACCESS SAMPLE BY ROWID RANGE | <TABLE_NAME>     |   79K |   12M |  6657 |  00:01:20 |:Q1000| PCWP |           |
-----------------------------------------------------------------------+-----------------------------------+-------------------------+

Changes

 

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.