Symptom:
The performance of certain SAP transactions is all of a sudden extremely slow or terminates with the ABAP/4 runtime error DBIF_RSQL_SQL_ERROR or DBIF_RTAB_SQL_ERROR. In the SYSLOG and in the detail information of the ABAP/4 runtime error you find the following entries:
"SQL error -243 occured when ... within a table
."
"INF-243: Could not position within a table."
"ISAM-101: file is not open."
Previously you may have found (it may have been some time prior to the occurance of this problem) in the database log file ("online.log file") messages of the type:
hh:mm:ss ...
hh:mm:ss Results: Index is now unusable
hh:mm:ss Action: Run 'oncheck -cI ...'
hh:mm:ss ...
Additional key words
INF243, INF101, ISAM101, INF271, INF131, ISAM131, INDEX, UNUSABLE
Cause and prerequisites
In your system a dbspace overflowed while an index modification was being cancelled (rollback of a different transaction). You may find in your SYSLOG previous entries of the type:
"SQL error occurs when...within table ."
"INF-: ..."
"ISAM-131: no free disk space."
Solution
Check the specified index with 'oncheck -cI ...' as described in the database log file ("online.log file") and, if necessary, recreate the index with the tool SAPDBA. (Caution: deleting and recreating an index may take some time). Proceed as follows:
1. Stop the R/3 System (as user adm):
$ stopsap r3
2. Repair the index with the tool SAPDBA. For this refer to the related Note 38401.
3. Start the R/3 System (as user adm):
$ startsap r3
No comments:
Post a Comment