Qlik Replicate Encouter a Critical issues with Compressed tables after Oracle July 2024 Patch

[wali]

I have Qlik Replicate version  May 2023 (2023.5.0.771). 

I see the early builds version 2023.11 and 2024. Which one should I apply? 

Please advise. 

[john_wang]

Hello @wali ,

Thanks for the update.

>> the Oracle DBA confirmed the Oracle instance is: 19.24, which means the July 2024 patch was installed.

Would you please run the SQL and share the result with me?

SELECT * FROM v$version;

>> Can someone advise what version of Qlik Replicate and Manager I need to upgrade to resolve the issue.

Please upgrade to 2024.5 SP03, or 2023.11 SP05, both will be formal released recently. Will keep you posted.

Regards,

John.

[Dana_Baldwin]

Hi @wali 

The needed patch is only available in version 2023.11 and 2024.5 per the link above. Please ensure your server operating system, source/target versions and driver versions are supported before you upgrade.

See here for more details on these items: Qlik Replicate Upgrade Best Practices - Qlik Community - 1729651

You can check the release notes here: Release Notes | Qlik Community

And User Guide here (change the version at the top left for the version you are installing): Start | Qlik Replicate Help

Supported server, endpoint and drivers are documented here.

Thanks,

Dana

[wali]

@Dana_Baldwin @john_wang @kng @SushilKumar @Shashi.Holla@qlik.com

Thanks to Shashi's help, I have downloaded Qlik Replicate version: 2023.5.0.1055. while there is no compatible Qlik Manager thus, have to update each task by adding "supportNewV19CompressionFeatures" to each task in order to resolve the issue.

Please let me know when the GA version is available for Replicate and Manager.

Thank you

[john_wang]

Thank you for the update @wali , we will keep you posted on the GA version progress.

[john_wang · Accepted solution]

Hello @wali ,

Both 2023.11 SP05 and 2024.5 SP03 patches are formal released. Please check the articile after installing Oracle July 2024 patch to download them.

Thanks,

John.