Depending on the error number The more descriptive error message follows:
The same errors occur in various operations in the program R3trans.
If oncheck finds inconsistencies in an index, you are asked if you wish to repair this. Please note the name of the index
The execution of an SAP transaction terminates with the ABAP/4 runtime error DBIF_RSQL_SQL_ERROR. The evaluation of the syslog and the detailed information from the ABAP/4 runtime error show the following entries:
"SQL Error . "
"INF-240: Could not delete a row."
"INF-245: Could not position within a file via an index."
"INF-246: Could not do an indexed read to get the next row."
"INF-271: Could not insert new row into the table."
"ISAM-103: illegal key descriptor (too many parts or too long)."
An index of the table is inconsistent and corrupt. The cause for this is not yet known.
Solution
Check the indices on the table and, if necessary, recreate them using the SAPDBA tool. (Warning: deleting and re-creating an index can take a long time). To do this, proceed as follows:
1. Stop the R/3 System (as the user
$ stopsap r32. Determine index inconsistencies (as the user informix):
a) If a table
was given in the error message:
$ oncheck -cI
This checks all indices in the table .
b) If no table
is given in the error message:
$ oncheck -cI
This checks all indices in the entire database.
Warning: This may well take several hours, and is therefore not recommended. and reply with 'n'. Repairing an index using the SAPDBA tool is considerably faster than repairing it with oncheck.
3. Repair the index
4. Start the R/3 System (as the user
Note 38401.
$ startsap r3
Additional key words
DBIF_RSQL_SQL_ERROR, INF240, INF245, INF246, INF271, INF103, ISAM103
ILLEGAL KEY DESCRIPTOR
INDEX CORRUPTION INCONSISTENCY
PTS PTS_BUG PTS_BUG_xxxxx
SAP OSS Notes are online documents published by SAP which cover modifications, product errors, upgrades, FAQ's and customizing notes.
2.12.10
SAP Note 10851 - SQL Error "ISAM-103: illegal key descriptor"
Symptom
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment