Qlik replicate is trying to access temporary hash tables in Sybase and is failing as those temp tables are dropped

[akaradhya]

Hi Team, 

I am working with a customer where we are replicating data from Sybase to Sybase. During this process, we are noticing a peculiar behaviour. Replicate is trying to access the hash tables generated on the Sybase end. These temp tables are created and are dropped as soon as the user session is terminated. 

Since replicate is trying to access them after they are being dropped, the task is failing with the below error message. 

"Failed to execute insert statement, stream position is 029ff52c:0002:029ff52f:0008
RetCode: SQL_ERROR  SqlState: 42000 NativeError: 208 Message: [SAP][ASE ODBC Driver][Adaptive Server Enterprise]#palp_def_wil not found. Specify owner.objectname or use sp_help to check whether the object exists (sp_help may produce lots of output)"

Reaching out to the community to see if there is a workaround to avoid Replicate from accessing the internal sybase hash tables. Also attaching the task logs with elevated logging. 

Thanks.

[john_wang]

Hello @akaradhya ,

Thanks for reaching out to Qlik Community!

In most RDBMS platforms, changes to temporary tables are not recorded in the transaction log (this applies to Oracle, SQL Server, MySQL, Sybase ASE, and others). Therefore, temporary tables should not be included in the monitor list.

Could you please confirm whether any temporary tables were added to the task? Especially if the table were included by "Table Selection Patterns". You may get the Full Tables List by:

 If so, stop the task, exclude those tables from the monitor list, and then resume the task.

Hope this helps.

John.

[akaradhya]

Thanks for your response @john_wang. We have not selected any temp tables as part of the replication. As per the logs, the table that replicate is trying to access is not added to the table list at all. 

[john_wang]

Hello @akaradhya ,

Thanks for the update.

Please set SOURCE_CAPTURE, SOURCE_UNLOAD, TARGET_APPLY, and TARGET_LOAD to Verbose, then reproduce the issue and attach the Diagnostics Package to the support case.

Also, please remember to decrypt the verbose task log files before uploading them. Our support team will be glad to assist you further once we have this information.

Thanks,

John.