This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(182.40000000000003, 55.00000000000001%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESD%3C/text%3E%3C/svg%3E)
SAP CDC data replication has been activated in Azure Data Factory, and the following error has recently been observed:
Job failed due to reason: at Source 'S4CDC: Error Message: DF-SAPODP-012 - Sapodp copy activity failure with run id: 7c61e233-e833-42e2-a625-c405egdgdeg4, error code: 2200 and error message: ErrorCode=SapOdpOperationFailed, 'Type-Microsoft.DataTransfer.Common.Shared.HybridDeliveryExceptiomMessage=Sap View error detail
Odp operation 'OpenOdpRead' failed. Error Number: '505', error message: 'Pointer does not contain source XXXXX or is no longer available', Source= Microsoft.DataTransfer.Runtime.SapRfcHelper
While it is possible to restart the flows by reinitializing, this approach is not viable for large tables. There is a need to identify the root cause and establish a recovery strategy.
Any suggestions to (a) understand what might have happened and (b) how to recover delta loads?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(99.2, 65%, 19%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ECB%3C/text%3E%3C/svg%3E)
Just checking in to see if the below suggestion helped. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
As I know it is different to timeout error, so maybe the source data is modified / locked during replication and it didn't handled correctly,
Maybe SAP community can help better
https://community.sap.com/t5/technology-q-a/qa-p/technology-questions
Greetings & Welcome to Microsoft Q&A forum! Thanks for posting your query!
The error you encountered during SAP Change Data Capture (CDC) data replication in Azure Data Factory (ADF) indicates a failure in the SAP ODP (Operational Data Provisioning) operation, specifically "Error Number: '505', error message: 'Pointer does not contain source XXXXX or is no longer available'," suggests that there may be an issue with the SAP source configuration, or the availability of the data being referenced.
Here are some troubleshooting steps that might help you in resolving your issue:
If the initial load has successfully worked, then please try updating the Checkpoint key and redo the initial load.
As suggested by @Vahid Ghafarpour
If the issue still persists, I recommend you to please reach out in SAP community forum as well as open a support ticket with SAP to further investigate on this as it seems more of SAP side problem.
I hope this information helps. Please do let us know if you have any further queries.
If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.
First, thanks for the reply. To expand on what we observed : while the delta loads failed, full loads and also reinitializations continued to work.
On your suggestions, any suggestion how to do the "Pointer Validity" check ? Any clue what would make a pointer suddenly disappear?
The error message you are encountering, specifically "Pointer does not contain source XXXXX or is no longer available," suggests that there may be an issue with the ODP context, or the pointer used for the delta load.
Here are some suggestions to understand the root cause and establish a recovery strategy:
how to do the "Pointer Validity" check ?
Pointer Validity Check: To check the validity of the pointer, you can use the transaction ODQMON in your SAP back-end system. This transaction allows you to monitor the operational delta queues (ODQs) and verify if the pointer associated with your delta load is still valid and available.
For additional information, please refer: Troubleshoot delta changes
Any clue what would make a pointer suddenly disappear?
Potential Causes for Pointer Disappearance:
Recovery Strategy:
Monitoring and Logging: Implement logging and monitoring for your data flows to capture detailed error messages and statuses. This can help in diagnosing issues more effectively in the future.
For more details, please refer: Monitor data extractions on SAP systems
If the issue still persists, I recommend you to please reach out in SAP community forum as well as open a support ticket with SAP to further investigate on this as it seems more of SAP side problem.
I hope this information helps.
Thank you.
Following up to see if the above answer was helpful. If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.