Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
Today I have to migrate Qlik to another server and I'm have the password for super user repository. The instruction at the website is pretty clear. I must create a backup of the repository database and I use this instruction below:
Produce a dumpfile for the repository database (that is, a single file for the entire database):
If you are prompted for the PostgreSQL super user password, enter the password that was given during the installation of Qlik Sense.
If I enter the lines and press enter, I get the message "Permission denied", see attachment. I am not prompted to enter a password.
How can I enter my password?
Thank you in advance.
Greeting from Martijn Wanders
That is strange, normally you would be prompted for the password next.
There are other ways of supplying the password when using pg_dump.exe
It can be supplied in a file and in a environment variable.
Perhaps something of this is in effect?
Do a search for pg_dump.exe and password.
Hi Anders,
Thank you for your reply. On internet I found material about RSM for backup. I tried this and there is a backup now. But I have to restore it so I don't know if everything is alright.
Hi Anders,
Todat I'm at another customer and here I'm prompted for the password but I can not enter this. I read about other solutions such as pgpass etc. but i don't have the knowledge for CMD coding.
How can I implemt such thing in this line?
pg_dump.exe -h localhost -p 4432 -U postgres -b -F t -f "c:\QSR_backup.tar" QSR
First issue the set command below;
set PGPASSWORD="yourpassword"
Then issue your backup command;
pg_dump.exe -h localhost -p 4432 -U postgres -b -F t -f "c:\QSR_backup.tar" QSR
I found the answer about entering password. If I enter the password I don't see the code in the screen and it seems that nothing is happening. But that is not the case. You can enter the code and press enter. It works.
p.s: i'm not a CMD specialist 😉
Ah ok. I have to enter the codes seperately. Thanks for clarifying.
I know this is an old thread but I just had the same problem and the solution (when finally figured out) was rather simple. At least in the environment I'm working.
When opening the cmd right click and Run as Admininstrator and after that it worked.