Data Insight User Guides
SE14 Technical Recovery Activity – /ADM/TDTTCLSLINK
This section explains a controlled technical recovery activity that may be required before restarting a DDR replication process. The SAP table /ADM/TDTTCLSLINK is used by DDR for cluster and configuration linkage processing during replication execution.
In this recovery scenario, the table is handled through SAP transaction SE14 using Activate and Adjust Database with the Delete Data option selected. This is a controlled technical reset activity and must only be performed when required.
Why This Technical Recovery Step May Be Required
The table /ADM/TDTTCLSLINK stores DDR cluster and runtime linkage information used during replication execution. In some recovery situations, existing linkage data may need to be cleared before the same template is executed again.
This can be required when a previous execution has left inconsistent runtime linkage information after an interrupted or failed DDR process.
- ABAP runtime dump during DDR processing
- Interrupted export or import processing
- Cancelled workprocesses
- Incomplete replication execution
- Failed overwrite or recovery execution
- System termination during replication
- Cluster linkage inconsistency
- Template re-execution issue caused by stale runtime linkage records
This activity deletes the data held in /ADM/TDTTCLSLINK. It must only be performed by authorised SAP Basis administrators or DDR technical administrators and only when the recovery scenario requires the runtime linkage information to be cleared.
Recommended SE14 Recovery Settings
Open SAP transaction SE14 and enter the DDR table /ADM/TDTTCLSLINK.
| Setting | Required Value |
|---|---|
| Table Name | /ADM/TDTTCLSLINK |
| Processing Type | Direct |
| Recovery Action | Activate and Adjust Database |
| Data Option | Delete Data |
The screenshot above shows transaction SE14 for table /ADM/TDTTCLSLINK. The recovery action is Activate and Adjust Database and the data option selected is Delete Data. This means existing table data is cleared as part of the database adjustment activity.
Why the Delete Data Option Is Required Here
The Delete Data option is used in this recovery step because the purpose is to clear existing DDR runtime linkage or cluster linkage records that may have been left behind from a failed or incomplete replication execution.
If stale or inconsistent linkage records remain, DDR may continue to reference old runtime information when the same template is executed again. Clearing the table helps ensure the next execution starts with a clean linkage state.
This must not be treated as a standard daily process. It is a technical recovery/reset step and should only be performed when advised or approved by the responsible DDR technical team.
Do Not Perform During Active DDR Processing
This activity must NEVER be executed while DDR processing is active.
Before performing SE14 activity, administrators must confirm:
- No DDR export jobs are active
- No DDR import jobs are active
- No background workprocesses are processing DDR data
- No scheduled refresh activity is running
- DDR Monitoring does not show ACTIVE runtime status
- The same table is not being used by an active DDR process
Performing this SE14 activity during active DDR processing may result in:
- Loss of active runtime linkage records
- Export corruption
- Replication inconsistency
- Cluster linkage mismatch
- Cancelled background jobs
- Runtime dumps
- Incomplete refresh processing
- Failed template execution
Technical Validation Before Execution
Enterprise Data Insight strongly recommends validating the DDR runtime environment before performing this activity.
- Check DDR Monitoring
- Review DDR Error Log
- Validate SAP transaction SM37
- Review SAP runtime dumps in ST22
- Validate workprocess activity through SM50 or SM66
- Confirm Source and Target systems are stable
- Confirm no active DDR export or import is running
Next Step After Completion
Once the SE14 activity has completed successfully:
- Return to DDR Dashboard
- Select the same DDR Template ID
- Execute the same template again if the original scope is still required
- Monitor the execution through DDR Monitoring
This allows DDR to execute again after the technical linkage reset has been completed.