ORA-600 [opiexe0]

In this Document

APPLIES TO:

SYMPTOMS

After defragmentation using ALTER TABLE SHRINK SPACE or ALTER INDEX SHRINK SPACE, the following errors occur in the alert log in a RAC (real application cluster) environment:

ORA-00600: internal error code, arguments: [ktecgetsh-inc], [1], [], [], [], [], [], [], [], [], [], []
ORA-00600: internal error code, arguments: [opiexe0], [10632], [], [], [], [], [], [], [], [], [], []

The Current SQL Statement in the associated incident trace file shows DML (INSERT).

The table involved in the failing INSERT operation is a partitioned table.

The Call Stack Trace in the same incident trace file shows:

ktecgetsh <- ktecgshx <- ktspisc <- ktspgsp_main2 <- kdtgsp <- kdtgsph <- kdtgrs
<- kdtInsRow <- qerltcNoKdtBufferedInsRowCBK <- qerltcSingleRowLoad <- qerltcFetch

CHANGES

Issue is visible only for one day after defragmentation using ALTER TABLE SHRINK SPACE or ALTER INDEX SHRINK SPACE.

CAUSE

This issue is caused by a product defect.

It was investigated in:

     Bug 22855193 - ORA-600 [KTECGETSH-INC] WHEN INSERTING INTO A TABLE

SOLUTION

1.  Upgrade to a release which includes this fix.

          Reference:

               Bug 22855193 - ORA-600 [ktecgetsh-inc] Error During DML after Shrinking Table or Index (Note 22855193.8)

-OR-

2.  Apply Patch 22855193 if available for your version and platform.

     To check for conflicting patches, please use the My Oracle Support (MOS) Patch Planner Tool.

          Reference:
               How to Use MOS Patch Planner to Check and Request the Conflict Patches? (Note 1317012.1)

     If no patch exists for your platform and version, please contact Oracle Support to request a fix.

-OR-

3.  Workarounds:

     a.  Connect as SYSDBA and check the current value of the hidden parameter "_ptn_cache_threshold":

set pagesize 60 lines 1000 trimspool ON
col name format a40
col TYPE format a15
col description format a60
col value format a10
SELECT a.ksppinm name, b.ksppstvl value, b.ksppstdf defalt, DECODE (a.ksppity, 1, 'boolean',2, 'string', 3, 'number', 4, 'file', a.ksppity) TYPE, a.ksppdesc description
FROM sys.x$ksppi a, sys.x$ksppcv b
WHERE a.indx = b.indx
AND a.ksppinm LIKE '%ptnÊche%threshold%'
ORDER BY name;

         If if "_ptn_cache_threshold" > 0, then flush the shared pool.

     -or-

     b.  Try the DMLs again after the defragmentation has completed.
 

REFERENCES

Bug 22855193  ORA-600 [ktecgetsh-inc] Error During DML after Shrinking Table or Index

Affects:

Product (Component)	Oracle Server (Rdbms)
Range of versions believed to be affected	Versions BELOW 12.2
Versions confirmed as being affected	12.1.0.2 (Server Patch Set) 11.2.0.4
Platforms affected	Generic (all / most platforms affected)

Fixed:

The fix for 22855193 is first included in

12.2.0.1 (Base Release) 12.1.0.2.171017 (Oct 2017) Database Patch Set Update (DB PSU) 12.1.0.2.171017 (Oct 2017) Database Proactive Bundle Patch 12.1.0.2.171017 (Oct 2017) Bundle Patch for Windows Platforms

Interim patches may be available for earlier versions - click here to check.

Description

There are certain scenarios where ORA-600 [ktecgetsh-inc] may manifest during DML that is
run after ALTER TABLE SHRINK SPACE or ALTER INDEX SHRINK SPACE.
  
Rediscovery Notes
an ORA-600 [ktecgetsh-inc] after shrinking a table or index, and these two possible cases:
 
1) If the segment is a partitioned object and it is a RAC system and _ptn_cache_threshold > 0 
    FLUSH SHARED_POOL may resolve the problem.
 
2) Otherwise, it is possible to hit this bug in a very small window around the
SHRINK SPACE. Falling into this case and retrying the DML a few
seconds after SHRINK SPACE is complete the ORA-600 may not reproduce.
 
复制

References

Bug:22855193 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

Bug 7313847  OERI[ktecgetsh-inc] after shrink and split of partitioned table

Affects:

Product (Component)	Oracle Server (Rdbms)
Range of versions believed to be affected	Versions BELOW 12.1
Versions confirmed as being affected	11.2.0.1 11.1.0.7 10.2.0.5 10.2.0.4
Platforms affected	Generic (all / most platforms affected)

Fixed:

The fix for 7313847 is first included in

12.1.0.1 (Base Release) 11.2.0.2 (Server Patch Set)

Interim patches may be available for earlier versions - click here to check.

Description

NOTE: In the images and/or the document content below, the user information 
and environment data used represents fictitious data from the Oracle sample or 
bulit-in schema(s), Public Documentation delivered with an Oracle database product 
or other training material.  Any similarity to actual environments, actual persons, living 
or dead, is purely coincidental and not intended in any manner.
 
A memory corruption can be left after a shrink and split of a partitioned table.
This corruption may raise ORA-600 [ktecgetsh-inc] or ora-10632.
 
eg:
 create table t1(c1 number, c2 number) 
  partition by range(c1) (
	partition p1 values less than(10), 
	partition p2 values less than(20)) enable row movement;
 insert into t1 values(1,1);
 commit;
 alter table t1 shrink space cascade;
 alter table t1 split partition p1 at(5) into (
	partition p1_1, partition p1_2);
 insert into t1 values(4,4);
 
 ^
 ORA-600 [ktecgetsh-inc]
 
Workaround
 Shutdown and restart the instance after the SPLIT operation
  (this will ensure that the in-memory data is reloaded from 
   the dictionary)
 
复制

References

Bug:7313847 (This link will only work for PUBLISHED bugs)
Note:245840.1 Information on the sections in this article

Note: For additional ORA-600 related information please read Note:146580.1

PURPOSE:
  This article represents a partially published OERI note.

  It has been published because the ORA-600 error has been 
  reported in at least one confirmed bug.

  Therefore, the SUGGESTIONS section of this article may help
  in terms of identifying the cause of the error.

  This specific ORA-600 error may be considered for full publication
  at a later date. If/when fully published, additional information 
  will be available here on the nature of this error.


ERROR:
复制

SUGGESTIONS:

  If the Known Issues section below does not help in terms of identifying
  a solution, please submit the trace files and alert.log to Oracle 
  Support Services for further analysis.

  Known Issues:


Related Articles
@ Note:872316.1     ORA-00600 [Opiexe0][10632] on Accessing a Object


复制