This chapter describes how to install DB2 Query Patroller server and agent components.
![]() |
If you are migrating from a previous version of this product refer to the
"Migration" appendix for instructions before proceding with
installation.
|
Installation of DB2 Query Patroller on a database server system consists of installing the server component on one system node and installing the agent on one or more system nodes.
On a single-processor or symmetric multiprocessing (SMP) system, the server component and agent components run on the same computer. On a massively parallel processing (MPP) system or a cluster of computers, the server component runs on one node and the agent may be run on several nodes, including the DB2 Query Patroller server node.
![]() |
There are a number of configuration steps required to setup the DB2 Query
Patroller server. It is recommended that you use the DB2 Installer
(db2setup) program, but if you want to use the operating systems native
installation tools, see the "Manual Installation" appendix.
|
DB2 Query Patroller requires a configured DB2 Universal Database Extended Enterprise Edition (DB2 UDB EEE) instance to work. It is recommended that you first create and set up a DB2 UDB EEE instance to be used with DB2 Query Patroller before you begin installation.
The installer program first checks the node you are installing on for existing DB2 Query Patroller components. If a component is already present on the node, that component will not be available for installation.
Server Installation
You can use the installer program to install the DB2 Query Patroller code and create a new DB2 UDB EEE instance. The configuration of this instance cannot be done using the DB2 Installer program. Refer to the DB2 Administration Guide for the necessary configuration steps for a DB2 UDB EEE instance. Once the instance has been configured, you may use the DB2 Installer to set up the DB2 Query Patroller server, or you can manually set up the server using the dqpsetup command (refer to the "Manual Installation" appendix for details). Using the DB2 Installer is recommended.
If you are using an existing instance of DB2 UDB EEE, you will be asked to provide information for a database, a nodegroup, and two tablespaces. The installer program will use this information when performing the DB2 Query Patroller server installation tasks listed below. If you are creating a new instance, you will not be prompted for this information.
Note: | The installer does not create this tablespace for you. You must create this tablespace manually. |
Note: | If an IWM schema is already present you can choose to use this schema or replace it with a new one. |
Agent Installation
The DB2 Query Patroller agent can be installed on any node used by the DB2 UDB EEE instance. The installer preforms the following tasks when installing an agent component:
Before you begin installation, be sure you have the following items and information:
![]() |
When you use the DB2 Installer program, you should be aware of the following:
|
The Table below will help you determine the values required to install DB2
Query Patroller. Before proceeding with the installation, complete the
Your Value column in the table. For descriptions of the
parameter values see Parameter Definitions.
Description | ||
Information Required for DB2 Installer | Default Value | Your Value |
---|---|---|
Instance Name |
|
|
Database Name |
|
|
Nodegroup Name |
|
|
Node Number |
|
|
Tablespace Name |
|
|
Tablespace Path |
|
|
Result Tablespace Name |
|
|
TCP/IP Service Name | dqp1 |
|
TCP/IP Port Number | 55000 |
|
DMS Tablespace Size |
|
|
This is the DB2 UDB EEE instance name you want to set up as the DB2 Query Patroller server. In the installer, this parameter is referred to as the User Name.
Database
Name of the database to be used with the DB2 Query Patroller server.
Nodegroup
Name of the nodegroup that contains the tablespace for the DB2 Query Patroller server.
Node Number
Node number of a single node where the nodegroup is defined.
Tablespace
Name of the DB2 Query Patroller tablespace. The default type is an SMS tablespace. You can use a DMS tablespace by providing a value for the DMS Tablespace Size parameter.
Tablespace Path
Full path name of the DB2 Query Patroller tablespace.
Result Tablespace
This parameter is used to set an environment variable for the DB2 Query Patroller server and for user iwm. Providing this parameter does not create the result tablespace, it only sets up the environment. The system administrator must create this tablespace. DB2 Query Patroller will route results sets to this tablespace.
TCP/IP Service Name
This value should be the same for DB2 Query Patroller server and agent.
TCP/IP Port Number
This value should be the same for DB2 Query Patroller server and agent.
DMS Tablespace Size
The DMS Tablespace Size parameter is optional. Providing a value for this parameter indicates that you want to use a DMS tables space. If you are using a DMS tablespace the path you entered for the tablespace path must be a valid file path. The default is an SMS tablespace.
To mount DB2 Query Patroller using the DB2 Installer program, you must first mount the CD-ROM. Once you have mounted the CD-ROM, you can start the installation. There are two sets of instructions: Mounting on AIX Systems and Mounting on Solaris Systems. Choose the appropriate instructions.
To mount the CD-ROM on AIX, perform the following steps:
mkdir -p /cdrom
smitty storage
Note: | Device names for CD-ROM file systems must be unique. If there is a duplicate device name, you may need to delete a previously-defined CD-ROM file system or use another name for your directory. |
/cdrom.
smit mountfs.
![]() |
After mounting the CD-ROM file system, proceed to Step 3: Installation.
|
To mount the CD-ROM on Solaris, perform the following steps:
mkdir -p /cdrom/unnamed_cdrom
mount -F hsfs -o ro /dev/dsk/c0t6d0s2 /cdrom/unnamed_cdrom where /cdrom/unnamed_cdrom represents the CD-ROM mount directory.If the Volume Manager (void) is running on your system, the CD-ROM is automatically mounted as: /cdrom/unnamed_cdrom
![]() |
If you are mounting the CD-ROM drive from a remote system using NFS, the
CD-ROM file system on the remote machine must be exported with root
access. You must also mount that file system with root access on the
local machine.
|
After you mount the CD-ROM file system, use the DB2 Installer program to install DB2 Query Patroller.
To install DB2 Query Patroller, perform the following steps:
cd /cdrom
cd /cdrom/unnamed_cdrom
where /cdrom is the mount point of the CD-ROM drive on AIX, and /cdrom/unnamed_cdrom is the mount point of the CD-ROM on Solaris.
Press the Tab key to change the highlighted option and the Enter key to select or deselect an option. To go back to a previous window at any time select Cancel.
![]() |
If you are installing the agent component of DB2 Query Patroller, proceed
to the section entitled "Installing the Agent".
|
The DB2 Query Patroller set up program checks to see if DB2 Query Patroller components are already installed. If a component is already installed, the installation option for that component will not be available.
Note: | Installation of the server component automatically installs an agent component if an agent is not already present. |
![]() |
If you chose Create New Instance, skip to the section entitled
"Creating a New DB2 Instance."
|
The DMS Tablespace Size parameter is optional. Providing a value for this parameter indicates that you want to use a DMS tablespace. The default is an SMS tablespace.
Note: | Once the server has been installed, a result tablespace must be created. Refer to the result tablespace parameter definition in the section entitled Parameter Definitions for more information. |
Note: | An alternative to returning to the DB2 Installer is to continue the install manually by running the dqpcrt and dqpsetup command. Refer to the "Manual Installation" appendix for more information. |
The DMS Tablespace Size parameter is optional. Providing a value for this parameter indicates that you want to use a DMS tablespace. The default is an SMS tablespace.
Note: | Once the server has been installed, a result tablespace must be created. Refer to the result tablespace parameter definition in the section entitled Parameter Definitions for more information. |
Before you can install an agent, the server component must be installed. Also, the home directory of the DB2 UDB EEE instance on which the server is installed must be visible to the nodes you want to install the agent on.
Fill in the user name, service name and port number parameter fields with the information you recorded in Step 1: Identify and Record Parameter Values. Select OK.
Note: | The service name and port number you provide for the agent should be the same as the service name and port number of the DB2 Query Patroller server. |
Before performing the installation verification you must do the following:
Set up an instance environment and invoke the DB2 command-line processor. Run the start-up script as follows:
For a C shell enter: source . INSTHOME/sqllib/db2cshrc
For a C shell enter: source . INSTHOME/sqllib/dqpcshrc
The . INSTHOME variable represents the home directory of the instance.
Perform the following procedure to verify successful software installation:
iwm start all
![]() |
You can also log in on the DB2 Query Patroller server node and execute
iwm start server and then log in on the agent nodes and execute
iwm start agent.
|
iwm_submit -S "SELECT COUNT(*) FROM ibm.systables"
iwm_cmd
iwm stop
If DB2 Query Patroller does not start or the query does not run, look in the $IWMLOG directory. The syserr.log file may contain error messages related to the failed query. The /tmp/db2setup.log file contains a transcript of the installation. The contents of these files may be required by the DB2 Query Patroller support team to diagnose problems.