Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE

Qlik Replicate: PostgreSQL Aurora in RDS source is not replicating DDL changes

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Barb_Fill21
Support
Support

Qlik Replicate: PostgreSQL Aurora in RDS source is not replicating DDL changes

Last Update:

Nov 13, 2023 12:09:43 AM

Updated By:

Sonja_Bauernfeind

Created date:

Nov 13, 2023 12:06:15 AM

During the replication of a table from an Aurora Postgres database in AWS source to a Snowflake database in AWS target, the data appears to replicate properly, but the DDL does not come through. Apply Changes Processing is turned on to allow DDL changes to come through, but there is no indication that Qlik Replicate sees the DDL at all. Permissions and authorizations are set correctly.  

Environment

  • Qlik Replicate  - Any Version 
  • AWS Aurora Cloud for PostgreSQL

Resolution

Verify your PostgreSQL database's session_replication_role setting. If it is currently set to replica, set it to either origin or local.

Cause 

The session_replication_role setting is used to enable or disable triggers. By default, tables are created with all triggers enabled, which means that they fire with the default setting "session_replication_role = origin".  When it is set to "replica", it disables the firing of triggers.  

Qlik Replicate uses a Stored Procedure called attrep_intercept_ddl to help capture the DDL. 

Related Content  

Using an account without the "superuser" role

Labels (1)
Version history
Last update:
‎2023-11-13 03:09 AM
Updated by: