Facing read lock frequently when running Full load tasks on read-replica informix server

[amit-lamba-ns]

Is there any way to read lock issue when we are running full load task again read-replica informix server ?

Any guess, why this read lock happen on read replica server ? 

[john_wang]

Hello @amit-lamba-ns ,

Thanks for reaching out to Qlik Community!

Would you please share the Informix server version, Informix ODBC Driver version, and the Replicate version? BTW, any information about the locks are welcome.

The default isolation level in ODBC is "0 - Default", we'd like to check further for you.

thanks,

John.

[amit-lamba-ns]

we are getting below warning on table, after loading for these table got suspended

ODBC Driver version: 4.10.C14
Replicate version: V2023.5.0.322

[john_wang]

Hello @amit-lamba-ns ,

Thanks for the information. It's better you can share the complete line in reddish color. However please take note that to make sure the data integration in Replicate, the default isolation level should be "Read Committed". Looks to me it's just a warning and can be ignored. Please let me know if you are facing any potential issues.

thanks,

John.

[amit-lamba-ns]

Yes, after this warning, in logs it's been mentioned table (on which read lock) loading is suspended.
Once rest of table in loaded, then Full load task is stopped.

For our use case, we are triggering Qlik full load task through Rest API, keep checking their status. 

For scenario, that i mentioned above, once full load task are stopped, then we are getting some value greater than zero (in highlighted line) in Rest API response (https://{host}/attunityenterprisemanager/api/v1/servers/{ServerName}/tasks/{TaskName} "  

In logs, if it's just warning, However in rest api response, those are represented as "Error"

[john_wang]

Hello @amit-lamba-ns ,

There are several options to resolve this error eg change the isolation level etc, please set SOURCE_UNLOAD to Trace, recreate the error, and attach the task log file and task Diag Packages to a support ticket. We will check and provide findings.

BTW, any idea how to reproduce the lock error?

Regards,
John.

[SushilKumar]

Hello @amit-lamba-ns 

It is always recommended Sticking with the configuration Settings mentioned in the Qlik Help Document only a Support case provide insight because API is considering it as ERROR although it falls under the Warning in Qlik replicate.

Regards,

Sushil Kumar 

[Sreekanth_333]

Hi @amit-lamba-ns, I'm also facing the same issue. Could you please let me know the root cause and how you resolved it?

[DesmondWOO]

Hi @amit-lamba-ns ,

Please check if another application has locked your source table while Qlik Replicate is performing a full load. If tables get suspended, you can reload these tables only.

If the problem persists, please kindly submit a support ticket.

Regards,
Desmond

[john_wang]

Hello @amit-lamba-ns , @Sreekanth_333 

First of all, Qlik Replicate User Guide claims: 

• All transactions should be manually stopped before starting a Full Load task. Transactions started during the Full Load operation will be cached.

Secondly, please open a support ticket and provide below information if the issue persists:

1- Set SOURCE_UNLOAD to Verbose and recreate the issue, then download the Diagnostics Packages.

2- Check the table's lock and upload the results.

Hope this helps.

John.