DB2 Trigger after commit

Haresh · New User Joined: 04 Jan 2009 Posts: 18 Location: Germany

Hi

please let me know is there some way to make the DB2 trigger to work only after the DB2 commit.

We have a DB2 table which will be inserted/updated/deleted by many applications. We need to capture these changes and replicate in another system in near time basis.

The main problem is all these insert/delete/update within a transaction are inter related and should be replicated as single request.

Thank You

dick scherrer · Posted: Thu Mar 03, 2011 10:07 pm

Hello,

At the top of the page is a link to "IBM Manuals". Look at the SQL Reference for your release of DB2.

This is not a proper use for a TRIGGER . . .

Haresh · New User Joined: 04 Jan 2009 Posts: 18 Location: Germany

Hi

i already went through the manual, but i just want to know whether any of you guys cracked a similar scenario.

Anyway now i am looking into the option of 'DB2 Probagator' for my requirement.

thank you for the reply

sushanth bobby · Posted: Fri Mar 04, 2011 1:10 am

Hi Haresh,

In my place we use two kinds of tools for replication tool,

CA-Log Analyzer - Which will be executed after the batch process, it gets all the changes happened to table during that day and generates SQL STATEMENTS which is FTP'd and executed at multiple MS-SQL SERVER's.

We are starting to use Attunity Product for real-time replication, capturing changes from mainframe and ship it to SQL SERVER. This product even captures VSAM changes.

Thanks,
Sushanth

Haresh · New User Joined: 04 Jan 2009 Posts: 18 Location: Germany

Hi Sushanth,

thank you for the details,
will have a look on both the things and check whether it will fit in our system.

Haresh