Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Nov 13, 2024 9:31:12 AM
May 24, 2022 2:40:49 AM
In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).
For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.
Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.
Index
Video Walkthrough
Video chapters:
The following versions have been tested and verified to work with QPI (1.4.0):
Qlik Sense February 2022 to Qlik Sense November 2023.
If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.
The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.
Using the Qlik PostgreSQL Installer on a patched Qlik Sense version can lead to unexpected results. If you have a patch installed, either:
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Do not use the standard Qlik Sense folders, such as C:\Program Files\Qlik\Sense\Repository\PostgreSQL\ and C:\Programdata\Qlik\Sense\Repository\PostgreSQL\.
Download the installer here.
Qlik PostgreSQL installer Release Notes
The following versions have been tested and verified to work with QPI (1.4.0):
February 2022 to November 2023.
If you are on any version prior to these, upgrade to at least February 2022 before you begin.
Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a 9.6 update is blocked.
Uninstall the old Qlik Sense Repository Database service.
This step is required. Failing to remove the old service will lead the upgrade or patching issues.
Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts.If you do not immediately upgrade:
If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.
Now that your PostgreSQL instance is no longer connected to the Qlik Sense Enterprise on Windows services, all future updates of PostgreSQL are performed independently of Qlik Sense. This allows you to act in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions.
Your PostgreSQL database is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.
See How To Upgrade Standalone PostgreSQL, which documents the upgrade procedure for either a minor version upgrade (example: 14.5 to 14.8) or a major version upgrade (example: 12 to 14). Further information on PostgreSQL upgrades or updates can be obtained from Postgre directly.
The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.
Qlik PostgreSQL installer version 1.3.0 Release Notes
Techspert Talks - Upgrading PostgreSQL Repository Troubleshooting
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades
Hi @Sonja_Bauernfeind ,
Thanks for your message. I logged a case 3 days ago, I couldn't find a solution yet. Do you recommend Uninstalling Feb 2022 and Installing it again (ir order to upgrade Postgre 9.6) or running the QPI? have you tried upgrading Feb 2022 after upgrading PostgreAQL 9.6 using the QPI? did it work for you?
Thanks
Hi Sonja,
Thanks for the response.
We would prefer running an embedded Qliksense Postgres Db. Especially from a support perspective, should any issues arise in future, so that there's no blame game between Qliktech and a Postgres DBA.
Please advise how we can go back to an embedded Db. We were under the impression that the QPI tool upgrades the Db to resolve vulnerability issues picked on Qliksense servers running 9.6 Db version, Where past Qliksense application upgrades failed to update the database.
We would prefer that Qliksense (application & Db) remain in a supported version, as one package.
For our customers that have already used the QPI Tool v1.xx , How do we get them back to a single Qliksense application with an embedded Qlik supported Db.
Kind Regards,
Siven
@pasgalbarra I am unfamiliar with the issue you are facing, so I am reluctant to advise you. Please direct message me the case number, and let me see if I can have someone review it for you.
All the best,
Sonja
Hello @Sonja_Bauernfeind,
We've experienced a situation where the upgrade process ran through successfully, but we've ended up with an empty QSR. We used the latest version of the installer and chose a location on a different drive for the new repository. During the upgrade we saw that the disk was running full. So we made space by deleting non Qlik related files on the disk. The process ran trough and we were able to verify with pgAdmin that the new databases were created. However the new QSR database was completely empty.
We can imagine that if during the upgrade sufficient space cannot be allocated the content of the new QSR will not be created/copied. Can you tell whether a case like this has already been reported or that you have any experience with this?
Best regards,
Luuk
Hello @lkbouman
I cannot find an instance of this having been reported. Could you raise a support ticket so that we can reproduce it and log a defect for the QPI tool on this?
All the best,
Sonja
Thanks for the answer, we will raise ticket.
Hi Sonja,
as one of the last steps of the upgrade it is mentioned to remove the old Qlik Sense Repository Database Service. Should this be done also if we still run August 2022 Version of Qlik but did upgrade the postgres to 14.8 using QPI?
In addition we use a batch job to start the Qlik services. Do we now have to include the new postgres service to our batch job?
Thx in advance
Regards Michael
Hello @mg_gsi_da
(1) Removing unneeded services is a good practice, especially as it would cause issues later down the line when you upgrade your Qlik Sense version and may have forgotten the service is still present. And the moment you have used QPI, you have unbundled/decoupled Postgres from Qlik Sense, meaning the old service is no longer needed.
(2) The new service is simply an unbundled/decoupled version of the previous Qlik Sense Repository Database service; its functionality is still the same otherwise. So if you have been restarting the QSRD service, restarting the unbundled database is also in order.
All the best,
Sonja
FYI, possible bug(s):
In the scenario of
starting with May2022, with already Postgre12.5 (due to original installation 2021-Nov),
then running the Postgre update to 14,
then installing Sense 2022-August, you get a broken server, due to no service dispatcher service installed ALTHOUGH the installation finished without errors!
In the scenario of
starting with May2022, with already Postgre12.5 (due to original installation 2021-Nov),
then running the Postgre update to 14,
then installing Sense 2023-May, you may have weird QMC errors (Failed to load properties. No data found) on the QMC start page.
Solution/workaround:
On May2022, with already Postgre12.5, DON'T use the Postgre Updater, since it is not necessary, you can directly install 2023-May.
We did not contact support about this, due to the working workaround.