How to change SLT system without reloading tables on Hana

[robertom]

Dears,

I have an SLT system, we can call it SLA , ver DMIS 2011_1_731 pl 13 used to Replicate tables from an ECC source systems into an Hana Database using a specific Configuration X.

Now for infrastructure matters I have to move this Configuration X to another SLT , called SLB, alligned to the same DMIS version.

SLB is already in use to Replicate tables from different ECC systems to other Hana databases, so in tx LTRC already exist Configurations.

As the tables Replicated via SLA are used on Hana for productive purposes, I would like to avoid to Stop the Replication on SLA for these tables and begin it again on SLB, redoing the whole Initial Load.

During this time I would have lack of services in Production.

I need to clarify if there is a way to copy or transfer the ltrc's Configuration X from SLA to SLB without to redo the Initial Load.

Best regards

[antonio_nunes1]

Hi

Starting with DMIS 2011 SP13 you can avoid the load with the Data Provisioning option "Start Replication (w/o Load)"

Regards

A.Nunes

[ken_halvorsen2]

Hi Roberto

Why wouldn't doing a system restore to the new system, from a Backup of the old system work? (I'm assuming it would be possible to install the SLT with the same SID as the old system).

Ken

[manish_gupta32]

Hi Roberto,

Its not possible to copy configuration from SLA to SLB, but when you re-create the config in SLB, its possible to avoid the initial load.

You can add a dummy filter for one of the fields, for eg: Document Number in LTRC for the specific table, this will prevent the initial load, and your table will switch to replication mode quickly.

Let me know if you need more help/info.

Regards,

Manish

[former_member313124]

Dear Roberto

Unfortunately it is not possible to copy or transfer the ltrc's Configuration X from SLA to SLB without to redo the Initial Load as there is a dependency on the structure mapping and write modules. Also when you create a new config in SLB, please try to check the logging table sequence and ensure that it does not conflict with existing read modules in the source system.

[robertom]

Thanks Manish

Please could you explain a little bit what do you mean about the dummy filter that can be added in order to skip the Initial Load phase ?

As draft this is what I was thinking:

- On SLA to suspend the Replication for the table and then to deactivate the COnfiguration

- on SLB to create a new Configuration with the same name,but here I have another problem , because on the target Hana Database that schema already exist.

And the SLB will ask me the psw of the existing schema. Can I reuse this or the SLB will try to drop it in any case ?

- Then I add the table and I should add a dummy filter in advanced options in order to skip the Initial Load,

- Finally run the Replication again for that table.But I can prevent the table to be truncated when the Replication starts ?

regards