can't restore odoo database in the same environment? - postgresql

I am tried to take a backup from my odoo 12 server and this was done correctly, immediately I am trying to restore it again, and I found this error
Database restore error: Postgres subprocess ('/usr/bin/pg_restore', '--dbname=database_name', '--no-owner', '/tmp/tmp2bohi3ne') error 1
odoo installed and running with docker-compose
so how can I restore it again

Related

Fatal error: No default database configured

When I try to do a migration of my database in heroku using vapor I get the following error when I run heroku run Run -- migrate --env production
FluentKit/Databases.swift:160: Fatal error: No default database configured.
I execute heroku config and created a database before migration.
Local migration works for me without problem. From a database management software if I can access the database without problem.
Thanks

How to migrate openproject database from Postgresql v9.4 to v9.6 within a docker installation?

I'm trying to update my OpenProject from v7.0 to v8.0 using the new Docker image.Everything went well till I try to import the database. The new version uses Postgresql v9.6 which is incompatible with the former Postgresql v9.4.
There is a good guide on the OpenProject website on how to migrate to Postgresql v9.6: https://www.openproject.org/operations/upgrading/openproject-postgresql-migration-guide-9-6/ . But it covers only the linux installation.
How is it possible to migrate the OpenProject database from Postgresql v9.4 to v9.6 within docker ?
Finally a solution is found. Here are the general steps for the migration:
Create the database backup of the current installation:
Connect to the old Container v7.0
Stop the running services, except postgers, via supervisorctl stop < service_name >
Create the dump of the database with the name "openproject"
Exit the container and copy the created dump outside it
Restore the database into a the new installation:
Copy the former created dump inside the new container v8.0
Connect to the new Container v8.0
Stop the running services, except postgers, via supervisorctl stop < service_name >
Connect to the postgresql database server and delete the database "openproject"
Create a new "openproject" database and assign it to the user "openproject"
Restore the openproject database using the dump file
Exit and restart the container
OpenProject system will automatically recognize the old database structure and will migrate the tables to match the new version.
I hope this will help someone

newly installed postgres startup error

I have installed postgres & also started the server. But, when I tried to start console using psql, I'm getting error like database "****"(any database) does not exists. How to resolve this error?? I don't have acces to psql shell. And is there other way to create or change startup database without accessing psql.

Why is pg_restore returning successfully but not actually restoring my database? PostgreSQL 9.5

I'm trying to use PostgreSQL 9.5 with pgAdmin 4 (I would prefer to use pgAdmin 3 but I get the following message when trying to connect to my database:
"Warning:
The server you are connecting to is not a version that is supported by this release of pgAdmin III.
pgAdmin III may not function as expected.
Supported server versions are 8.4 to 9.3")
So I'm forced to use pgAdmin 4. However, when I restore (like I usually do on pgAdmin III) I get a 'successful' restore but no data is actually restored into the tables.
If I click on the details of the 'successful' restore I am presented with this:
"1. pg_restore: connecting to database for restore"
How do I fix this issue?
Would you provide pgAdmin4 logs after running restore?
pgAdmin4 Log location:
Linux:
~/.pgadmin/pgAdmin4.log
~/.pgadmin/job_logs/
Windows:
%appdata%\pgAdmin\pgAdmin4.log
%appdata%\pgAdmin\job_logs\
Note: Do not close Success dialog in pgAdmin4 after restore otherwise once you acknowledge the success dialog, pgAdmin4 will delete respective job log files from "job_logs" directory & also delete "pgAdmin4.log" before running restore to trim unwanted logs.

Google Cloud MySql Instance An unknown error occurred when importing

I created a mysql instance and everything is running on it. I used the process outlined in the cloud sql import to create a mysqldump file from my local production mysql instance running on windows.
mysqldump --databases xxxxx -uroot -p --hex-blob --default-character-set=utf8 > d:\database_file_feb2_2014.sql
Uploaded the file to the cloud storage and every time I try to import I get a Unknown error.
Things I have checked.
1) Made sure the USE database; command was in the file after the
CREATE DATABASE IF NOT EXISTS databasename;
command.
2) Made sure i was using the --hex-blob command.
created a export of smaller test db which was only 4.5MB instead of the 6GB file i was trying to import. Ran the first few lines from the sql prompt which ran fine.
Still unable to isolate at which line the import is breaking or Why
When I try to view the log from the old console, I get "An error has occurred. Please retry later."
I have dumped the whole instance and recreated the instance and still get the same error.
Origin OS: Windows Server 2003 R2
Running Mysql 5.1
Any advise on how I can troubleshoot this and move forward.
Thank you