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
@Sebastian_Linser, I just know found out how to describe the issue. A user came up to me with an address such as this. They had it bookmarked to directly open a stream:
https://qs.company.sth.else/hub/stream/fb890468-...-f0c2d34c1416
Using that address, the browser would just show "Opening hub" and the popping circles without any progress.
If instead this address is used, it still works fine. The stream opens as usual.
Hello @steeefan
I recommend posting this either in our relevant Qlik Sense forum or logging a support ticket if necessary. We will not be able to directly assist you with troubleshooting this in this thread.
All the best,
Sonja
There is no need for troubleshooting. I just wanted to follow up to sth. I posted earlier and clarify that it's something completely different than I first thought.
Nothing to see here, please move along 😉
Take care
-Stefan
Hi,
as described, I upgraded the PostgeSQL DB (Nov 2022 version of Qlik Sense) and everything worked correctly.
But now I wanted to install the Feb 2023 version of Qlik Sense, but I encountered a big problem: the upgrade is successful, but the Qlik Sense services don't start. In particular, the Qlik Sense Repository Database service does not start, which after the upgrade is no longer on the Manual, but on Automatic (Delayed Start).
Do I need to switch this service back to Manual?
Thanks.
Robert.
Hello @Roberto_Licciardello
Before the upgrade, have you finalized the steps by removing the Qlik Sense Repository Database service?
See Finalizing the Upgrade/Uninstalling the old Database Service
I may need to recommend a support ticket.
All the best,
Sonja
There seems to be one step missing for a cluster with rim nodes!
After doing the Postgre Update, further Sense updates may run into problems when trying to update to rim nodes.
To prevent this problem, on central node check the file
postgresql.conf in ..\PostgreSQL\12\data\
There is a line at the end of the file with something like
listen_addresses = 'localhost,central.customer.com '
In the case this does not list the rim nodes, you need to edit it and add the rim nodes (or listen_addresses = '*' might also work).
Otherwise the installer doing an update on a rim node may fail, and it might look similar to a firewall issue.
(I identified this fix with the help of https://community.qlik.com/t5/Deployment-Management/Rim-Node-Error-quot-Database-connection-not-reac... )
Please help. $ character in postgres superuser password is causing a crash. details:
Upgrading an existing QRD to PostgreSQL 12.5
all went well, but it crashed in step 11 during backup creation on the postgres superuser password. from the logs i gather that it is because of the & character in my superuser password.
password: s&C@#Sxxxxxxxxx
log message: "'C@#Sxxxxxxxx' is not recognized as an internal or external command"
as you can see it interprets the & as a start of a command.
i cannot simply change the password. please fix or advice.
@Valstar which is a cmd prompt limitation where you have to past this as a command line parameter
you can add an escape character up front like ^& that will make the command prompt not interpret it as a special operation. The other and much easier way is to install it with Password123! for Postgres and right after the conversion you change the password to the one you want to have in the first place
ALTER USER postgres WITH PASSWORD 'Example_Password';
best regards
Sebastian
@john_oll you old postgresql.conf file is copied over into the 12.5 installation, so if the rim nodes already had been whitelisted they will still be whitelisted in the 12.5 installation