Last updated on JULY 05, 2017
Applies to:Oracle Database - Enterprise Edition - Version 10.1.0.2 to 126.96.36.199 [Release 10.1 to 11.1]
Information in this document applies to any platform.
Following a platform conversion, an insert into a table failed with an ORA-600 [ktecgeb-2] error.
In the error below which is captured in the alert log, the "incarnation" of the block (that is, the rdbms version of the block) is showing as "2," which is not a valid incarnation for a 10g database:
ORA-00600: internal error code, arguments: [ktecgeb-2], , , , , , , 
The call stack contained the following elements:
ksedst ksedmp ksfdmp kgerinv kgeasnmierr ktecgeb ktspgenhw ktspbhwm ktspmlhwm ktspfmtrng
ktspfsall ..... main
Traditional corruption checks (e.g. analyze . . . validate structure, dbv, rman backup validate check logical) did not detect the problem. The only way to detect the corruption in the database (other than running DML on the corrupted segment) was to run space advisor which would fail with the same ORA-600[ktecgeb-2] error.
The database was converted using Transportable Tablespaces and the RMAN convert functionality from a platform using big endian to a platform using little endian.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms