avatar image
Former Member

SLT During Source and Target System refresh

I am trying to understand the correct handling of SLT during a refresh of a source ECC and target HANA system. I have read through the document titled "Resuming Replication Without Initial Load After System Refresh or OS/DB

Migration" but still have a couple of clarification questions.

1.) It states that all delta data has to be replicated prior to the system copy being taken. Does this mean no user or batch activity is allowed on the source system since that could create further delta data and hence the source system has to be under maintenance?

2.) Does the SLT configuration need to be disabled in the production SLT system prior to the source and target system copy or only in the QA SLT system?

3.) There is an additional step to be performed if the HANA Data Provisioning UI is being used. The table RS_REPLICATION_COMPONENTS needs to be adapted for source and target. Is there a way to simply disable the data provisioning UI in HANA to begin with so it cannot be used? If not, does it just mean if that table is not maintained after refresh replication still works but the HANA UI can no longer be used?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 22, 2016 at 04:55 PM

    Hi Martin

    I think you are referring to note 1933605.

    I tried this solution to resume replication without initial load Load after System Refresh or OS/DB and it never did work for me, and always I ended by in reloading the tables.

    1) yes we have to stop any activities on the source system prior to system copy

    2) You need stop SLT replication on both Source SLT and target SLT system and any activities on  source system as it will create additional delta some data will be residing the logging tables.

    3) I don't have much info on this

    also this solution may not work if you have multi usage scenario, ie., 1 source --> 2 SLT --> 2 HANA.

    This solutions is more designed in case of os/db migration not for system refresh.

    some times the migration process will delete the triggers.


    Kishore Ch

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Kishore,

      Thanks for your input on whether this method is successful or not.

      I also got the sense that the document was more geared towards OS/DB migration versus system refresh.

      Based on your experience does it make any sense to refresh SLT as well when source and target are refreshed or since SLT is more of a middleware component it makes no sense to refresh it from PRD to QA and in case source and target get refreshed just include the time to initialize and reload all tables to be replicated?



Skip to Content