We occasionally have tables that mysteriously stop replicating the data filling the logging tables in the source SAP ECC system. A few times, whether there are errors showing on the table or not (many times there are no errors showing when doing a table health check), the replication has mysteriously resume successful and cleared the logging table a day or 2 later. However, most of the time we are forced to stop and restart replication which has some drawbacks.
- The table may take a long time to reload and until then the users are left no or limited data until the reload is complete.
- Restarting will drop and re-create the table in HANA, and this can deactivate HANA views which will all need to be reactivated.
- We may have some specific tables that we had to use the ALTER TABLE command to change specific field types (this was necessary for STXL long text that we are replicating.
I found the exact same issue described on the SAP community http://scn.sap.com/thread/353304. In it a suggestion is to perform the following (KONV was the example table that had the issue)
Step1 : Suspend Replicationn for table-KONV(LTRC)
Step2 :Go to transaction
IUUC_REPL_CONTENT. Select KONV -> ‘Edit Settings for Selected
Tables’-> Reset Replication Object -> Enter KONV & Save the Configuration
- settings.
Step3: Resume Replication for table-KONV(LTRC)
In IUUC_REPL_CONTENT I do not see the option "Reset Replication Object"
but I do see "Reset Migration Object". Is this the same thing and would
it only regenerate the migration objects, then the runtime objects, and
then proceeds with the replication without dropping the table in HANA?
We are currently on DMIS 2011 SP5 for SLT and I know 1 response will be to upgrade which we are in the process of doing but will not go live for several weeks now. We are replicating over 100 tables from multiple ECC systems, and from a support perspective, it would be helpful to understand techniques to resume replication of the logging table entries short of stopping and restarting replication.