How To Fix RSDRI_HDB129 - Number of records copied (&3): &1. Expected: &2.

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDRI_HDB - InfoCube Conversion Program

• Message number: 129

• Message text: Number of records copied (&3): &1. Expected: &2.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDRI_HDB129 - Number of records copied (&3): &1. Expected: &2. ?

  The SAP error message RSDRI_HDB129 typically occurs in the context of data extraction or data loading processes, particularly when working with SAP HANA databases. This error indicates a discrepancy between the number of records that were actually copied and the number of records that were expected to be copied during a data transfer operation.
  Cause:
  The error message RSDRI_HDB129 can be caused by several factors, including:
  
  Data Inconsistency: There may be inconsistencies in the source data that prevent all expected records from being copied.
  Filter Conditions: If there are filters applied during the data extraction process, they may limit the number of records being copied.
  Data Type Mismatches: If there are data type mismatches between the source and target systems, some records may fail to copy.
  Database Locks: If the source database is locked or if there are concurrent processes that affect data availability, this can lead to fewer records being copied.
  Network Issues: Temporary network issues can interrupt the data transfer process, leading to incomplete data being copied.
  
  Solution:
  To resolve the RSDRI_HDB129 error, you can take the following steps:
  
  Check Data Consistency: Verify the integrity of the source data to ensure that it is complete and consistent.
  Review Filter Conditions: Examine any filters applied during the extraction process to ensure they are set correctly and not excluding records unintentionally.
  Data Type Validation: Ensure that the data types in the source and target systems match. If there are discrepancies, adjust the data types accordingly.
  Monitor Database Locks: Check for any locks on the source database that may be preventing records from being accessed. Resolve any locking issues if necessary.
  Network Stability: Ensure that the network connection is stable and that there are no interruptions during the data transfer process.
  Re-run the Data Transfer: After addressing the above issues, attempt to re-run the data transfer process to see if the error persists.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common errors.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench) and RSD1 (InfoObject Maintenance) for monitoring and managing data extraction processes.
  Logs and Traces: Review logs and traces for more detailed error messages that can provide additional context about the failure.
  
  If the issue persists after trying the above solutions, consider reaching out to SAP support for further assistance, providing them with detailed information about the error and the steps you have already taken.