Gluesync for DB2 LUW

Gluesync SQL to NoSQL for DB2 LUW

Core principles

Gluesync on DB2 LUW uses the GDC (Gluesync Data Capture) feature to let the magic happen under the hood, more specifically Gluesync adopts an optimized triggers structure to catch events generated by operations that hit fields in your source DB2 LUW database.

Triggers on GDC are based on a per-transaction logic and only track changed row IDs, storing data on a table called Action logs table where all changed row IDs are stored and their data type is maintained unaltered.

This technique is also known as change tracking pattern. This is the opposite of change data capture which does not require a copy of all the data present in all the columns involved in a commit, this ensures performance gain and less footprint per each transaction on your source database since no data transformation or manipulation is being required by our design.

Architectural overview

Here in the following diagram represents an architectural overview of the environment you are going to have after having deployed Gluesync.

a diagram illustrating the architectural overview of Gluesync for DB2 LUW

Q&A

I have got DB2 on an i series system, is it supported? IBM Power (AS/400) is supported and requires the usage of a specific Gluesync source connector for IBM Power that makes use of the AS400 built-in journal. To read more about this specific source connector you can follow this link.

I have got DB2 running on z/OS (aka mainframe) is it supported? This specific version has not yet been tested. If you would like to consider helping us with testing in this system please reach out to us by writing at hello@molo17.com.

Having further questions? For more information regarding Gluesync please reach us via email by pressing here: Contact MOLO17.