How To Fix RSODSO_ROLLBACK255 - Database call for in-memory-optimized rollback ended with errors

SAP Error Message - Details

• Message type: E = Error

• Message class: RSODSO_ROLLBACK - DataStore Object: Messages for rollback

• Message number: 255

• Message text: Database call for in-memory-optimized rollback ended with errors

What causes this issue?

Database call for In-Memory-optimized rollback ended with errors.

System Response

DataStore object: &V1&
Request: &V2&

How to fix this error?

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

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSODSO_ROLLBACK255 - Database call for in-memory-optimized rollback ended with errors ?

  The SAP error message RSODSO_ROLLBACK255 indicates that there was an issue during the rollback of an in-memory optimized operation in SAP BW (Business Warehouse) or SAP HANA. This error typically occurs when there is a failure in the database call that is responsible for rolling back changes made during a transaction.
  Causes:
  
  Database Connection Issues: Problems with the connection to the database can lead to rollback failures.
  Data Consistency Issues: If there are inconsistencies in the data being processed, it may cause the rollback to fail.
  Resource Limitations: Insufficient memory or other resources on the database server can lead to errors during rollback operations.
  Transaction Log Issues: If the transaction log is full or corrupted, it may prevent successful rollback.
  Configuration Issues: Incorrect configuration settings in the SAP BW or HANA system can lead to errors during database operations.
  
  Solutions:
  
  Check Database Connection: Ensure that the connection to the database is stable and functioning correctly. You may need to restart the database or check network connectivity.
  Review Logs: Check the SAP application logs (transaction SLG1) and database logs for more detailed error messages that can provide insights into the cause of the rollback failure.
  Monitor System Resources: Use monitoring tools to check the memory and resource usage of the database server. If resources are low, consider increasing them or optimizing the workload.
  Transaction Log Management: Ensure that the transaction log is not full. If it is, you may need to back it up or clear it to allow for new transactions.
  Data Consistency Checks: Run consistency checks on the data to identify and resolve any inconsistencies that may be causing the rollback to fail.
  Configuration Review: Review the configuration settings for the SAP BW or HANA system to ensure they are set correctly for your environment.
  
  Related Information:
  
  SAP Notes: Check for relevant SAP Notes that may address this specific error or provide patches and updates that could resolve the issue.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  Documentation: Refer to the official SAP documentation for guidance on handling database transactions and rollbacks in SAP BW and HANA.
  
  If the issue persists after trying the above solutions, it may be necessary to contact SAP support for further assistance.