Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
diagonjope
Partner - Creator III
Partner - Creator III

Restoring QSEoW....

Greetings!

If one uses pgAdmin4 to check the owner of the databases created by QSEoW, the only database that is actually owned by the user named "postgres" is the one named QSR. The other databases are owned by the user "qliksenserepository". However, the pg_restore commands provided in this help page indicates using the -U postgres option for the restoring of ALL these databases.  Is this correct?

Cheers,

++José

Labels (1)
2 Replies
Sonja_Bauernfeind
Digital Support
Digital Support

Hello @diagonjope 

The help site informs you of other databases having a different owner with a modified command to use:

For the SenseServices, QSMQ, and Licenses databases, the default owner is qliksenserepository instead of postgres. Use the following modified command for these databases, adjusting the database name accordingly: createdb -h localhost -p 4432 -U postgres -O qliksenserepository -T template0 SenseServices (link)

 

All the best,
Sonja 

 

Don't forget to Like posts and use the "Accept as Solution" button on content that answered your question! Thanks 🙂
diagonjope
Partner - Creator III
Partner - Creator III
Author

Hi @Sonja_Bauernfeind!  Thanks for your follow-up and for highlighting the warning paragraph in the section for "Restoring a Qlik Sense site to a machine with the same hostname".

Unfortunately, that warning is missing in the section titled "Restoring a Qlik Sense site to a machine with a different hostname".  So, if anyone, like me, goes straight to the instructions that are relevant to his/her immediate concern, the warning will be missed and subsequent problems might arise during the migration.

I think that the team in charge of the Help documentation must be asked to also include that warning in the section for migrating to a machine with a different host name.

Cheers,

++José