Skip to main content

How to manually upgrade the bundled Qlik Sense PostgreSQL version

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Bastien_Laugiero

How to manually upgrade the bundled Qlik Sense PostgreSQL version

Last Update:

Jan 22, 2024 8:18:38 AM

Updated By:

Sonja_Bauernfeind

Created date:

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.

 

Step 1: Upgrading your Qlik Sense site

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.

 

Step 2: Backing up your Qlik Sense site

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.

 

Step 3: Uninstall Qlik Sense on the central node

You will now need to uninstall Qlik Sense from the central node following these instructions.

During the uninstall:

  • Have all rim nodes stopped.
  • Don't check the box Remove Qlik Sense demo apps, certificates, and data folders.
  • After uninstall and before reinstall rename C:\programdata\qlik to C:\programdata\qlik.old and rename C:\program files\qlik to C:\program files\qlik.old (if you changed it on another drive adjust accordingly)

 

Step 4: Install an identical version of Qlik Sense Enterprise on Windows on the central node

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).

  • select the same host name and database settings as before
  • The file share can point at a temporary one since you will take the original one again after restoring the QSR database in step 5.
Do not check the box Start theQlik Senseservices when the setup is complete at the end of the installer.

 

Step 5: Restoring your Qlik Sense site

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.

 

Environment

Qlik Sense Enterprise on Windows May 2021 and later

 

Labels (2)
Comments
fabdulazeez
Partner - Creator III
Partner - Creator III

Will that be possible to restore the back up from a different version of Qlik sense?

Sonja_Bauernfeind
Digital Support
Digital Support

@fabdulazeez Correct.

sri_c003
Partner - Creator II
Partner - Creator II

@Benoit_C 
Thank you for coming back so quickly. I looked into the document at https://community.qlik.com/t5/Official-Support-Articles/How-to-manually-upgrade-the-bundled-Qlik-Sen...

But the issue is the number of manual steps needed. We have a few hundred deployments of Qlik and doing this manually on all these is simply not a viable option.

We are looking a simpler process where the steps to upgrade Postgres can be automated via a script, just like how we currently deploy/upgrade Qlik.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @sri_c003 

Please log an idea in our ideation platform explaining your need for the Qlik installer packages to upgrade PostgreSQL so that the appropriate team (product management) can review the request and provide you with the most accurate response.

All the best,
Sonja 

aldo-tgh
Partner - Creator II
Partner - Creator II

Hi @Sonja_Bauernfeind ,
I have updated a server to Qlik Sense May 2023, then decouple and upgraded PostgreSQL to version 14.8 using the Qlik tool for this purpose.

Qlik Sense May 2023 is running ok with the "old" Repository Database service stopped and set to manual. There is instead a new PostgreSQL service running properly.

I am trying to upgrade to Qlik Sense August 2023.
I have tried several times but the installer keep running without any error messages, still running for almost 24 hours now!

I have tried several times but always getting the same irresponsive status.

Do I miss something during installation?

Windows Server 2019 standard,
no server resource issues,
QS installer running as administrator under a full admin user on the machine.

Aldo.

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @aldo-tgh 

After unbundling the PostgreSQL database, the old database must be removed. See Step 16 in the Upgrade and Unbundle instructions. Before the old database is removed, we cannot guarantee any upgrades to function correctly.

If you still see issues after uninstalling the PostgreSQL database, I would recommend posting about the issue directly in the Qlik Sense Deployment and Management forum, including the error message which you are seeing.

All the best,
Sonja 

aldo-tgh
Partner - Creator II
Partner - Creator II

Thanks, that solved the issue.

Sonja_Bauernfeind
Digital Support
Digital Support

@aldo-tgh Glad to hear!

Have a good week!

All the best,
Sonja 

pasgalbarra
Partner - Creator
Partner - Creator

Hi @Sonja_Bauernfeind ,

 

What is the best way to upgrade Qlik Sense Feb 2023 with PostgreSQL 12.5 to Aug 2023 and PostgreSQL 14.8 not using the QPI? Should I upgrade to AUG 2023 ignoring the postgresql message and then uninstall and Install Qlik Sense August 2023?

 

Thanks

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @pasgalbarra 

The method described here is the correct one if you wish to remain on a bundled PostgreSQL setup rather than use QPI to upgrade it. I do want to mention though that using QPI and upgrading + debundling your repository database will give you the choice and freedom to upgrade PostgreSQL seamlessly afterwards whenever you need to. It is the main benefit gained from moving away from a bundled repository database.

Regardless though, yes! This is the correct method. See System Requirements , where the Postgresql version is still listed as not recommended with a note to upgrade.

All the best,
Sonja 

 

Version history
Last update:
‎2024-01-22 08:18 AM
Updated by: