topic Re: Qlik Sense Aug 2021 Repair in Management & Governance

Qlik Sense Aug 2021 Repair

polyakov — Thu, 11 Nov 2021 14:52:43 GMT

Hi!

I have test server with Windows Server 2019 and Qlik Sense Aug 2021 (without patches).

I want to run Repair. I go to the App & Features and run modify on Qlik Sense instalation string.

But i get notify what Patch detected but patch is not installed.

How i can run correct repair?

Re: Qlik Sense Aug 2021 Repair

Sebastian_Linser — Fri, 12 Nov 2021 11:43:09 GMT

Hello @polyakov

Even though this is another symptom root cause might be the same as in this article https://support.qlik.com/articles/000040462

If the registry key for the patch does not exist and you also don't see it under appwiz.cpl -> view installed updates

Then please open a ticket with the Qlik support.

I do have one last question why do you want to run a repair? Just as a proof of concept or because something seems broken?

I have tested the repair today on a fresh installed Qlik Sense August 2021 and this worked without an error, at the end it promted for a reboot.

Best regards

Sebastian

Re: Qlik Sense Aug 2021 Repair

polyakov — Fri, 12 Nov 2021 14:29:21 GMT

I want to try repair DB or Files for recover worked functionality.

At this time released November 2021 and after update to this release - DB and files recovered.

For testing i drop all DB exclude postgres and rerun repair on Nov 2021 release.

In the result DB in not recovered.

Re: Qlik Sense Aug 2021 Repair

Sebastian_Linser — Fri, 12 Nov 2021 18:14:11 GMT

The installer doesn't recreated the Database on repair, only files.

If you follow the backup and restore points of Qlik sense adding an empty qsr database it would be re-initalized when starting the Repository service.

https://help.qlik.com/en-US/sense-admin/August2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Backup-and-restore.htm

Regards Sebastian

Re: Qlik Sense Aug 2021 Repair

polyakov — Mon, 15 Nov 2021 10:39:09 GMT

I'm curious if i execute update for the next release, it will recover DB while if run repair - it does not perform DB recovery doing files restore only.

If the updater restores the database to its default state, why isn't it enabled in recovery mode? This Can be enabled for user selection in repair mode - but is not included. I think is the second question.

Thanks for the help.

Re: Qlik Sense Aug 2021 Repair

Sebastian_Linser — Mon, 15 Nov 2021 12:47:48 GMT

Hello, @polyakov

for the last remaining question. This is not implemented in the product for the moment, but it would be great if you raise it as an idea here: https://community.qlik.com/t5/Suggest-an-Idea/idb-p/qlik-ideas

One trick which works is if you create the DB's and add them to the right user post repair, the first start of the Repository Service will initialise them again.

-- one by one, for creating the DB CREATE DATABASE "QSR" ENCODING = 'UTF8'; CREATE DATABASE "SenseServices" ENCODING = 'UTF8'; CREATE DATABASE "QSMQ" ENCODING = 'UTF8'; CREATE DATABASE "Licenses" ENCODING = 'UTF8'; //one at a time -- from here the whole script CREATE ROLE "qliksenserepository" WITH LOGIN NOINHERIT NOSUPERUSER NOCREATEDB NOCREATEROLE NOREPLICATION VALID UNTIL 'infinity'; -- change <qliksenserepository_user_pass> to your password for the repository service user ALTER ROLE "qliksenserepository" WITH ENCRYPTED PASSWORD '<qliksenserepository_user_pass>'; GRANT qliksenserepository TO postgres; ALTER DATABASE "QSR" OWNER TO "qliksenserepository"; ALTER DATABASE "SenseServices" OWNER TO "qliksenserepository"; ALTER DATABASE "QSMQ" OWNER TO "qliksenserepository"; ALTER DATABASE "Licenses" OWNER TO qliksenserepository; GRANT TEMPORARY, CONNECT ON DATABASE "QSMQ" TO PUBLIC; GRANT ALL ON DATABASE "QSMQ" TO postgres; GRANT CREATE ON DATABASE "QSMQ" TO "qliksenserepository"; GRANT TEMPORARY, CONNECT ON DATABASE "SenseServices" TO PUBLIC; GRANT ALL ON DATABASE "SenseServices" TO postgres; GRANT CREATE ON DATABASE "SenseServices" TO "qliksenserepository"; GRANT TEMPORARY, CONNECT ON DATABASE "Licenses" TO PUBLIC; GRANT ALL ON DATABASE "Licenses" TO postgres; GRANT CREATE ON DATABASE "Licenses" TO qliksenserepository;

You can ignore the Create Role part for qliksenserepository because you didn't drop that one. You start at creating the DB and then ALTER DATABASE "QSR"

scripts are from

https://help.qlik.com/en-US/sense-admin/November2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Installing-configuring-postgresql.htm

and

https://help.qlik.com/en-US/sense-admin/November2021/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Installing-configuring-postgresql-on-Azure.htm

best regards

Sebastian

Re: Qlik Sense Aug 2021 Repair

polyakov — Wed, 17 Nov 2021 10:36:02 GMT

Thanks for your advice. I will follow for your advice and have created idea on portal.

https://community.qlik.com/t5/Suggest-an-Idea/Repair-Qlik-Sense-DB/idi-p/1859405#M7796

For testing i stopped all services on testing server except Repository DB and drop all DB except postgres. Then i executed the script which you give me. Script executed success and created databases. I rebooted the server. But when server and services start i do not see listening port and though all serices in status runing, the Proxy Service do not listening web ports. I noticed what in databases: Licenses, QSMQ and SenseServices not have a tables.