Skip to Content
0

SLT downtime

Jul 23, 2017 at 07:47 AM

111

avatar image

Hi All,

We have SLT system in place and we are loading data at 1:00 AM daily. ECC--->SLT at 1:00 AM daily replication happens for 42 tables. We had a planned downtime in ECC, it started on Thursday 9 PM, before which we had "Suspend Replication" in SLT system.

On Saturday night source system was up-again, so we "Resumed load",but still the replications have failed with "Missing trigger for table SWWWIHEAD for MT ID 006. Replication suspended."!!!

What did we miss? Should we have replicated on Friday morning 1:00 AM and then suspended the replication. When the source system was down at 9:00 PM we still had triggers open for the tables in source and these were not replicated to HANA via SLT.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

4 Answers

Andrey Martynov
Jul 24, 2017 at 02:12 PM
0

1. Check if you connection to the source system is still alive
2. Check if the trigger in source system for the table exists
of course, suspend command should not delete triggers. SLT tool don't have such functionality by suspending. So, either the SLT tool wrongly calculated number of triggers or triggers were deleted outside from SLT.

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Aug 08, 2017 at 04:33 PM
0

Is there any structural changes happened on SWWWIHEAD table during downtime. if so there is a chance of triggers get delete.

Share
10 |10000 characters needed characters left characters exceeded
Gregor Horvath Aug 22, 2017 at 03:21 PM
0

hi,

Oh, you went for "Suspend".....

I never ever do that in case of a planned system outage.

In such a case, I always go for deactivating the whole replication.

It simply works better than suspending.

As you have only 42 tables......copy & paste all the tables into an excel sheet, stop load/replication for all those table, wait until they're gone and then.....start replication for all the tables.

If it is only one table....then delete all triggers and settings for that table (expert functions) and retry. You might need several attempts....this should work fine too.

regards

Share
10 |10000 characters needed characters left characters exceeded
avatar image
Former Member Sep 01, 2017 at 11:13 AM
0

Hi,

Even i agree, incases when there is a planned down time, it is better to deactivate the configuration and then activate it when the system is available.

Regards,

Saritha

Share
10 |10000 characters needed characters left characters exceeded