Ensure that these prerequisites are in place before finding
and fixing changes to access plans after rebinding packages.
- If the SQL statements run on DB2® for z/OS®:
- In the Data Source Explorer, connect to a DB2 for z/OS subsystem
that is configured for query workload tuning and where a license for IBM® InfoSphere® Optim™ Query
Workload Tuner is active.
- If the SQL statements are static, packages to be analyzed must
be bound with the EXPLAIN(YES) command.
- Ensure that the packages to be analyzed have the same names in
the source and target collections.
- Use the same authorization ID when performing the BIND operation.
The EXPLAIN output for the BIND operation must point to the same set
of EXPLAIN tables that you used when binding the packages the first
time.
- You must have the following privilege on these tables:
- SELECT privilege on the following DB2(r) system catalog tables:
SYSIBM.SYSPACKAGE, SYSIBM.SYSPACKSTMT, and SYSIBM.SYSPACKDEP
- SELECT privilege on the EXPLAIN tables (PLAN_TABLE and DSN_STATEMNT_TABLE)
under the package owners
- If the SQL statements run on DB2 for Linux, UNIX, and Windows:
-