Replicate Table Column in Log Stream

[Al_gar]

For Qlik Replicate November 2024 (2024.11.0.177) I have a staging task that is replicating data from HANA to log stream files and another task that is replicating the data from the staged log stream files to the target database (SQL Server 2022). What is the correct process to replicate HANA table schema changes to the staged log stream and target database? (i.e. new column, data type change)

[Dana_Baldwin]

Hi @Al_gar 

Is the source endpoint a direct connection to SAP HANA, SAP Application, or SAP Application DB endpoint with HANA on the back end?

Are you experiencing a specific error message when there are table/schema changes on the source, or are they just not flowing through?

In task settings \ Change Processing \ Apply Changes Settings, what are the DDL Handling Policy items set to?

Thanks,

Dana

[Al_gar]

Hi @Dana_Baldwin,

We're using SAP HANA as a source. When there's a table change it's not flowing through to the target task. In our specific scenario we're making a change to an SAP HANA table schema (i.e. added column named "FLAG3 NVARCHAR(1) NULL") and the change is not showing up on the target db. At this time the DDL handling policy set for When source table is altered is "ALTER target table".

This are the steps we're following:
1. Changes are made in SAP HANA table: Add column FLAG3 NVARCHAR(1) NULL
2. Qlik Replicate target task is stopped and table is set to reload
3. Qlik Replicate target task is resumed with Full load option set to Drop and Create

After resuming the task the new column is not visible. Reloading the task will not show the SAP HANA changes either.

[Dana_Baldwin]

Hi @Al_gar 

Are you using trigger based, or log based? Trigger based does not support DDL operations.

See:
Limitations and considerations | Qlik Replicate Help

Having said that, the full load should update the target schema to match the source, but only if full load settings are "drop & recreate table".

Thanks,

Dana

[Al_gar]

Yes, we're using triggered based CDC. We have tried to Resume and Reload the task with Full load option set to "Drop and Create", but no luck getting the table changes flown down to the target db.

[Dana_Baldwin]

Ok thanks @Al_gar 

Please open a support case so we can look into this further. We will need a diagnostics package and the log file from the last attempt to reload.

Thanks,

Dana

[Al_gar]

Thanks @Dana_Baldwin. Will do.