Qlik Community

Knowledge

Search or browse our knowledge base to find answers to your questions ranging from account questions to troubleshooting error messages. The content is curated and updated by our global Support team

Qlik Sense May 2021 - Upgrade bundled PostgreSQL to 12.5 version

Bastien_Laugiero

Qlik Sense May 2021 - Upgrade bundled PostgreSQL to 12.5 version

Starting at Qlik Sense Enterprise on Windows May 2021, the bundled PostgreSQL has been upgraded to version 12.5

However, PostgreSQL 12.5 will only be deployed during a fresh installation of Qlik Sense Enterprise on Windows May 2021. This means that, if you are upgrading to 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:

 

Environment

  • Qlik Sense Enterprise on Windows May 2021

 

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 May 2021 following the steps and recommendations provided on this link.

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 Qlik Sense Enterprise on Windows May 2021, however, the bundled PostgreSQL is still on version 9.6.

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:

  • Check the box Remove Qlik Sense demo apps, certificates and data folders.
  • Have all rim nodes stopped. 

 

Step 4: Install Qlik Sense Enterprise on Windows May 2021 on the central node

Now that Qlik Sense Enterprise on Windows May 2021 is uninstalled on the central node, you will reinstall it as a result will deploy a bundled PostgreSQL 12.5.  Instructions available here.

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 May 2021 deployed on your central node with PostgreSQL 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. 

 

Labels (3)
Comments
RaviGinqo
Partner
Partner

HI Bastien,

 

Thanks for the article, Couple of questions though, Do RIM nodes needs to be re-installed after Central node installation in Step 4&5 ? Are there any issues if PostgreSQL is not upgraded to latest version and kept to 9.6 ?

Any other known issue with May 2021 release or article (maintaining those issue) I can watch out for?

 

Thanks & Regards
Ravi

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @RaviGinqo 

 

 

-Sonja

RaviGinqo
Partner
Partner

Thank you @Sonja_Bauernfeind

pablodelcerro
Partner
Partner

Hi There,

We have a QS cluster with a standalone Postgresql and will like to get it back to the bundle version so that we dont have to worry about Postgresql updates, and also to get it to Postgresql 12.5 version.

Will a clean new install and a restore DB procedure work or we need to worry about anything else?

What about rim nodes? Need to do anything there?

Thanks!

Pablo

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @pablodelcerro 

Before we get into details on the procedure: Standalone gives you more flexibility as you can control which version of Postgres is deployed (as long as it is a supported version in Qlik Sense). This is especially relevant for security-related defects in Postgres.
 
If you still want to go ahead with the migration though, then we can recommend these two steps:

  1. Clean new install and a restore DB (on the same version of Postgres)
  2. Upgrade to PG 12.5 following this article
 
A backup is of course needed so that you can revert back if needed. 
 
For the Rim nodes: You shouldn't have to take any actions if you restore the certificate as part of the central node re-install. 
 
pablodelcerro
Partner
Partner
Hi Sonja

Due to your comments, we have upgraded postgresql to 12.8 and have left it
as an standalone db.

But then we found out some post regarding problems with centralized logging
and postgresql 12.

Should we disable it? Something else we should do?

Before the db upgrade we have done qs upgrade to may 2021

Thanks for your help
Pablo

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @pablodelcerro 

Apologies for the delay!

Disabling Centralised Logging if you do not plan to use it is a good idea. We are also deprecating this feature: Deprecation of Centralized Logging in Qlik Sense Enterprise on Windows.

pablodelcerro
Partner
Partner
Thanks! We will do so!

Quick question... shall we remove the Qlik Logging Service then? How?

In the meanwhile, we can disable it right?

Thanks!
Pablo
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @pablodelcerro 

This should help: How To Enable/Disable Centralized Logging Mode.

And then you can just disable the service. No need to uninstall it. 

pablodelcerro
Partner
Partner
Thanks Sonja!
Version history
Last update:
‎2021-08-19 02:30 AM
Updated by: