Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jan 22, 2024 8:18:38 AM
Jul 9, 2021 2:31:59 AM
Upgrading Qlik Sense Enterprise on Windows does not automatically upgrade the bundled PostgreSQL version. New versions of PostgreSQL are only deployed during a new install. This means upgrading to, for example, Qlik Sense Enterprise on Windows May 2021, PostgreSQL will remain on 9.6.
For many organizations, running on the latest supported PostgreSQL version is a security requirement. To achieve this:
Content:
The information in this article is provided as-is and to be used at your own discretion. Depending on the tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
This process requires a full reinstallation of the product. Despite the fact that a backup is being taken as part of the process, it is highly recommended to have a second backup plan in place such as a Virtual Machine snapshot and/or a Server Backup.
It is highly recommended to test this process in a test environment to get familiar with it.
The first step is to upgrade your environment to Qlik Sense Enterprise on Windows. This article was originally written for May 2021, but can be applied to any version. Follow the required steps and recommendations for an upgrade for your version. Example: August 2023.
Once the upgrade is done make sure your Qlik Sense site is completely operational.
At this point, you have an operational Qlik Sense site running on your new version of Qlik Sense Enterprise on Windows. However, the bundled PostgreSQL is still on version 9.6 or 12.5, depending on the originally installed version.
The next step will be to backup your entire Qlik Sense site following these instructions (including the certificates) . The backup is essential as it will need to be restored later on.
You will now need to uninstall Qlik Sense from the central node following these instructions.
During the uninstall:
Now that Qlik Sense Enterprise on Windows is uninstalled on the central node, you will reinstall it as a result will deploy either a bundled PostgreSQL 14.8 (August 2023 and later) or a bundled PostgreSQL 12.5 (May 2021 to May 2023). Instructions available here (choose your version).
Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.
You now have a clean Qlik Sense Enterprise on Windows deployed on your central node with PostgreSQL 14.8 or 12.5. You now need to restore your environment to retrieve all your configurations and apps.
Please follow the Restoring a Qlik Sense site (including the certificates).
Note: While restoring the database backup you will most likely receive the following error which can be ignored. This error is caused by the version discrepancies between the pg_dump that made the dump file and the pg_restore that's restoring it - in example files coming from PostgreSQL version 9.6 vs files coming from PostgreSQL version 12.5. QSR backup taken and restored with the same version of PostgreSQL will not produce that error.
pg_restore: while PROCESSING TOC:
pg_restore: from TOC entry 3; 2615 2200 SCHEMA public postgres
pg_restore: error: could not execute query: ERROR: schema "public" already exists
Command was: CREATE SCHEMA public;
pg_restore: warning: errors ignored on restore: 1
Once the environment is restored, you should be able to start your central node and rim nodes successfully.
Qlik Sense Enterprise on Windows May 2021 and later
Good day support,
We want to update our version of May 2023 and PostgreSQL 12.5 for May 2024 and PostgreSQL 14.8
Today an attempt to update your instructions
- made a backup database - successfully
- Updated PostgreSQL on the 14th version - Successfully
- deleted the old version of the platform - successfully
- renamed the old Qlik folder
- installed the platform May 2024 (launched with "Run as Administrator") - successfully
- installed patch 3 - Successfully
- Restoration of the database - error "Not found QSR base", run QRD
Tell me, what did it wrong?
Additional information:
- I launch "Run as administrator"
- MS Windows Server 2016 Standard
- installed NET. Framework 4.8