Welcome to Embarcadero® DB Change Manager™ 5.6 and XE
Change Manager Web Site | Embarcadero Technologies
Home | Technical
Support
ReadMe Last Published: November 18, 2010. Any updates to these notes will be available at http://docs.embarcadero.com.
Thank you for using Embarcadero 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 Change Manager 5.6
See the DB Change Manager User Guide at
http://docs.embarcadero.com/products/change_manager/
or the online help for details about the new features.
Changes in the 5.6/XE release include:
- Schema comparison job user interface improvements let you easily browse and
filter results and review a summary of object types and actions before you run
a sync script. These features also improve performance and scalability.
-
You can specify how schema or configuration archive versions are kept on disk.
Versions can be deleted based on how old they are, how many there are,
or how much disk space they consume.
-
Schema comparison jobs include new objects by default.
You can modify this setting in the Preferences.
-
A Split reports feature breaks large reports into smaller sections
and limits the number of objects per section.
By default the number is 1000. This improves performance for very large reports.
-
Schema comparison and archive job Refinements tab activities now perform faster.
-
In SQL Editor, if a SQL script is larger than 3 MB,
it will open and a message will say that parsing was deactivated.
-
The format in which schema comparisons are saved has changed.
Use the import feature to import pre-5.6 schema comparison jobs.
Release Notes
System Requirements
Important Advisory Notes
Upgrading
Known Issues
Bug Fixes
System Requirements
Change Manager supports the following operating systems:
- Microsoft Windows 7 (x86-32,
Win32), Microsoft Windows 2008 (x86-32, Win32), Microsoft Windows
XP (x86-32, Win32), Vista (x86-32, Win32), or Microsoft Windows Server
2003)
- Red Hat Enterprise Linux 5.0, x86-32, GTK 2 or SuSe Linux Enterprise
Server (x86) GTK+ 2.x
- 1.2 GHz Processor
- 1 GB of RAM
- 500 MB of hard disk space
- 1024 x 768 display
DBMS Support
Change Manager supports the following platforms.
- Oracle 8i - 11g
- Sybase 12.5 - 15.0, 15.0.1, 15.0.2
- IBM DB2 LUW 8.0 - 9.5
- Microsoft SQL Server 2000, 2005, and 2008
- InterBase 2007, 2009
- Firebird 1.5, 2.0
Important Advisory Notes
- You can install Change Manager as an
Eclipse plugin. This
installation feature lets Eclipse users add a version of Change Manager with full
functionality to their development environment without requiring the
standalone application.
- Change Manager 5.6 is
not compatible as a plugin with Rapid SQL Developer 2.x and DB Optimizer 2.5.
Upgrading
DB Change Manager 5.6 should be installed in a different directory than previous versions.
If DB Change Manager is installed in the same directory,
the following error will result in at application start up:
"Unable to read workbench state. Workbench UI layout will be reset."
If a previous version 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 5.6.
Use the import feature to import pre-5.6 schema comparison jobs.
DB Change Manager 5.6 provides an upgrade process for moving jobs and other information from
an existing Change Manager 4.0, 5.0, 5.1.x and 5.5.x installations.
Upgrading from Version 5.0, 5.1.x, or 5.5.x to Version 5.6
All objects can be imported from version 5.0, 5.1.x or 5.5.x to Version 5.6.
To upgrade from 5.0, 5.1.x, or 5.5.x:
-
Make sure that the earlier product is not running and that no command line jobs are being processed.
-
Install and run DB Change Manager 5.6 in a different directory than the previous installation.
-
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.
-
Click Get Started to launch the Import Wizard.
Alternatively, you can launch the Import Wizard from the main menu:
-
Select File > Import.
-
Select Change Manager Workspace from the Embarcadero group and click Next.
-
Select the version of Change Manager from which to import.
-
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.
-
The wizard imports the items from the previous Change Manager version.
Click Next to continue through each step of the wizard.
-
Click Finish. The jobs are imported to version 5.6.
Upgrading from Version 4.0 to 5.6
The following objects can be imported from version 4.0:
- data sources
-
all comparison jobs (data, configuration, and schema)
-
configuration archives
-
configuration standards
-
The following objects cannot be imported from version 4.0:
-
schema archive versions
-
synchronization scripts
-
reports
-
command line automation (scheduled jobs, batch files, etc.)
Note: 4.0 should remain installed to access any archives and reports.
To upgrade from 4.0:
-
To import schema comparison jobs from 4.0, obtain and install cmschema_40_932_upgrade.exe from your Embarcadero Technologies Support representative.
-
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.
-
Follow the steps as described in the previous section, "Upgrading from Version 5.0, 5.1.x or 5.5.x".
Known Issues
General
- SQL Filter's conditions changed. In 5.0.3, the conditions within a SQL
Filter are applied in an AND manner (an intersection of the conditions
specified), but in 5.1, the conditions are applied in an OR manner (a reunion
of conditions).
- Type filter text from Data Source Explorer does not apply correctly for
imported data sources.
- The SQL Editor doesn't have an option to Set ON/OFF ARITHABORT for SQL
Server. The DML generated by data comparison will fail on tables with
indexes on computed columns or indexed views if the default Server setting is
OFF.
- Running jobs from the command line is not yet supported for the All Access
InstantOn version of Change Manager.
- The CM Schema 4.0 943 patch needs to be run twice in order to successfully
update an older CM Schema installation.
- Code complete is available only after you enable indexing of the specific
data source.
- While licensing, if the error "Cannot find base license" appears, try
removing the line:
"[email protected]/change_manager_5/configuration" from the
change.ini file and changec.ini file in the installation folder of Change
Manager 5.1.
- Users of InterBase may experience difficulties using the SQL Editor in
some isolated cases. You can disable parsing for the SQL Editor
script-by-script by right-clicking on the file in the Navigator view and
changing the Parser Settings. Contact support for more information.
- The
Open Scheduled Tasks button from the toolbar is not available for use
with the InstantOn version for Windows 2008 OS. As a workaround you
could start the scheduled tasks window manually from the operating
system functionality or install the application.
- Quick Launch icon is not available for Windows 2008 and Windows 7.
- SQL
Editor doesn't display big ntext fields for MS SQL Server caused by
Eclipse limitations for simple text files. The characters are there,
but can't be seen. If you copy the content of the SQL Editor and paste
it in a document you can see that the characters are displayed
correctly.
- Installing the application in the root partition C:\
is not recommended because serious problems may occur and some
functionality may fail to execute correctly.
- Sync Scripts Import functionality is not available from CM Data and Config 4.0 to Change Manager 5.1 and newer versions.
Schema Comparison
- The Ignore Object Permissions option for schema comparison jobs does not
work if the Enable Dependency Linking option is not selected in the
Preferences page. By default, Enable Dependency Linking is unchecked for
Oracle, so all Grant statements for Oracle objects are not extracted and
compared.
- Identical views with different Header comments cannot be synchronized on
SQL Server.
- Comparison fail views on SQL Server if the "Compatibility level" server
property is set to 70=SQL Server 7.0.
- Comparison fails for Tables and Indexes on DB2 if the system temporary
tablespace is a page size smaller than 8k. We recommend using a 16k page size so
that Change Manger queries run seamlessly.
- When using DB2 version 8.1 with different collation between the source and
target, the object matching will not be correct due to an IBM server known
limitation.
- Identical views are seen as different when comparing cross platform
objects SQL Server vs. Oracle due to text property which specifies the view
columns on Oracle. The same problem occurs for SQL Server vs. Sybase, due to
the way that Sybase returns the select statement.
- Identical Check constraints are seen as different when comparing objects
on Oracle, Sybase towards SQL Server, due to the way SQL Server returns check
conditions.
- When comparing tables among different versions of Oracle, the default
values for Storage parameters will be removed from synchronization.
- The options "Ignore Constraint Names", "Exists in Target Only (Drop)", and
"Ignore Specific Name" work only for object types for which all items are
included on the refinements tab. Specific object selection will invalidate
these option selections.
Data Comparison
- For MS SQL, you should manually exclude System Databases from any
Data Movement and Data comparison (e.g. master, msdb, model, etc.) in order to
avoid any alteration on data dictionary. See
http://msdn.microsoft.com/en-us/library/aa260604.aspx and
http://msdn.microsoft.com/en-us/library/ms179932.aspx.
- Data Auto-synchronization Limitations:
- When updating the IBM DB2 client with new patches, or upgrading from the
installed version, the client needs to be rebound to the IBM DB2 server. If
rebinding is not performed, there will be problems in getting metadata using
the DB2 driver. One solution is to drop and recreate the database if you are
unconcerned about the data in that database. This will automatically perform
the required bindings.
- For tables having columns with data type DECFLOAT, data migration
gives null pointer exception and the data does not get moved properly.
- For tables having columns with data type MLSLabel Oracle driver gives
a null pointer exception.
- Data Auto-synchronization is not supported for versions of InterBase
2007 below Service Pack 3 (v8.1.1.333)
- Use
the trim trailing spaces option when doing a cross-platform comparison
for tables with binary, nchar, numeric or unichar data types towards
SQL Server, because the server is appending trailing blanks and 0s when
data is inserted in the tables.
- Random exceptions could be
experienced when performing data movement jobs using MS SQL trusted
connection caused by concurrency issues when Secur32, ntdll (
from Windows) and ntlmauth from dbconnection (DB Change Manager internal plugin) are accessed.
Bug Fixes
Bugs fixed in Change Manager 5.6
Bug |
DBMS |
Description |
11853 |
All |
Data source Properties fields are not editable, a Connect and Disconnect has to be done in order for the fields to be enabled once more
|
11400 |
All |
When doing a schema archive job, the extracted DDL shows alter statements before table creation statements
|
13100 |
All |
DB Change Manager needs to be set to XP compatibility level to work on Windows 7
|
13081 |
All |
In a schema comparison job comparing two archives, the Mapping tab is not getting update when the schema overview Source and Target have "Most Recent version" selected
|
2870 |
All |
The most recent version is not updated when running a schema comparison job
|
12679 |
DB2 |
Wrong sync script when you schema compare a partitioned table space and a default table space
|
12678 |
DB2 |
Incorrect sync script is generated during a schema comparison of two partitioned table spaces
|
12633 |
DB2 |
Index, table and MQT population fails if you create them using a nickname for a remote table
|
13148 |
Oracle |
Selected items are deselected in the Schema Compare Resolution/Matching page when scrolling down page
|
13118 |
Oracle |
Identical materialized views are seen as different
|
13049 |
Oracle |
Schema comparison is not retrieving PK "USING INDEX" from database, although the archive job does; causes compare errors
|
13036 |
Oracle |
Generated sync script is not in correct order for Oracle for ALTER TABLE DROP PK and ALTER TABLE DROP RELATED INDEX statements
|
12852 |
Oracle |
Invalid script generated for synchronizing materialized on Oracle
|
12500 |
Oracle |
NPE thrown when comparing Oracle tables
|
12160 |
Oracle |
An error occurred while populating a table
|
1759 |
Oracle |
Schema archive fails for partitioned indexes on Oracle
|
13530 |
SQL Server |
User defined datatypes on SQL Server are not archived correctly |
13105 |
SQL Server |
Incompatible status triggered when comparing views with functions on SQL Server
|
13101 |
SQL Server |
Invalid create script for views that use select statement aliases
|
13050 |
SQL Server |
Computed columns are not extracted correctly on SQL Server; spaces are trimmed
|
13044 |
SQL Server |
Same table with extended properties on SQL Server is seen as different
|
12868 |
SQL Server |
Schema comparison fails on tables with extended properties on SQL Server
|
12842 |
SQL Server |
Identical procedures seen as different on SQL Server |
12654 |
SQL Server |
The new created PK for a pair of tables is not picked up when re-inspecting the parent databases pair in a data comparison job
|
12480 |
SQL Server |
Random issue with missing views in comparison task with archives
|
12309 |
SQL Server
|
Data comparison errors: "Internal Error has occurred"
|
5120 |
SQL Server |
Identical identity tables are seen as different when comparing an archive against a live source
|
4619 |
SQL Server
|
Ignore name case option generates create with columns in random order
|
2561 |
SQL Server
|
Extended properties not included in the sync file for tables
|
13325 |
Sybase |
Incorrect permission script extracted on Sybase views in DS Explorer and Schema Comparison
|
13147 |
Sybase |
Identical tables seen as different when comparing them between a server without Sybase encryption feature and one that has the feature
|
13141 |
Sybase |
Command line jobs fail for Sybase 15 |
12649
|
Sybase
|
SET QUOTED_IDENTIFIER is not set in front of views on Sybase when generating sync script for a comparison or archive
|
Additional Resources
Embarcadero Technologies Technical Support
Embarcadero Technologies on the Web
Embarcadero Technologies Technical Support
If you have a valid maintenance contract with Embarcadero
Technologies, the Embarcadero Technical Support team is available to assist you
with any problems you have with our applications. Our maintenance contract also
entitles registered users of Embarcadero Technologies products to download free
software upgrades during the active contract period. Evaluators receive free
technical support for the term of their evaluation.
We encourage you to visit the Support section of our
Web site.
Embarcadero Technologies on the Web
To download evaluations of other Embarcadero Technologies products
or to learn more about our company and our products visit us at http://www.embarcadero.com/.