DB Change Manager Home
| DB Change Manager
Documentation | IDERA Technical
Support | www.idera.com
ReadMe
Last Published: March 24, 2017. Any updates to these notes will be available at
https://www.idera.com/support/productdocuments.
Thank
you for using IDERA DB Change Manager! Its compare, synchronization, data
masking, and auditing capabilities let you track and report on changes, roll
out new releases, and pinpoint performance problems resulting from changes to
the data, schema, and database configurations. By comparing a live database to
a schema or configuration “snapshot” administrators can quickly identify
changes and correct problems. By monitoring configuration settings, DBAs can
ensure compliance with regulatory policies and performance standards, and
maintain overall database performance and availability.
What's New
in DB Change Manager
Requirements
Release Notes
Additional Resources
What's New in
DB Change Manager
This release begins a rollout of rebranding this product from
Embarcadero to IDERA. Note that these changes include a new license agreement,
installation and data directories, icons, file names, registry settings, and
more. For more information about IDERA and IDERA products, see www.idera.com.
Simplified licensing now offers a single DB Change Manager license
for all environments.
DB Change Manager now supports installations on 64-bit systems.
DB Change Manager now uses Java 1.8 update 91 and the Eclipse
4.5.2 platforms.
Requirements
DB
Change Manager requires the following:
Supported Operating Systems
DB Change Manager is supported on the following operating systems
(32- and 64-bit):
DB Change Manager is supported on the following DBMS platforms and
versions:
* For these databases,
DB Change Manager supports a subset of this database version’s
features/functions.
Release Notes
·
DB Change Manager 2016+ should be installed in a different
directory than 4.x, 5.x, 6.0.x, 6.1, 6.2, 6.3.x, and 2016 (6.3.3) 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.
·
DB Change Manager 2016+ 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 installations. No upgrade process is required to move from 6.x
installations to DB Change Manager 2016+ (16.5).
NOTE: You do not have to upgrade to 5.6 and then to DB Change Manager
2016+ (16.5). The import procedure is the same.
Upgrading
from Version 5.0, 5.1.x, 5.5.x or 5.6 to DB Change Manager 2016 (6.3.3) or 2016+
(16.5)
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) or 2016+ (16.5).
To
upgrade from 5.0, 5.1.x, 5.5.x or 5.6:
1.
Make sure that the
earlier product is not running and that no command line jobs are being
processed.
2.
Install and run DB
Change Manager 2016+ in a different directory than the previous installation.
3.
The Welcome to DB
Change Manager dialog opens with the Setup
and Import data sources, jobs, and settings from a previous version
import options selected.
4.
Click Get Started
to launch the Import Wizard. Alternatively, you can launch the Import
Wizard from the main menu:
o Select File > Import.
o Select Change Manager Workspace from the
IDERA group and click Next.
5.
Select the version of DB
Change Manager from which to import.
6.
Select the location of
your DB Change Manager workspace. The default value is the default workspace,
so you need only change this value if you configured DB Change Manager to store
the workspace in a custom location.
7.
The wizard imports the
items from the previous DB Change Manager version. Click Next to
continue through each step of the wizard.
8.
Click Finish. The
jobs are imported to DB Change Manager 2016+.
Upgrading
from Version CMSchema 4.0 or CMData/Config 4.0 to DB Change Manager 2016+
The
following objects can be imported from version 4.0:
The
following objects cannot be imported from version 4.0:
NOTE: 4.0
should remain installed to access any archives and reports.
To
upgrade from CM Schema 4.0:
1.
To import schema
comparison jobs from 4.0, obtain and install cmschema_40_932_upgrade.exe
from your IDERA Technical Support representative.
2.
Run
cmschema_40_932_upgrade.exe to convert the schema component jobs from version
4.0 to 5.0, which uses an XML-based format.
3.
Follow the steps as
described in the previous section, Upgrading from Version 5.0,
5.1.x, 5.5.x or 5.6 to DB Change Manager 2016 (6.3.3) or 2016+ (16.5).
General
Schema
Comparison
Data
Comparison
There
are no bug fixes included in DB Change Manager 2016+ (16.5).
Customer-reported bugs
fixed for the DB Change Manager 2016 (6.3.3) release:
|
Bug |
Description |
DBMS |
|
SC-14595 |
Schema Compare -
Triggers and Logical Foreign Keys failures. |
Sybase ASE |
|
SC-14594 |
Column Width Archive
Issue. |
SQL Server |
|
SC-14591 |
Identity Columns are
not correctly Extracted when Archiving a Database. |
SQL Server |
|
SC-14584 |
Schema archive job
creates incorrect SQL for a view with column level permissions. |
Sybase ASE |
|
SC-14580 |
Schema Comparison -
SYS.INSERT_TSN_LIST$ is not found in some cases. |
Oracle |
|
SC-14567 |
Case # 00425065:
Schema Compare - Missing Comparison Configurations. |
Oracle |
|
SC-14565 |
Owners are not
populated in refinements tab. |
Oracle |
|
SC-14553 |
Case # 00413533 -
Table difference being reported when there are no differences. |
Oracle |
|
SC-14547 |
Ability to include
> 10000 objects in a Schema Report. |
All |
|
SC-14524 |
Schema archive job creates
incorrect SQL for a view with column level permissions. |
Sybase ASE |
Customer-reported bugs fixed for the DB Change
Manager 2016 (6.3.1) release:
|
Bug |
Description |
DBMS |
|
SC-14489 |
Linux - Error when generating
configuration archive report. |
All |
|
SC-14490 |
Incorrect order of
statements in the Synch Script. |
SQL Server |
|
SC-14491 |
Support to ignore
object comments for SQL Server on schema comparison. |
SQL Server |
|
SC-14495 |
Data-synch job start
but makes no progress after 4+ hours. |
SQL Server |
|
SC-14498 |
Automatic sync - The
progress between sync summary and sync results is not the same. |
MySQL |
Customer-reported bugs fixed for the DB Change
Manager 2016 (6.3) release:
|
Bug |
Description |
DBMS |
|
SC-14281 |
[Schema Comparison
Job] Procedures showing "Don't Match" but when click View
Differences, there are no differences. |
Sybase |
|
SC-14289 |
[Schema Comparison Job]
when there is an ALTER procedure after the creation. ANSI_NULLS and
QUOTED_IDENTIFIER have been turned off. |
SQL Server |
|
SC-14463 |
[MSSQLServer]
Length of User Defined Datatype in Database Objects
is twice [nchar nvarchar]. |
SQL Server |
|
SC-14470 |
Incorrect comparison
of User Defined Types. |
SQL Server |
Additional
Resources
All IDERA products include a 14-day trial period. To continue
using the product without interruption, we recommend that you license it as soon
as possible. For information on licensing your product, refer to the Quick
Start Guide. If you have not yet purchased this product, contact [email protected].
The IDERA Web site is an excellent source for additional product
information, including white papers, articles, discussion forums, and the IDERA
Knowledge Base. Visit www.idera.com/support,
or click any of the links below, to find:
If you have a valid maintenance contract with IDERA, the Technical
Support team is available to assist you with any problems you have with our
applications. Our maintenance contract also entitles registered users of IDERA
products to download free software upgrades during the active contract period.
Evaluators receive free technical support for the term of their evaluation (14
days).
We encourage you to open technical support cases via the Customer Support Center. For
additional information about IDERA Technical Support, visit the Support section of our Web site.
To download evaluations of other IDERA products or to learn more
about our company and our products visit us at www.idera.com.