Solution : https://service.sap.com/sap/support/notes/15184 (SAP Service marketplace login required)
Summary :
Logging issues occur with DBTABPRT, leading to runtime errors and system crashes in SAP releases 2.1D-2.1H and 2.2A-2.2B. Primary issues include incorrect logging configurations (rec/client), signal11 termination during delete/update operations, invalid requests (DBIF_RSQL_INVALID_REQUEST), and table inconsistencies (DBIF_RSQL_DDIC_INCONSISTENT). Causes range from SAP kernel errors to misconfigured parameters. Solutions involve deactivating table logging, correcting profile parameter syntax, extending log table DBTABPRT fields, and ensuring correct client-specific settings. Execution of specific ABAP reports like TESTUTAB is also advised to diagnose flag inconsistencies in the DDNTT table. Logging issues are ameliorated in later releases like 2.1I/2.2C onwards.
Key words :
default directory /usr/sap/<sid>/sys/profile, tools ---> case ---> maintenance ---> compare utility ---> tab, deactivating table logging forthe client copy operation, reset n1 additional key words, longer permits data type varc, abap/4 runtime error dbif_rsql_internal_error occurs, key fields exceeds 86 bytes, -key section exceeds 500 directly, abap/4 run-time error, set profile parameter rec/client =
Related Notes :
| 424426 | Table DBTABPRT during the upgrade 3* -> 4* |
| 1916 | Logging table changes in R/3 |