Review the description of the DB2 agent attributes. The agent attributes are classified as required, optional, and internal.
Table: Required attributes for the agent for DB2 shows the required attributes for the agent for DB2, you must assign values to required attributes.
Table: Required attributes for the agent for DB2
Table: Optional attributes for the agent for DB2 shows the optional attributes for the agent for DB2.
Table: Optional attributes for the agent for DB2
Optional attributes |
Description |
||
---|---|---|---|
Name of the database for in-depth monitoring; required if in-depth monitor is enabled (IndepthMonitor = 1). Be careful when you change the DataBase name attribute as you can fault all the partitions in the database. Do not change the DataBaseName attribute to an invalid or an incorrect value.
Type and dimension: string-scalar |
|||
Node number or partition number of the database. Used when monitoring a specific database partition. Default: 0 |
|||
StartUpOpt |
Provides start up options. The allowed values are: START, ACTIVATEDB, or CUSTOM. Review the following options:
Type and dimension: string-scalar |
||
ShutDownOpt |
The allowed values for this attribute are STOP and CUSTOM. Review the following options:
Type and dimension: string-scalar |
||
IndepthMonitor |
Set the value of the IndepthMonitor attribute to 1 to enable in-depth monitoring. The agent now looks for the monitor_custom_$db2instance_$nodenum file in the /opt/VRTSagents/ha/bin/Db2udb directory. It executes this customized indepth monitor file if the file exists and is executable. You can find samples of custom monitor scripts in the sample_db2udb directory. Type and dimension: string-integer |
||
Specifies the operating system encoding corresponding to DB2 UDB encoding for display of DB2 UDB output. Type and dimension: string-scalar |
|||
AgentDebug |
When the value of this attribute is 1, it causes the agent to log additional debug messages. Type and dimension: boolean-scalar |
||
WarnOnlyIfDBQueryFailed |
This attribute either logs SQL errors, or checks the errors to handle them specially. Set the value of the WarnOnlyIfDBQueryFailed attribute to 1 to enable it. When this attribute is enabled, it ignores all SQL errors and logs a warning message in the agent log once a day. Set the value of the WarnOnlyIfDBQueryFailed attribute to 0 to disable it. When disabled, it checks if an error code needs to be handled specially in the db2error.dat file. If the error code does not exist in the db2error.dat file, then it returns OFFLINE for monitor. Otherwise, it follows the action of that particular error code in the db2error.dat file. Type and dimension: boolean-scalar |
||
UseDB2start |
Enables you to choose an alternate way to start DB manager. The agent executes the db2start when UseDBStart is set to 1, whereas it uses db2gcf when UseDBStart is set to 0. If the setup is non-MPP, you must set the value of the UseDB2start attribute to 1. If the setup is MPP, you must set the value of the UseDB2start attribute to 0. For MPP, VCS uses the actual hostname and needs the ability to start and stop each partition. For this purpose, VCS uses the db2gcf command and requires a value of 0 for the UseDB2start attribute. Type and dimension: boolean-scalar Default: 0 For more information on using UseDB2start attribute refer : See About DB2 configurations in VCS. |
Table: Internal attribute for the agent for DB2 shows the internal attributes for the agent for DB2.
Table: Internal attribute for the agent for DB2
Internal attributes |
Description |
---|---|
AgentDirectory |
Specifies the location of other files and scripts that are related to the agent. Do not use. For internal use only. |
IMF |
This resource-type level attribute determines whether the DB2 agent must perform intelligent resource monitoring. This attribute includes the following keys:
See Enabling and disabling intelligent resource monitoring for Db2udb resource. |