Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE

Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer

100% helpful (4/4)
cancel
Showing results for 
Search instead for 
Did you mean: 
Mario_Petre
Support
Support

Upgrading and unbundling the Qlik Sense Repository Database using the Qlik PostgreSQL Installer

Last Update:

Dec 20, 2023 6:28:09 AM

Updated By:

Sonja_Bauernfeind

Created date:

May 23, 2022 11:40:49 PM

In this article, we walk you through the requirements and process of how to upgrade and unbundle an existing Qlik Sense Repository Database (see supported scenarios) as well as how to install a brand new Repository based on PostgreSQL. We will use the Qlik PostgreSQL Installer (QPI).

For a manual method, see How to manually upgrade the bundled Qlik Sense PostgreSQL version to 12.5 version.

Using the Qlik Postgres Installer not only upgrades PostgreSQL; it also unbundles PostgreSQL from your Qlik Sense Enterprise on Windows install. This allows for direct control of your PostgreSQL instance and facilitates maintenance without a dependency on Qlik Sense. Further Database upgrades can then be performed independently and in accordance with your corporate security policy when needed, as long as you remain within the supported PostgreSQL versions. See How To Upgrade Standalone PostgreSQL.

Index

 

Supported Scenarios

Upgrades

The following versions have been tested and verified to work with QPI (1.4.0): 

Qlik Sense February 2022 to Qlik Sense November 2023.

If you are on a Qlik Sense version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade. From Qlik Sense August 2023 a upgrade with a 9.6 database is blocked.

New installs

The Qlik PostgreSQL Installer supports installing a new standalone PostgreSQL database with the configurations required for connecting to a Qlik Sense server. This allows setting up a new environment or migrating an existing database to a separate host.

 

Requirements

  • Review the QPI Release Notes before you continue
  • The PostgreSQL Installer can only upgrade bundled PostgreSQL database listening on the default port 4432.
  • The user who runs the installer must be an administrator.
  • The backup destination must have sufficient free disk space to dump the existing database  
  • The backup destination must not be a network path or virtual storage folder. It is recommended the backup is stored on the main drive. 
  • There will be downtime during this operation, please plan accordingly
  • If upgrading to PostgreSQL 14 and later, the Windows OS must be at least Server 2016

Known limitations

  • Cannot migrate a 14.8 embedded database to a standalone
  • Using QPI to upgrade a standalone database or a database previously unbundled with QPI is not supported.
  • The installer itself does not provide an automatic rollback feature.

 

Installing a new Qlik Sense Repository Database using PostgreSQL

  1. Run the Qlik PostgreSQL Installer as an administrator 

  2. Click on Install 

  3. Accept the Qlik Customer Agreement 

  4. Set your Local database settings and click Next. You will use these details to connect other nodes to the same cluster. 

  5. Set your Database superuser password and click Next

  6. Set the database installation folder, standard: C:\Program Files\PostgreSQL\14

  7. Set the database data folder, standard: C:\Program Files\PostgreSQL\14\data

  8. Review your settings and click Install, then click Finish

  9. Start installing Qlik Sense Enterprise Client Managed. Choose Join Cluster option.

    The Qlik PostgreSQL Installer has already seeded the databases for you and has created the users and permissions. No further configuration is needed.


  10. The tool will display information on the actions being performed. Once installation is finished, you can close the installer.  

    If you are migrating your existing databases to a new host, please remember to reconfigure your nodes to connect to the correct host. How to configure Qlik Sense to use a dedicated PostgreSQL database 

 

Qlik PostgreSQL Installer - Download Link

download.png

Download the installer here.

Qlik PostgreSQL installer Release Notes

 

 

Upgrading an existing Qlik Sense Repository Database

The following versions have been tested and verified to work with QPI (1.4.0): 

February 2022 to November 2023.

If you are on any version prior to these, upgrade to at least February 2022 before you begin.  

Qlik Sense November 2022 and later do not support 9.6, and a warning will be displayed during the upgrade.  From Qlik Sense August 2023 a 9.6 update is blocked.

 

