Command Reference

db2gov - DB2 Governor

Monitors and changes the behavior of applications that run against a database. By default, a daemon is started on every logical node, but the front-end utility can be used to start a single daemon at a specific node to monitor the activity against the database partition at that node.

For more information about this command, see the Administration Guide.

Authorization

One of the following:

• sysadm
• sysctrl

Command Syntax

>>-db2gov------------------------------------------------------->
 
>-----+-START--datadase--+--------------------+---config-file--log-file--+>
      |                  '-NODENUM--node-num--'                          |
      '-STOP--database--+--------------------+---------------------------'
                        '-NODENUM--node-num--'
 
>--------------------------------------------------------------><
 

Command Parameters

START database

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.

NODENUM node-num

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 node configuration file.

config-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 database

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 node configuration file.