Best practice for SAP HANA maintenance tasks

[Al_gar]

Hi @Bill_Steinagle ,

Last week’s Q&A with Qlik: Qlik Replicate Sources and Targets you were tagged on the Q&A with Qlik: Qlik Replicate Sources and Targets - YouTube on a question about best practice for Qlik Replicate during an SAP HANA maintenance window (e.g. adding a column or releasing transport), but not quite sure we got the answer we were looking for.

We have some assumptions during the SAP HANA (source endpoint) maintenance window, but just want a confirmation since I couldn’t find it in the Qlik Replicate guides:

1. For new table column at the source endpoint, if data is loaded (either by default or update) we would need to do a full reload for that particular table at the target endpoint
2. Qlik Replicate task must be stop before the SAP HANA maintenance window  and for any particular table triggers must be dropped at the source endpoint
3. After SAP HANA maintenance window completed the corresponding table triggers must be recreated at the source endpoint and the Qlik Replicate task can be resumed

However, is there any whitepaper that guides customer as to how successfully accomplish this? Are this assumptions correct? Is there any other task that we might need to consider to successfully complete this particular task? our target endpoint is SQL Server 2019.

Thanks!

[boaz_newman]

Hello

Please open a support ticket for those questions.

boaz

[Bill_Steinagle · Accepted solution]

@Al_gar 

Good day thank you for the post to the QDI Forums. See below details for this case and let me know if this is helpful. See below and let us know. 

• For new table column at the source endpoint, if data is loaded (either by default or update) we would need to do a full reload for that particular table at the target endpoint

             Answer: The SAP HANA trigger base endpoint does not support DDL operations

• Qlik Replicate task must be stop before the SAP HANA maintenance window  and for any particular table triggers must be dropped at the source endpoint

             Answer: With any DB Maint it is good practice to stop the Replicate Tasks and do the Maint and then                             Resume your Tasks

• After SAP HANA maintenance window completed the corresponding table triggers must be recreated at the source endpoint and the Qlik Replicate task can be resume

            Answer: The Tables triggers depending on the type of HANA Maint being done if its not related to                                    Table/Column or anything related to the Tables in your given Task this recreating of triggers should not be                an issue. Need clarify the DB Maint as noted if its not related to the Table/Trigger there should be no issue 

In general any DDL change to a given Table defined in the Task is something that is not supported. Next, for non-PK columns being added the Task must be set to Drop/Create the Target Table and not nothing with the trigger is changes or updated for that Table. And finally, when a new PK column is added, you must drop the triggers on the source and then also do a full reload with DROP/CREATE on the target.

Thanks,

Bill Steinagle

QDI Support

[rachin99]

Try hunting through the SAP Fiori Library. There are several different apps for Work Center Scheduling, though some only work with the PP/DS license. The base ones should work for PM work centers. Unless you are talking about Resources as in personnel, that is a different beast and no native Fiori apps that I'm aware of, without going to Service Mgmt SaaS solution.

[Al_gar]

Thanks @Bill_Steinagle. This clarifies how we carry out some of our processes. 

[Kohila]

Hello, Bill We are experiencing this situation. We are investigating the potential of continuing without reloading when Qlik Triggers are dropped in SAP Hana source during their upgrade procedure.

Observing your response, I can see that resume is feasible when triggers can be Re-created  in source with no  DDL table modifications. Must it be manually created on Hana's end?

Thanks,

Kohila

[Bill_Steinagle]

@Kohila 

Good day thank you for the post to the Forums. Yes that is correct to ensure completeness of the Triggers for the given Tables the syntax is under the path\Task\Task Name\scripts directory. If there is no change to the given Tables when the scripts directory was created for the given Tables these can be used to manually create the triggers.

Thanks,

Bill