Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Write Table now available in Qlik Cloud Analytics: Read Blog
cancel
Showing results for 
Search instead for 
Did you mean: 
desmondchew
Creator III
Creator III

An existing task failed with with error A compressed row cannot be parsed for table

We have an existing tasks that load table from Oracle 11g into MySQL 8.0.30. The task failed suddenly with error a compressed row cannot be parsed.

00008856: 2022-11-21T10:29:59:489101 [SORTER ]I: Transaction consistency reached (sorter_transaction.c:313)
00008708: 2022-11-21T10:29:59:489101 [TASK_MANAGER ]I: Starting replication now (replicationtask.c:3299)
00008856: 2022-11-21T10:30:00:660949 [ASSERTION ]W: A compressed row cannot be parsed for table 'SCHEMA.TABLE, context '00000000.00000000.00000000.0000.00.0000:0.0.0' (oradcdc_parse.c:1895)

Labels (1)
4 Replies
Dana_Baldwin
Support
Support

Hi @desmondchew 

What version of Replicate are you running?

Are you using our log reader or LogMiner?

What type of compression is in use on the source table?

Here is our documented limitations on compression for Oracle source: Supported compression methods ‒ Qlik Replicate

Thanks,

Dana

Bill_Steinagle
Support
Support

Hi,

Thank you for the post to the QDI Forums. The issue is due to the MySQL ODBC driver as you have the 8.0.30 version installed. As per the Replicate User guide you will need to install the 8.0.23 version of the MySQL ODBC driver to correct the condition. As Dana noted if you run into issue after installing the required ODBC Version of the driver a case with the Support Team is next step.

https://help.qlik.com/en-US/replicate/May2022/Content/Replicate/Main/Google%20Cloud%20MySQL/google_p...

Thanks!

Bill

desmondchew
Creator III
Creator III
Author

Hi,

We are definitely on ODBC version 8.0.23. The version that you see in the log files comes from the target database which is running on 8.0.30. Please see attached showing the installed ODBC version in replicate server.

 

 

Bill_Steinagle
Support
Support

Hi,

Thank you for the reply. Ok so the issue appears to be on the Source side reading from the Redo Log. I would suggest open a case since you confirmed the MySQL ODBC driver is correct.

Thanks!

Bill