Warning : TRANSACTION statement was not captured

[harsh2]

Hi Qlik Team,

After a successful replication, I received multiple warnings similar to the following:

Transaction '00000000000000000000134085337934' was committed after the Full Load started and the BEGIN TRANSACTION statement was not captured. Consequently, some changes may not be replicated (Record ID : 9041792; Source ID : 0; Stream Position : 'LA7JRN:PAXUS37747:134085339522').

I would like to understand the implications of this on my CDC.

Thanks,

Harsh

[john_wang]

Hello @harsh2 ,

Thanks for reaching out to Qlik Community!

Would you please share what's the Replicate version and the DB2i version? In general it means a half transaction was captured by Qlik Replicate however we need additional information to proceed.

thanks,

John.

[aarun_arasu]

Hello @harsh2 ,

Thank you for contacting Qlik Community Support.

As per John's request, could you please provide information about your Replicate version? I recall a similar issue being resolved in version 2023.05."

Regards

Arun

[deepaksahirwar]

Dear @aarun_arasu ,

This warning means that some transactions were committed after the full load started, but before the CDC was enabled on the source database. Therefore, the changes made by those transactions may not be captured by the CDC process.

Some possible solutions to avoid this warning in the future, such as:

1 Enabling CDC on the source database before starting the full load.

2 Using the Capture from option to specify a point in time before the full load started.

3 Using the Capture from LSN option to specify a log sequence number before the full load started.

If our response has been helpful, please consider clicking "Accept as Solution". This will assist other users in easily finding the answer

Regards,D

eepak

[SushilKumar]

Hello Team,

To add more to Deepak comments this is basically a warning. Which indicate Database  manages ACID property of transaction. Where Replicate have info about ongoing transaction however no info of When it was initiated hence its shows such warnings.

Regards. 

Sushil Kumar

here its about Data integrity if  

[harsh2]

Hi @john_wang and @aarun_arasu 

Here is our Replicate version and the IBM version.

Replicate version : 2023.5.0.516

IBM version : IBM i 7.3 (v7r3m0)

Thanks & regards,

Harsh Patel

[DesmondWOO · Accepted solution]

Hi @harsh2 ,

It appears that there was an opening transaction before the task started. Please check if the "Transaction consistency timeout (seconds)" setting helps.

Regards,
Desmond

[john_wang · Accepted solution]

Hello @harsh2 ,

Replicate version : 2023.5.0.516

IBM version : IBM i 7.3 (v7r3m0)

---

Thanks for the information. We'd a minor defect fix in previous build (2023.5.0.413) to repress the ambiguous warning messages, you are running 2023.5.0.516 which contains the fix already. if the messages show up in the short time after the task startup then it's reasonable, please reference to previous comment of Desmond. If the message come up after all tables full load finished then we need more researching.

Regards,

John.