After creation and transport of two secondary table indexes into productive system, these indexes become invalid after some time and it is necessary to create them again in SE14.
Both indexes were created in SE11 and both consist of two fields.
Table definition:
MANDT type CLNT lenght 3 - key field
VBTYP type CHAR lenght 1 - key field
VBELN type CHAR lenght 10 - key field
TEMPB type CHAR lenght 2 - key field
TCOUNT type INT2 lenght 5 - key field
SHPZG type CHAR lenght 1
SCNAM type CHAR lenght 12
SCDAT type DATS lenght 8
SCZET type TIMS lenght 6
RECZG type CHAR lenght 1
RCNAM type CHAR lenght 12
RCDAT type DATS lenght 8
RCZET type TIMS lenght 6
LFDTA type DATS lenght 8
LFTMA type TIMS lenght 6
LFDTD type DATS lenght 8
LFTMD type TIMS lenght 6
KNDTA type DATS lenght 8
KNTMA type TIMS lenght 6
KNDTD type DATS lenght 8
KNTMD type TIMS lenght 6
PARNRDSP type CHAR lenght 12
Index definitions:
Y01 - non-unique index, index on all database systems, index fields: MANDT, VBELN, SHPZG
Y02 - non-unique index, index on all database systems, index fields: MANDT, VBELN, RECZG
In data dictionary it seems that both indexes are created, they can be seem from SE11 and SE14 (with status active).
However in DB the indexes don't exist, because in SE14 below the status field it says "Does not exist in the database" and the button "Create table index" is active.
If I'd try to create the index (what I did 2 times already), the protocol won't show any errors, index will be created, but after some time (2-3 weeks) the table index probably becomes invalid and the same problem will occur again.
What might be the problem?
R/3 Release 4.6C
DB ORACLE 9.2.0.6.0