How to manually upgrade the bundled Qlik Sense PostgreSQL version

[Bastien_Laugiero]

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:

• Move Qlik Sense database to standalone PostgresSQL database in which case you will have control of which PostgreSQL version is deployed as long as it is supported by the system requirements
• Continue to use the bundled PostgreSQL with version 12.5 (May 2021 to May 2023) or 14.8 (August 2023 and later). Instructions below.

Content:

• Step 1: Upgrading your Qlik Sense site
• Step 2: Backing up your Qlik Sense site
• Step 3: Uninstall Qlik Sense on the central node
• Step 4: Install an identical version of Qlik Sense Enterprise on Windows on the central node
• Step 5: Restoring your Qlik Sense site

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

[Sonja_Bauernfeind]

Hello @TusharDev_Qlik 

If you have IIS running on port 80 at the same time as Sense, you may run into issues further down the line whenever Sense requires the use of the port. We recommend not having IIS running on the same machine.

All the best,
Sonja 

[PabloLabbeImaps]

Just upgraded customer site from May/21 SR2 to August/22 SR3 and the procedure worked without errors. 😎

[PabloLabbeImaps]

By the way, version August/22 requires PostgreSQL v12 and 9.6 is not supported any more. This requirement is mandatory starting  version August /22.

[Skage]

Lately the 9.6-12.5-upgrade is failing to retain the license.

I've performed way more than a handful of these upgrades and all but the two latest has not been licensed when the upgrade is complete.

I've followed the instructions carefully every time. The two failing upgrades was performed when November 2022 was the latest. Coincident?

Wouldn't the renaming of the programdata & program files folders result in loss of logs?

I have no clear recollection of doing that in the previous upgrades, but that might just me my memory failing...

The QPI-tool might be a candidate if the end result would be identical to a new install of the latest Sense version. Having a new service not amongst the other Qlik-services has turned out be be confusing to other administrators.

With quite a lot of customer environments still to be moved from 9.6 to 12.5 and probably an even newer version in the not distant future the need for a tool, or an easy to follow instruction, that does this properly and reliably is sorely needed.

It can't be a surprise to Qlik that the embedded pg-service would need to be upgraded to a supported version. Making that transparent and secure should be a part of the regular installer with an option to delay the 12.5-switch.

Did I miss a required step in my two latest attempts?

The Dispatchservice WAS started before QRS.

What should I do differently in my next attempt?

br

/lars

[Sonja_Bauernfeind]

Hello @Skage 

Thank you for reporting this. Let me give this a test to see if I can reproduce this. We may require a case, but I will let you know.

All the best,
Sonja

[Sonja_Bauernfeind]

Hello again @Skage 

Can you confirm what version of Qlik Sense you were upgrading Postgre for and what version of Postgre you moved to? 

Edit: And what license type are you using? SLK or license number?

[Skage]

Hi @Sonja_Bauernfeind 

Both environments was upgraded to Nov 2022 before attempting the manual pg-upgrade.

I'm certain that one of the customers are using SLK and awaiting answer on the other one... it was a while ago and I can't recall what type of license it was.

I've asked people who know but they have note responded yet.

/lars

[Skage]

Hi again @Sonja_Bauernfeind 

I got an answer about the other customer and that is also a SLK.

So both attempts were November 2022 and SLK.

/lars

[Sonja_Bauernfeind]

Hello @Skage 

I finished my testing and have successfully upgraded Postgre manually using these steps + November 2022. The license was not cleared, and I was not prompted for it after the restore.

Here are my steps:

1. Upgraded a May 2022 setup with 9.6 to November 2022, ignoring the "hey this is not supported" warning.
2. Backed up all databases (Backing up a Qlik Sense site) and the certificates
3. Uninstalled Qlik Sense (had a coffee during)
4. Renamed the C:\Programdata\Qlik folder and the C:\Program Files\Qlik folder
5. Installed November 2022 (services not started) and pointed at a different share
6. Started only the Database service
7. Restored my databases (I forgot the certs, but since I was testing on a single node, that wasn't an issue)
8. Started all the services (chanting "please work, please work")
9. Launched the QMC and found everything where it was supposed to be (license there, apps there, etc)

If you keep seeing the problem with the license vanishing as you follow these steps, maybe a case with Support may be in order.

All the best,
Sonja 

[jchoucq]

Hi,

just for information, i think the sentence below is not correct

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

Even after restoring QSR database, my file share (service cluster) was not changed. To do so, i had to use QlikSenseUtil.exe. Maybe it is a better option to point to the same share location ?

After migrating from QS August 2021 to QS November 2022, and doing a manually upgrade of the bundled Qlik Sense PostgreSQL, i had a problem of communication with my rim nodes, which were all offline ; i can't explain why, it was impossible to redistribute certificate ... I had to uninstall / reinstall all my rim nodes to have a fully operational platform.

Do you have a an idea about a possible cause ?

Thanks again for quality of your articles !!!

Have a good day

Johann