Symptom
- Runtime Errors DBIF_RSQL_INVALID_REQUEST are happening in transaction ST22 when trying to create a sales order in VA01
Category Error in database interface
Runtime Errors DBIF_RSQL_INVALID_REQUEST
Date and Time 01-27-2025 09:30:32
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|Short Text |
| Invalid call of the database interface. |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|What happened? |
| |
| |
| The current ABAP program terminated due to an internal error in the |
| internal SAP database interface. |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|What can I do? |
| Note which actions and entries caused the error to occur. |
| |
| Consult your SAP administrator. |
| |
| Using transaction ST22 for ABAP dump analysis, you can view, manage, |
| and retain termination messages for longer periods. |
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
|Error analysis |
| An invalid request was made to the SAP-internal database interface when |
| accessing table "BSEG". |
| The situation indicates an internal error in the SAP software or an |
| erroneous state of the affected work process. |
| For a more detailed analysis, examine the SAP system log (transaction |
| SM21). - The work process reports the following:
B dbmyclu : c3_write_page_on_db (1.14829): unexpected return code 128 from db_xrtab at insert (pageno 0, prev pages 0).
B ***LOG BZY=> unexpected return code 128 calling RT_INSERT [dbmyclu 14831]
B dbmyclu : c3_create_cluster_on_db (1.17700): received return code 2 from c3_write_page_on_db.
B dbmyclu : c3_create_cluster (1.17570): received return code 2 from c3_create_cluster_on_db.
B myCluster: RFBLG myKey: 010*1000*4924684447*2019
B dbmyclu : c2_one (1.4566): failed to create new cluster for insertion (rc 2, fcode 130, table BSEG ).
B dbmyclu : db_rclu2 (1.2885): received return code 2 from cluster access for fcode 130, table BSEG , cluster RFBLG - The function DB_GET_TRIGGERS for table cluster RFBLG shows there are SLT DB triggers.
Read more...
Environment
- SAP NetWeaver Release independent
- SAP Landscape Transformation Replication Server
Product
Keywords
RFBLG, Triggers, BSED_INSERT, SAPLF005, ab_HandleRsqlErrors, SLT, return code 128, db_xrtab , KBA , BC-DB-DBI , DB Independent Database Interface , CA-LT-SLT , SAP Landscape Transformation Replication Server (SLT) , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.