DB Change Manager 17.1 should be installed in a different directory than 4.x, 5.x, 6.0.x, 6.1, 6.2, 6.3.x, 2016 (6.3.3), 2016+ (16.5), 16.6, and 17.0 versions. If DB Change Manager is installed in the same directory, the following error will result at application start up: "Unable to read workbench state. Workbench UI layout will be reset."
If one of the conflicting versions is already installed on your machine, either change the default Workspace or delete all files from the Workspace directory. The Workspace directory location appears whenever you start DB Change Manager and can be redefined from this dialog box. If the same Workspace is indicated for the new version, as was indicated previously, the following error will result: "Cannot restore workbench layout."
If DB Change Manager is already running, you can also modify the Workspace directory by choosing File > Switch Workspace > Other from the Main menu.
The format in which schema comparisons are saved has changed in 6.x. Use the import feature to import pre-6.0 schema comparison jobs.
Beginning with version 17.0, DB Change Manager provides an upgrade process for moving jobs and other information from an existing DB Change Manager 4.0, 5.0, 5.1.x, 5.5.x or 5.6 installation. No upgrade process is required to move from 6.x installations to DB Change Manager 17.1.
You do not have to upgrade to 5.6, and then to DB Change Manager 17.1. The import procedure is the same. |
All objects can be imported from version 5.0, 5.1.x, 5.5.x or 5.6 to DB Change Manager 2016 (6.3.3), 2016+ (16.5), 16.6, 17.0, or 17.1.
To upgrade from 5.0, 5.1.x, 5.5.x or 5.6:
The following objects can be imported from version 4.0:
The following objects cannot be imported from version 4.0:
4.0 should remain installed to access any archives and reports. |
To upgrade from CM Schema 4.0:
Issue Number | Description | DBMS |
---|---|---|
SC-14764 | Errors coming up for schema comparison job movies_dev to movies_prod | Oracle |
SC-14757 | Configuration compare job does not save work | Oracle |
SC-14626 | NullPointer exception while generating report once Schema Archive Job completed |
| | | | | | | |