The following restrictions apply to DB2® Change Management Expert.
- If you receive the following error message when you attempt to rebind
packages with a RI database, the DB2 CLI packages need to be bound with an
appropriate value for the bind parameter CLIPKG:
SQL0805N error, Package.Nullid.SYSLH203 was not found
For
more information about this problem and the solution, see the IBM® Software Support Web site.
- Database authorizations are generated by using the db2look utility. Results
may vary depending on that tool. Review the authorization commands carefully.
Authorizations generated for undo processing contain all the authorizations
returned by the db2look utility. If an object exists, authorization commands
will succeed (even if they are not required). For this reason, DB2 Change Management Expert runs
all authorizations. Authorization preservation for a change starts with the
GRANT and REVOKE statements that are returned by db2look. However, the object
of each authorization command is cross checked in the target model. If the
authorization object does not exist in the target it is removed; the GRANT
or REVOKE statement is removed from the script. The db2look utility has known
problems when generating authorization commands for table spaces. You might
need to review and correct the authorizations in that case.
DB2 Change Management Expert does
not support these features or objects that were introduced with DB2 V9.1: - Label-based access control (LBAC)
- XSR objects
- Domains (for example, CREATE DOMAIN)
- Character sets (for example, CREATE CHARACTER SET)
- Collation (for example, CREATE COLLATION)
- Ability to invoke external table functions in parallel (for example, CREATE
FUNCTION with DISALLOW PARALLEL or ALLOW PARALLEL EXECUTE ON ALL DATABASE
PARTITIONS RESULT TABLE DISTRIBUTED COLLATION)

- DB2 Change Management Expert does
not fully support DB2 method objects. In some cases, physical
data models will not be correctly reverse engineered from the catalog. In
addition, DB2 Change Management Expert does
not fully forward engineer method objects. When you are managing changes to
method objects, you should check your physical data models and change command
files to ensure that the commands are correct.
DB2 Change Management Expert does
not forward engineer federated objects such as servers, wrappers, function
mapping, or nicknames. 
DB2 Change Management Expert does
not preserve some attributes for tables and views when you create a model
from the DB2 catalog. Thus, if you later forward engineer DDL for the model,
the attributes are not included. The attributes that are not preserved are:- Tables
- CCSID ASCII or CCSID UNICODE
- SECURITY POLICY
- DB2SECURITY LABEL
- COLUMN SECURED WITH
- DATA CAPTURE
- COMPRESS SYSTEM DEFAULT
- ORGANIZE BY KEY SEQUENCE
- Views
- ENABLE QUERY OPTIMIZATION or DISABLE QUERY OPTIMIZATION
- WITH CASCADED/LOCAL CHECK OPTION
- WITH ROW MOVEMENT or WITH NO ROW MOVEMENT

DB2 Change Management Expert does
not properly recognize labeled durations that use the MINUTES keyword. The
Change Command Editor marks the keyword as an error. The Deployment Script
Editor is unable to convert DDL that contains the MINUTES keyword into individual
change commands, and DB2 Change Management Expert is
unable to deploy DDL that contains the MINUTES keyword.To work around this
problem, change occurrences of the MINUTES keyword to MINUTE.

- DB2 Change Management Expert will
not deploy your changes correctly if you have changes that involve a materialized
query table (MQT) that is based on an alias that is based on another alias
that is again derived from another alias that is based on a real table. You
might want to consider deploying changes in this type of situation outside
of DB2 Change Management Expert. This
situation is uncommon.
- DB2 Change Management Expert relies
on db2look functionality to maintain object authorizations during a change.
In some releases of DB2, db2look lacks support for certain database objects.
A known db2look problem exists when you generate grants for table spaces.
You should review the authorization scripts thoroughly before you issue them.