Help with Qlik Repository service only restarting after updating/unbundeling DB

[John-Harald]

Hi everyone, I was hoping someone could give me some help or advice with an issue I’ve been having with updating my Qlik Sense Enterprise for Windows install.

Our system consists of 3 servers, 2 Qlik instances installed with November 2023 Patch 9, one working as the central node and the other as a rim node. The third server runs a dedicated PostgreSQL instance and works as a store for all our data and log archive. Our servers do not have free access to the internet.

The central node also has the bundled database installed.

I was recently trying to update to May 2024 Patch 2, I also tried to unbundle the database. I tried following the guide posted here: https://community.qlik.com/t5/Official-Support-Articles/Upgrading-and-unbundling-the-Qlik-Sense-Repo... using the Qlik PostgreSQL Installer. However, when I tried this, I ended up with the Qlik Repository just continuously restarting over and over.

I tried multiple times in various ways:
Tried unbundling the database before updating the Qlik version.
Tried updating the Qlik version before unbundling the database.
Tried updating the Qlik version, unbundle the database and uninstall the old version and reinstall the PostgreSQL binaries.

I always end up with the same results Repository does not start. This is even when I undo everything related to running in a multi-node environment and just run everything on the single server.

Due to having to restore our system back to running state after this I do not have any logs, and also did not know where to find them when I could. If

Any advice or suggestions would be very helpful and appreciated.

[korsikov · Accepted solution]

short tip.

Before user Qlik Postgre Installer for unbundle Postgre you MUST uninstall any patches. 

After that:

1. make backup
2. uninstall patches on all nodes (central and rim)
3. stop all services on rim nodes.
4. unbundle PostgreSQL using QPI.
5. Check is it work on cental node
6. Update PostgeSQL to lasted version. Current it's 14.12
7. Check is it works fine.
8. make backup
9. update QS. 
10. If central node works - update RIM node.
11.  

[John-Harald]

I was not aware I needed to uninstall the patch. I will try this as soon as I have time!

[John-Harald]

I didn't find a good way to uninstall the patch, but I upgraded to the new version and unbundeled the database before installing the patch and that seemed to work.