Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. IMPORTANT DETAILS
cancel
Showing results for 
Search instead for 
Did you mean: 
husainbhavna
Contributor II
Contributor II

DB2 statements issued when using Qlik Replicate

Hello All, 

I am using DB2 Qlik replicate to load data into DB2. I want to know what are the actual commands issued by Qlik Replicate on DB2 when: 

1 ) Performing a Full Load and the 'DROP and CREATE Table' is selected if the target table already exists

2) Performing a Full Load and the 'TRUNCATE before loading' is selected if the target table already exists

Also on which scenario does the following statement run by Qlik Replicate on DB2:

ALTER TABLE "SCHEMA"."TABLENAME" activate not logged initially with empty table

Your inputs will be much appreciated. Thank you

Best Regards,
Husainbhavna

2 Solutions

Accepted Solutions
Heinvandenheuvel
Specialist III
Specialist III

The absolute best way to know what is being asked from a DB is to ask that DB.  For Oracle that could be queries to the V$SQL table and its friends, or Event 10046 trace files. For DB@ that might be through https://www.ibm.com/docs/en/db2/10.5?topic=statements-create-event-monitor or DB2TRC. Most databases have 3rd party tools to help with this. Toad might be a good choice.

Replicate can help through its logs. First enable TRACE level logging for TARGET_LOAD and TARGET_APPLY.  See if that give enough detail for your needs. If not enough, then switch to VERBOSE. Because VERBOSE can be VERY verbose please be sure to test to tiny table and tiny change batches. Like 10 rows to load, 2 rows to insert.

Hein.

View solution in original post

lyka
Support
Support

Hello,

 

Enabling TRACE or VERBOSE logging will give you some details on this.

 

For Full load, increase the logging for target_load and source_unload.

For CDC, increase the logging for target_apply and source_capture.

 

Hope this helps!

 

Thanks

Lyka

View solution in original post

4 Replies
Heinvandenheuvel
Specialist III
Specialist III

The absolute best way to know what is being asked from a DB is to ask that DB.  For Oracle that could be queries to the V$SQL table and its friends, or Event 10046 trace files. For DB@ that might be through https://www.ibm.com/docs/en/db2/10.5?topic=statements-create-event-monitor or DB2TRC. Most databases have 3rd party tools to help with this. Toad might be a good choice.

Replicate can help through its logs. First enable TRACE level logging for TARGET_LOAD and TARGET_APPLY.  See if that give enough detail for your needs. If not enough, then switch to VERBOSE. Because VERBOSE can be VERY verbose please be sure to test to tiny table and tiny change batches. Like 10 rows to load, 2 rows to insert.

Hein.

lyka
Support
Support

Hello,

 

Enabling TRACE or VERBOSE logging will give you some details on this.

 

For Full load, increase the logging for target_load and source_unload.

For CDC, increase the logging for target_apply and source_capture.

 

Hope this helps!

 

Thanks

Lyka

husainbhavna
Contributor II
Contributor II
Author

Thank you Hein. Setting to VERBOSE helped. 

husainbhavna
Contributor II
Contributor II
Author

Hello Lyka, 

Thank you. Setting to Verbose helped.

 

Sincerely,

Husain