...
| Info | ||
|---|---|---|
| ||
It is recommended that you maintain separate QA (test) and Production instances. Upgrade your QA tier and confirm things are working as expected before upgrading Production. |
Backup Your Database
While upgrading is usually a fairly straightforward process, from time to time fairly significant database changes are made. Efforts are made to make these changes transparent, but as a precaution you should create a backup of your database prior to upgrading in case you need to revert the upgrade.
...
Various caches are maintained to improve performance, but can cause problems during upgrades. Clear existing caches prior to continuing.
| No Format |
|---|
$ cd app
$ ./Console/cake cache
[...]
Done clearing cache
|
...
| Note |
|---|
In order to avoid problems with file ownership, you should run console commands as the web server user. Otherwise, make sure the cache directory ( |
...
wherever |
...
points to) and all of its subdirectories and files are writeable by the web server. |
...
and |
...
may be in order after running console commands. |
| No Format |
|---|
$ cd app $ su -c "./Console/cake cache" ${APACHE_USER} [...] Done clearing cache |
Update Database Schema
Generally, updating the database schema is required when upgrading COmanage Registry. You may need to run this command as a user that has permission to write to your tmp directory.
| No Format |
|---|
$ cd app $ su -c "./Console/cake upgradeVersion" ${APACHE_USER} [...] Current version: 0.9.4 Target version: 1.0.0 [...] Database schema update successful |
| Info | ||
|---|---|---|
| ||
It is not always possible to upgrade multiple versions in one step. For example, if you are currently running 0.9.3 you cannot directly upgrade to 1.0.0. If you try, you will see the error message
You must download and upgrade successfully to version 0.9.4, and then you may download and upgrade from 0.9.4 to 1.0.0. |
| Info | ||
|---|---|---|
| ||
When upgrading the database schema, you may see " |
...
) |
...
Periodically, database tables are removed from use. The database schema management script does not currently drop disused tables (CO-672). You should remove them manually to avoid problems with deleting records with foreign key constraints.
...