Agents Administration - Tests
 

Configuration of Db2DPFSQLNetTest

The Database Partitioning Feature (DPF) is available on DB2 UDB Enterprise Server Edition (ESE). With DPF your database is scalable as you can add new machines and spread your database across them. This means more CPUs, more memory and more disks from each of the additional machines for your database! DB2 UDB ESE with DPF is ideal to manage data warehousing, data mining and online analytical processing (OLAP) workloads. It can also work well with online transaction processing (OLTP) workloads.

When a database is partitioned, you split your database into different independent parts, each consisting of its own data, configuration files, indexes and transaction logs. Each of these parts is a database partition. You can assign multiple partitions to a single physical machine. These are called ‘logical partitions’ and they share the resources of the machine.When a database is partitioned, you split your database into different independent parts, each consisting of its own data, configuration files, indexes and transaction logs. Each of these parts is a database partition. You can assign multiple partitions to a single physical machine. These are called ‘logical partitions’ and they share the resources of the machine. Db2DPFSQLNetTest test reports the availability and responsiveness of the server, and collects statistics pertaining to the traffic into and out of the database server.

The default parameters associated with this test are:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, specify the HOST for which this test is to be configured.

  • In the PORT text box, specify the port at which the target host is listening. The default port is 50000.

  • To monitor Db2 UDB database server, the eG agent should be configured with the credentials of a user with any of the following privileges SYSADM or SYSCTRL or SYSMAINT or SYSMON. Specify the name of user in the USER text box.

  • The eG agent should be configured with the credentials of a user to monitor Db2 UDB database server. Specify the password of the specified user in the PASSWORD text box.

  • Confirm the Password by retyping it in the CONFIRM PASSWORD text box.

  • The test uses a database on the monitored Db2 UDB server. Specify the name of the database in the DATABASE text box.

  • Select the query to execute in the QUERY text box. By default, this is set to selectTABSCHEMA,TABNAME,TYPE,COLCOUNT,KEYCOLUMNS,KEYINDEXED,KEYUNIQUE FROM, SYSCAT.TABLES WHERE TYPE=‘T’

  • Specify the additional list of databases that you wish to monitor in a comma-seperated list in the ADDITIONAL DATABASES text box. By default this is set to None.

  • To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.

    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.