How To Fix RSDA344 - Consistent data selection from database and archive not guaranteed

RSDA344 - Overview

• Message type: E = Error

• Message class: RSDA - BW Archiving: Messages

• Message number: 344

• Message text: Consistent data selection from database and archive not guaranteed

What causes this issue?

Consistent selection of data from the database and the archive /
near-line storage of the InfoProvider &v1& cannot be guaranteed. During
the runtime of the data selection, the archiving or reload request &v2&
had a status for which it is not possible to guarantee data consistency.
This can occur if an archiving request is in the deletion phase during
the selection or if a reload request is active.
At the start of the selection, the UTC timestamp of the partitioning
status was &v3&. The current UTC timestamp is &v4&.

System Response

The current data selection was terminated.

How to fix this error?

Repeat the process if no archiving or reload runs are active.

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 RSDA344 - Consistent data selection from database and archive not guaranteed ?

  The SAP error message RSDA344 indicates that there is an inconsistency in the data selection process between the database and the archive. This typically occurs when you are trying to access data that is stored in both the database and the archive, and the system cannot guarantee that the data is consistent across both sources.
  
  Cause:
  
  Data Archiving: The error often arises when data has been archived but the corresponding entries in the database have not been updated or deleted. This can lead to situations where the same data exists in both locations, but the versions may differ.
  Inconsistent Data State: If the data in the database has been modified after it was archived, there may be discrepancies between the archived data and the current state of the database.
  
  Configuration Issues: There may be issues with the configuration of the data archiving process or the way the data is being accessed.
  
  
  Solution:
  
  Check Archiving Status: Verify