How To Fix RSBK072 - Database selection was interrupted (see long text)

SAP Error Message - Details

• Message type: E = Error

• Message class: RSBK - Messages for the Data Transfer Process

• Message number: 072

• Message text: Database selection was interrupted (see long text)

What causes this issue?

You are extracting data from a DataSource or an InfoProvider. The
selection is made with an open database cursor. This cursor was in
validated by one of the following ABAP commands:
<AB>COMMIT WORK</>
<AB>ROLLBACK WORK</>
<AB>CALL TRANSACTION</>
<AB>SUBMIT</>
The ABAP command leading to the termination was probably executed in a
custom transformation routine.

System Response

Processing of the request ended with errors.

How to fix this error?

Change the code of the transformation in which one of the
above-specified ABAP commands is executed. If you are using the command
<AB>COMMIT WORK</>, replace it with the following call:
<AB>CALL FUNCTION 'DB_COMMIT'.</>

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSBK072 - Database selection was interrupted (see long text) ?

  The SAP error message RSBK072, which states "Database selection was interrupted," typically occurs in the context of data extraction or reporting in SAP BW (Business Warehouse). This error can arise due to various reasons, including issues with the database connection, performance problems, or interruptions in the data retrieval process.
  Causes:
  
  Database Connection Issues: The connection to the database may have been lost or interrupted, leading to the failure of the data selection process.
  Timeouts: Long-running queries may exceed the allowed execution time, causing the system to terminate the process.
  Resource Limitations: Insufficient system resources (CPU, memory, etc.) can lead to interruptions in data processing.
  Locks or Deadlocks: Other processes may be locking the database tables, preventing the current query from executing.
  Network Issues: Problems with the network can disrupt communication between the SAP application server and the database server.
  
  Solutions:
  
  Check Database Connection: Ensure that the connection to the database is stable and functioning correctly. You can test the connection from the SAP GUI or use transaction codes like DBACOCKPIT.
  Increase Timeout Settings: If timeouts are causing the issue, consider increasing the timeout settings for database queries in the SAP system configuration.
  Monitor System Resources: Use transaction codes like ST02 (Tune Summary) or ST04 (Database Performance Analysis) to monitor system performance and identify any bottlenecks.
  Check for Locks: Use transaction code SM12 to check for any locks on the database tables that might be causing the interruption. If necessary, release the locks.
  Review Network Stability: Ensure that the network connection between the SAP application server and the database server is stable and has sufficient bandwidth.
  Optimize Queries: If specific queries are consistently causing issues, consider optimizing them for better performance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ST22 (Dump Analysis), SM21 (System Log), and SLG1 (Application Log) to gather more information about the error.
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  System Logs: Review system logs for any additional error messages or warnings that may provide context for the interruption.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.