Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content
Announcements
Qlik Connect 2025! Join us in Orlando join us for 3 days of immersive learning: REGISTER TODAY

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
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @jchoucq 

The temporary file share location statement is accurate. In my tests of this, I pointed it to a folder next to the actual folder named TEMP, which was then deleted when the upgrade was finished. Since the share information is stored in the repo, restoring it pointed back to the actual share (where all my apps were).

Was the environment where you had the problem with the share the same as the one with the rim nodes? Either way, it sounds like something else went wrong, but this will be difficult to troubleshoot in an article; I'd have to recommend a case, though as you have gotten everything back up and running I am not sure just how much we can assist.

But I will schedule some time to test from August 2021 to November 2022 (all my previous tests were later versions). 

All the best,
Sonja 

jchoucq
Partner - Creator III
Partner - Creator III

Thanks a lot @Sonja_Bauernfeind 

maybe the fact that my Qlik Sense Server in August 2021 was initially in 3.2 could have an impact !

Indeed, as everything is working fine now, i'm not going to create a case, but i really don't understant what happened. We will have to do the same exercice sor others customers, if i notice something, i will let you know.

Have a good day

Johann

Sonja_Bauernfeind
Digital Support
Digital Support

Anytime, @jchoucq 

jchoucq
Partner - Creator III
Partner - Creator III

Hi @Sonja_Bauernfeind,

i've just made another manual upgrade of the bundled Qlik Sense PostgreSQL (From Feb 2022 to Feb 2023), and again, my file share (service cluster) was not changed. To do so, i had to use QlikSenseUtil.exe. 

Moreover, before that i got a fail with QPI (on backup of 9.6 database) even if it was a very simple qlik sense archiecture single node site.

Do you think it is interesting to create a case about the error with QPI ?

Have a good day !

Johann

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @jchoucq Apologies for the delay in my response. It's been a busy two weeks.

If you haven't already, a case to investigate this may be best since that would help us log defects in case you found one.

All the best,
Sonja 

fabdulazeez
Partner - Creator III
Partner - Creator III

Hi @Sonja_Bauernfeind ,

We are planning to upgrade from Feb 2019 to November 2022. Can we use the same steps as mentioned here.

Since the user running Qlik sense services do not have administrator privilege I believe we will not b able to use QPI. 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @fabdulazeez 

With February 2019 you will not be able to use QPI regardless of admin permissions or not. QPI is only supported beginning with the February 2022 release.

The method of manually upgrading PostgresSQL as per this article will work regardless of version (as long as you stick to supported PostgresSQL versions for whatever Qlik Sense release you aim for).

All the best,
Sonja 

 

fabdulazeez
Partner - Creator III
Partner - Creator III

Thanks @Sonja_Bauernfeind .

I have seen if we are targeting Qlik Sense February 2021 and later , we must upgrade to November 2020 first. Is this a mandatory requirement or shall I directly upgrade from Feb 2019 to Nov 2022

fabdulazeez
Partner - Creator III
Partner - Creator III

Since in the above process we are uninstalling and installing the latest version, will it be fine to directly do November 2022 upgrade

@Sonja_Bauernfeind 

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @fabdulazeez 

Here are our recommendations for this scenario:

  • We do not recommend an in-place upgrade, as you would be leaping too many versions 
  • Instead, take a backup of your current database
  • Then do a fresh install of February 2022
  • Then restore the database from your old system to February 2022
  • From here on, you can upgrade to later versions smoothly.

If you need direct assistance with this, I would recommend speaking to our professional services.

All the best,
Sonja 

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