Index Unusable After Delete And Insert Through Third Party Application
(Doc ID 1239524.1)
Last updated on NOVEMBER 03, 2019
Applies to:Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Cloud Service - Version N/A and later
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database - Enterprise Edition - Version 10.2.0.4 and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
After certain SAP job removes rows from partition table, indexes become UNUSABLE, and subsequent insert (typically bulk load insert) ends with
ORA-00600: internal error code, arguments: [kdtdelrow-2], , , , , , , 
ORA-01502: index '<SAP_INDEX>' or partition of such index is in unusable state
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