Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Nov 13, 2024 7:57:29 AM
Aug 13, 2024 10:23:06 AM
Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch.
All Qlik Replicate versions older than the 2024.5 SP03 release are affected.
Upgrade to Qlik Replicate 2023.11 SP05, or 2024.5 SP03 or later.
Download the formal builds for 2023.11 and 2024.5 here:
Qlik Replicate 2023.11 SP05: https://files.qlik.com/url/qr2023110860sp05 (expires 1/31/2025)
Qlik Replicate 2024.5 SP03 link: https://files.qlik.com/url/qr2024050563sp03 (expires 1/31/2025)
If you have Qlik Enterprise Manager deployed, upgrade this as well. See Qlik Enterprise Manager fails adding a table to a task with SYS-E-HTTPFAIL, no rest handler for url for download links.
The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly.
RECOB-8698
Oracle Database 19c Release Update July 2024 Known Issues
As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.
Hi,
Is upgrading to 2023.11 SP05 a part of the resolution as well or is it only 2024.05 SP03? It is not mentioned explicitly.
Regards,
Mohammed
How can I as a user of Qlik Replicate stay up to date on any potential issues like this?
I was happy to get notified by a previous CSM we worked with about this, but without that, I would not have seen this and want to ensure I get notified for any future updates/issues.
The tags on this would not be sufficient to find specific driver/product issues.
Hi @wmcgee4
Thank you for this feedback. We are looking into ways to improve communications on high impact issues such as this. One think you can do now though is subscribe to our product forums: Support Updates | Qlik Community
That way when a new article is published, you'll get an email notification.
I hope this helps.
Thanks,
Dana
Hi,
Thanks for your answer! I know it's not likely since it will be out of support soon but, will the fix for QR November 2022 be out as well?
Thanks,
Mohammed
Hi @MoeyE
Due to the age of version 2022.11 and the complexity of not just patching this issue - but needing to include all other fixes back to that version - there are no plans at this time to patch 2022.11.
Thanks,
Dana
Hi,
Is there an expected date when the early builds mentioned in the article, especially Replicate May 2024 SP03, will become generally available releases published on the Product Downloads page (https://community.qlik.com/t5/Download-Qlik-Products/tkb-p/Downloads)?
Regards,
Nak
Hi is there a temporary workaround outside of just upgrading to the latest release. We have recently encountered this issue in Production and will need to test in our lower environments before upgrading Prod. I have attempted to use the Advanced Options start from timestamp but that will work for a few hours and then we run into the error again. I am looking for a way to not have to upgrade until we can do testing in our lower environments first.
HI @jgalberth ,
Oracle Database 21c and later versions only support the multitenant container database architecture. However, Oracle Database 19c and earlier versions (down to 12c) support both multitenant and non-multitenant setups. If you're running Oracle 19c in a non-multitenant configuration, LogMiner may still be an option.
To check if your database is using the container architecture, run the following query:
SQL> SELECT CDB FROM V$DATABASE;
If the result is NO
, your database is non-multitenant, and you can set up the Oracle source endpoint to use LogMiner as follows:
hope this helps.
John.
Hi Support,
I'd just like to know if the patched version of Replicate (v2023.11.0.714) will still be able to process data from an unpatched version of Oracle (19.23). Or is it only able to read data from Oracle instances which have the 19.24 patch?
Regards,
Nak