The DB2 Governor monitors and changes the behavior of applications that run against a database. By default, a daemon is started on every database partition, but the front-end utility can be used to start a single daemon at a specific database partition.

Authorization

One of the following:

•     sysadm
•     sysctrl

In an environment with an instance that has a db2nodes.cfg file defined, you might also require the authorization to invoke the db2_all command. Environments with a db2nodes.cfg file defined include partitioned database environments as well as single-partition database environments that have a database partition defined in db2nodes.cfg.

Command Syntax

db2gov [START | STOP] <db_name> [DBPARTITIONNUM <dbpart_number>] 
<cfg_file> <log_file>

Command parameters

START <db_name>
Starts the governor daemon to monitor the specified database. Either the database name or the database alias can be specified. The name specified must be the same as the one specified in the governor configuration file.
Note: One daemon runs for each database that is being monitored. In a partitioned database environment, one daemon runs for each database partition. If the governor is running for more than one database, there will be more than one daemon running at that database server.

DBPARTITIONNUM <dbpart_number>
Specifies the database partition on which to start or stop the governor daemon. The number specified must be the same as the one specified in the database partition configuration file.

<cfg_file>
Specifies the configuration file to use when monitoring the database. The default location for the configuration file is the sqllib directory. If the specified file is not there, the front-end assumes that the specified name is the full name of the file.

<log_file>
Specifies the base name of the file to which the governor writes log records. The log file is stored in the log subdirectory of the sqllib directory. The number of database partitions on which the governor is running is automatically appended to the log file name. For example, mylog.0, mylog.1, mylog.2.

STOP <db_name>
Stops the governor daemon that is monitoring the specified database. In a partitioned database environment, the front-end utility stops the governor on all database partitions by reading the database partition configuration file db2nodes.cfg.

Compatibilities

For compatibility with versions earlier than Version 8:

•     The keyword NODENUM can be substituted for DBPARTITIONNUM.