Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
We have Oracle source and Snowflake as target.
DDL changes are applied to the Oracle Source for monthly releases.
We have noticed that the DDL changes are not migrated to snowflake in several occasions and the behavior is very inconsistent.
In the most recent release, the following DDL changes on Source Oracle have not been migrated to snowflake when the CDC task resumed.
Please provide resolution for this issue to have DDL changes automictically migrate without intervention (intervention in most cases required reload target tables to capture DDL changes.)
thank you so much.
Hello,
Replicate only supports the following DDL statements:
Supported DDL statements include:
There are also some limitations like:
ALTER TABLE ADD/MODIFY <column> <data_type> DEFAULT <>
does not replicate the default value to the target and the new/modified column is set to NULL. Note that this may happen even if the DDL that added/modified the column was executed in the past. If the new/modified column is nullable, the source endpoint updates all the table rows before logging the DDL itself. As a result, Qlik Replicate captures the changes but does not update the target. As the new/modified column is set to NULL, if the target table has no Primary Key/Unique Index, subsequent updates will generate a "zero rows affected" message.For a complete list please refer to:
Thanks
Lyka
Hello,
Replicate only supports the following DDL statements:
Supported DDL statements include:
There are also some limitations like:
ALTER TABLE ADD/MODIFY <column> <data_type> DEFAULT <>
does not replicate the default value to the target and the new/modified column is set to NULL. Note that this may happen even if the DDL that added/modified the column was executed in the past. If the new/modified column is nullable, the source endpoint updates all the table rows before logging the DDL itself. As a result, Qlik Replicate captures the changes but does not update the target. As the new/modified column is set to NULL, if the target table has no Primary Key/Unique Index, subsequent updates will generate a "zero rows affected" message.For a complete list please refer to:
Thanks
Lyka
Hello @lyka, Does these DDL only for log based CDC enabled table or for all CDC methods?
Regards
Fazil M
Hello @MdFazil
Seems above info is more related to Oracle endpoint. You can start the QR from the timestamp with the resume timestamp .so it will force metadata refresh which helps you to deal in most cases required reload target tables to capture DDL changes.
And do check for Supplemental logging for the updated table as well. if supplemental logging is enabled with all colls and you have added columns in that table you have to delete and readd the supplemental logging as QR only enforce pk Supplemental logging.
Regards,
Sushil Kumar