The Upgrade

  1. Stop all services on rim nodes 

  2. On your Central Node,stop all services except the Qlik Sense Repository Database 

    qlik sense repository database service running.png

  3. Run the Qlik PostgreSQL Installer. An existing Database will be detected. 

    Upgrade PostgreSQL with QPI.png

  4. Highlight the database and click Upgrade 
  5. Read and confirm the (a) Installer Instructions as well as the Qlik Customer Agreement, then click (bNext.

    QPI Customer Agreement.png

  6. Provide your existingDatabase superuser password and click Next.

  7. Define your Database backup path and click Next.

    Location of database backup folder.png

  8. Define your Install Location (default is prefilled) and click Next.

    Location of database installation folder.png

  9. Define your database data path (default is prefilled) and click Next.

    Location of database data folder.png
     
  10. Review all properties and click Upgrade.

    The review screen lists the settings which will be migrated. No manual changes are required post-upgrade.

    Finalise PostgreSQL upgrade with QPI.png

  11. The upgrade is completed. Click Close.
     
  12. Open the Windows Services Console and locate the Qlik Sense Enterprise on Windows services.

    You will find that the Qlik Sense Repository Database service has been set to manual. Do not change the startup method. 

    old service set to manual.png

    You will also find a new postgresql-x64-14 service. Do not rename this service. 

    postgresql-x64-14.png

     

  13. Start all services except the Qlik Sense Repository Database service. 

  14. Start all services on your rim nodes.

  15. Validate that all services and nodes are operating as expected. The original database folder in C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated

     

  16. Uninstall the old Qlik Sense Repository Database service.

    This step is required. Failing to remove the old service will lead the upgrade or patching issues.
    1. Open a Windows File Explorer and browse to C:\ProgramData\Package Cache

    2. From there, search for the appropriate msi file.

      search package.png

      If you were running 9.6 before the upgrade, search PostgreSQL.msi

      If you were running 12.5 before the upgrade, search PostgreSQL125.msi

    3. The msi will be revealed.

    4. Right-click the msi file and select uninstall from the menu.

      uninstall postgresql.png


  17. Re-install the PostgreSQL binaries. This step is optional if Qlik Sense is immediately upgraded following the use of QPI. The Sense upgrade will install the correct binaries automatically. 
    Failing to reinstall the binaries will lead to errors when executing any number of service configuration scripts. 
    1. Open a Windows Command prompt as administrator

    2. Navigate to the location of the previously located .msi file

      Example: 

      cd C:\ProgramData\Package Cache\{GUID}

    3. Run the following command, replacing PostgreSQL125.msi with the correct .msi depending on your previous version used.

      Qlik Sense August 2023 and later: PostgreSQL14.msi
      Qlik Sense February 2022 to May 2023: PostgreSQL125.msi

      msiexec.exe /qb /i "PostgreSQL125.msi" SKIPINSTALLDBSERVICE="1" INSTALLDIR="C:\Program Files\Qlik\Sense"

      This will re-install the binaries without installing a database. If you installed with a custom directory adjust the INSTALLDIR parameter accordingly. E.g. you installed in D:\qlik\sense then the parameter would be INSTALLDIR="D:\QLIK\Sense"

 

If the upgrade was unsuccessful and you are missing data in the Qlik Management Console or elsewhere, contact Qlik Support.  

Compatibility with PostgreSQL installers

This version of the upgrade tool is fully compatible with the official PostgreSQL installers from https://www.enterprisedb.com/downloads/postgres-postgresql-downloads.

If you have previously used the Qlik Postgres Installer (version 1.2.1 or earlier), you can simply install the latest PostgreSQL version (within your major release).

Example: You have used the old QPI to upgrade to 12.5. You can now easily upgrade to a later version in the same major release, such as 12.15.

 

Troubleshooting and FAQ

  1. If the installation crashes, the server reboots unexpectedly during this process, or there is a power outage, the new database may not be in a serviceable state. Installation/upgrade logs are available in the location of your temporary files, for example:

    C:\Users\Username\AppData\Local\Temp\2

    A backup of the original database contents is available in your chosen location, or by default in:

    C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\backup\X.X

    The original database data folder has been renamed to:

    C:\ProgramData\Qlik\Sense\Repository\PostgreSQL\X.X_deprecated

  2. Upgrading Qlik Sense after upgrading PostgreSQL with the QPI tool fails with:

    This version of Qlik Sense requires a 'SenseServices' database for multi cloud capabilities. Ensure that you have created a 'SenseService' database in your cluster before upgrading. For more information see Installing and configuring PostgreSQL.

    See Qlik Sense Upgrade fails with: This version of Qlik Sense requires a _ database for _.

    To resolve this, start the postgresql-x64-XX service.

 

Video Walkthrough

 

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support. The video in this article was recorded in a earlier version of QPI, some screens might differ a little bit.

 

Related Content

Qlik PostgreSQL installer version 1.3.0 Release Notes  
Techspert Talks - Upgrading Qlik Sense Repository Service
Backup and Restore Qlik Sense Enterprise documentation
Migrating Like a Boss
Optimizing Performance for Qlik Sense Enterprise
Qlik Sense Enterprise on Windows: How To Upgrade Standalone PostgreSQL
How-to reset forgotten PostgreSQL password in Qlik Sense
How to configure Qlik Sense to use a dedicated PostgreSQL database
Troubleshooting Qlik Sense Upgrades 

Labels (1)
Comments
pasgalbarra
Partner - Creator
Partner - Creator

Hi @Sonja_Bauernfeind ,

Thanks for your message. I logged a case 3 days ago, I couldn't find a solution yet. Do you recommend Uninstalling Feb 2022 and Installing it again (ir order to upgrade Postgre 9.6) or running the QPI?  have you tried upgrading Feb 2022 after upgrading PostgreAQL 9.6 using the QPI? did it work for you?

 

Thanks

SivenM2020
Partner - Contributor III
Partner - Contributor III

Hi Sonja,

Thanks for the response.

We would prefer running an embedded Qliksense Postgres Db. Especially from a support perspective, should any issues arise in future, so that there's no blame game between Qliktech and a Postgres DBA.

Please advise how we can go back to an embedded Db. We were under the impression that the QPI tool upgrades the Db to resolve vulnerability issues picked on Qliksense servers running 9.6 Db version, Where past Qliksense application upgrades failed to update the database.

We would prefer that Qliksense (application  & Db) remain in a supported version, as one package.

For our customers that have already used the QPI Tool v1.xx , How do we get them back to a single Qliksense application with an embedded Qlik supported Db.

Kind Regards,

Siven

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @SivenM2020 

I'll look into this question for you.

All the best,
Sonja 

Sonja_Bauernfeind
Digital Support
Digital Support

@pasgalbarra I am unfamiliar with the issue you are facing, so I am reluctant to advise you. Please direct message me the case number, and let me see if I can have someone review it for you.

All the best,
Sonja 

lkbouman
Partner - Contributor II
Partner - Contributor II

Hello @Sonja_Bauernfeind,

We've experienced a situation where the upgrade process ran through successfully, but we've ended up with an empty QSR. We used the latest version of the installer and chose a location on a different drive for the new repository. During the upgrade we saw that the disk was running full. So we made space by deleting non Qlik related files on the disk. The process ran trough and we were able to verify with pgAdmin that the new databases were created. However the new QSR database was completely empty.

We can imagine that if during the upgrade sufficient space cannot be allocated the content of the new QSR will not be created/copied. Can you tell whether a case like this has already been reported or that you have any experience with this?

Best regards,

Luuk

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @lkbouman 

I cannot find an instance of this having been reported. Could you raise a support ticket so that we can reproduce it and log a defect for the QPI tool on this?

All the best,
Sonja 

lkbouman
Partner - Contributor II
Partner - Contributor II

Thanks for the answer, we will raise ticket.

mg_gsi_da
Contributor III
Contributor III

Hi Sonja,

as one of the last steps of the upgrade it is mentioned to remove the old Qlik Sense Repository Database Service. Should this be done also if we still run August 2022 Version of Qlik but did upgrade the postgres to 14.8 using QPI?

In addition we use a batch job to start the Qlik services. Do we now have to include the new postgres service to our batch job?

 

Thx in advance

Regards Michael

Sonja_Bauernfeind
Digital Support
Digital Support

Hello @mg_gsi_da 

(1) Removing unneeded services is a good practice, especially as it would cause issues later down the line when you upgrade your Qlik Sense version and may have forgotten the service is still present. And the moment you have used QPI, you have unbundled/decoupled Postgres from Qlik Sense, meaning the old service is no longer needed.

(2) The new service is simply an unbundled/decoupled version of the previous Qlik Sense Repository Database service; its functionality is still the same otherwise. So if you have been restarting the QSRD service, restarting the unbundled database is also in order.

All the best,
Sonja 

 

john_oll
Partner - Creator
Partner - Creator

FYI, possible bug(s):
In the scenario of
starting with May2022, with already Postgre12.5 (due to original installation 2021-Nov),
then running the Postgre update to 14,
then installing Sense 2022-August, you get a broken server, due to no service dispatcher service installed ALTHOUGH the installation finished without errors!

In the scenario of
starting with May2022, with already Postgre12.5 (due to original installation 2021-Nov),
then running the Postgre update to 14,
then installing Sense 2023-May, you may have weird QMC errors (Failed to load properties. No data found) on the QMC start page.

Solution/workaround:
On May2022, with already Postgre12.5, DON'T use the Postgre Updater, since it is not necessary, you can directly install 2023-May.

We did not contact support about this, due to the working workaround.

Version history
Last update:
‎2023-12-20 09:28 AM
Updated by: