Many odoo users have encountered the problem that the backed up database cannot be restored

You can self-check in the following ways

1. Is the odoo version correct? Different versions of odoo cannot be restored directly, for example, odoo13 cannot be restored directly to odoo15

2. Whether the database version is correct, postgres may have problems when it is backward compatible. It is recommended to migrate to the same version.

3. Whether the code is migrated correctly, inconsistent codes on both sides will also cause an error, which is common in the conf file without specifying the code location.

If you confirm that the above content is correct, you can try the following methods

1. Add -d database name -i base when starting odoo through the command line, this method is to select the database to force the update of the base module; because all odoo modules are dependent on this, the mandatory update will be all the modules installed in the database after the base Will be upgraded.

2. Enter postgres, enter the following command

su postgres; # Switch postgres users
psql; # Enter the postgres command line
\c; database name # specify database instance
DELETE FROM ir_attachment WHERE url LIKE '/web/content/%'; # Delete the front-end files cached in the data table

Generally, most problems can be solved through the above two steps.

Read More:

• odoo Error: KeyError:‘ir.http‘ [How to Solve]
• [Solved] Conda Upgrade Error: PackageNotInstalledError: Package is not installed in prefix.
• Python Connect database error: command listdatabases requires authentication
• An error is reported in the requirements code of the generated project
• Design python+mysql database with multi-level menu directory
• Python classes that connect to the database
• [Solved] error in REfO setup command: use_2to3 is invalid.
• [Solved] Saving to Database Error: pymysql.err.DataError: (1366, “Incorrect string value…
• [Solved] flash initializate database error: Keyerror: ‘migrate’
• ‘InceptionOutputs‘ object has no attribute ‘log_softmax‘
• Flask Database Migration Error: ERROR [flask_migrate] Error: Can‘t locate revision identified by ‘a1c25fe0fc0e‘
• [Solved] RuntimeError: a view of a leaf Variable that requires grad is being used in an in-place operation
• Python Grpc Error: A file with this name is already in the pool
• “EncoderDecoder: ‘mit_b1 is not in the backbone registry‘“ [How to Solve]
• Failed to establish a new connection: [winerror 10048] in the requests thread pool, the interface is called circularly to get the datagram error
• [Solved] error in pycallgraph setup command: use_2to3 is invalid.
• [Solved] RuntimeError: a view of a leaf Variable that requires grad is being used in an in-place
• [Solved] RuntimeError (note: full exception trace is shown but execution is paused at: ＜module＞)
• [Solved] Error starting proxy server: oserror (10013), “an attempt was made to access the socket in a way that the access permission is not allowed.”, None, 10013, None)
• For the problem of rejecting old usage errors after numpy is updated, modified in numpy 1.20; for more details and guidance