DB2 Version 9.7 for Linux, UNIX, and Windows

Starting the governor

The governor utility monitors applications that are connected to a database, and changes the behavior of those applications according to rules that you specify in a governor configuration file for that database.

About this task

Important: With the new workload management features introduced in DB2® Version 9.5, the DB2 governor utility has been deprecated in Version 9.7 and might be removed in a future release. For more information, see "DB2 Governor and Query Patroller have been deprecated".

Before you start the governor, you must create a governor configuration file.

To start the governor, you must have sysadm or sysctrl authorization.

To start the governor, use the db2gov command, specifying the following required parameters:

START database-name: The database name that you specify must match the name of the database in the governor configuration file.
config-file: The name of the governor configuration file for this database. If the file is not in the default location, which is the sqllib directory, you must include the file path as well as the file name.
log-file: The base name of the log file for this governor. For a partitioned database, the database partition number is added for each database partition on which a daemon is running for this instance of the governor.

To start the governor on a single database partition of a partitioned database, specify the dbpartitionnum option.

For example, to start the governor on database partition 3 of a database named SALES, using a configuration file named salescfg and a log file called saleslog, enter the following command:

db2gov start sales dbpartitionnum 3 salescfg saleslog

To start the governor on all database partitions, enter the following command:

db2gov start sales salescfg saleslog