Before you tune an SQL statement, ensure that the necessary
tables and other objects exist on the DB2® database
or subsystem that the statement runs on.
Before you begin
- If you are using a DB2 for Linux, UNIX, and Windows database,
ensure that the user ID that you use to verify the configuration is
a member of the DB2ADMNS group.
- If you are using a DB2 for z/OS® subsystem, ensure that your
authorization ID has SYSADM authority.
- In the Data Source Explorer or Administration Explorer,
connect to the DB2 database or subsystem, if the connection is not
already open.
Procedure
To verify that a DB2 database
or subsystem is configured for single-query tuning:
- Right-click the database or subsystem and select Analyze
and Tune > Configure for Tuning > Advanced
Configuration and Privilege Management.
- If you are using a DB2 for Linux, UNIX, and Windows database,
follow these steps:
- If you are using InfoSphere® Optim™ Query Tuner for DB2 for Linux, UNIX, and Windows: In the Activated license field,
look for the message No product license for InfoSphere
Optim Query Workload Tuner is activated on the data server.
- In the Configuration Status section, check
that EXPLAIN and ADVISE tables and the stored procedure for index
recommendations are enabled.
- In the Features section, ensure that the
features that are listed under Basic functions have
checkmarks next to them.
- If you are using a DB2 for z/OS subsystem, follow these steps:
- If you are using InfoSphere Optim Query Tuner for DB2 for z/OS: In
the Activated license field, look for the message No
product license for InfoSphere Optim Query Workload Tuner is activated
on the data server.
- In the Query Tuner section, check that
the Query Tuner packages and Query Tuner tables are enabled.
- In the EXPLAIN Tables section, check that
the your authorization ID is has access to a set of EXPLAIN tables.
- In the Features section, ensure that the
features that are listed under Basic functions have
checkmarks next to them.