How to create Tools Catalog database
The tools catalog database contains task information created by the Task Center and the Control Center.
These tasks are run by the DB2 administration server’s scheduler. The scheduler is a specific piece of the DB2 administration server that acts as an agent to read the tools catalog database and runs the tasks at their respective times.
To create the DB2 tools catalog tables (in an existing or a new database), you must issue the CREATE TOOLS CATALOG command. The database must be local and the command is not valid on a DB2 client. You need SYSADM or SYSCTRL authority as well as the DASADM authority to be able to update the DAS server configuration.
To create a tools catalog with the name cc on a new database with the name toolsdb, you issue:
information. The JVM information is specified using the jdk_path DB2 DAS configuration
parameter.
The Control Center and Task Center access the tools catalog database directly from the
client. The tools catalog database therefore needs to be cataloged at the client. The
Control Center provides the means to automatically retrieve information about the tools
catalog database and to create the necessary directory entries. The only communication
protocol supported for this automatic cataloging is TCP/IP.
To update the DAS to work with the tools catalog database, use the following command:
If the tools catalog database is remote to the DB2 Administration server, you need to issue db2admin setschedid sche-user/sched-password to establish the logon account used by the scheduler to connect to the tools catalog database.
There are two DAS configuration parameters used to enable notifications by the scheduler
or the Health Monitor:
E-mail and pager notifications from the DB2 administration server can be local or remote. A contact list is required to ensure that notifications are sent to the correct hostname. When the Admin Server is created at a later point in time, you must catalog it in order to enable the Control Center to be known by the correct hostname. The catalog command is similar to the catalog local node command:
To create the DB2 tools catalog tables (in an existing or a new database), you must issue the CREATE TOOLS CATALOG command. The database must be local and the command is not valid on a DB2 client. You need SYSADM or SYSCTRL authority as well as the DASADM authority to be able to update the DAS server configuration.
To create a tools catalog with the name cc on a new database with the name toolsdb, you issue:
db2 create tools catalog cc create new database toolsdbTo create a tools catalog using an existing database toolsdb (which must be deactivated and activated after creation), issue:
db2 create tools catalog use existing database toolsdb forceThe DAS scheduler requires a Java virtual machine (JVM) to access the tools catalog
information. The JVM information is specified using the jdk_path DB2 DAS configuration
parameter.
The Control Center and Task Center access the tools catalog database directly from the
client. The tools catalog database therefore needs to be cataloged at the client. The
Control Center provides the means to automatically retrieve information about the tools
catalog database and to create the necessary directory entries. The only communication
protocol supported for this automatic cataloging is TCP/IP.
To update the DAS to work with the tools catalog database, use the following command:
db2 update admin cfg using toolscat_inst INSTANCENAME toolscat_db DBNAME
toolscat_schema SCHEMANAME
If the tools catalog database is remote to the DB2 Administration server, you need to issue db2admin setschedid sche-user/sched-password to establish the logon account used by the scheduler to connect to the tools catalog database.
There are two DAS configuration parameters used to enable notifications by the scheduler
or the Health Monitor:
- smtp_server is used to identify the Simple Mail Transfer Protocol (SMTP) server used by the scheduler to send e-mail and pager notifications as part of task execution completion actions as defined through the Task Center, or by the Health Monitor to send alert notifications.
- contact_host specifies the location where the contact information by the scheduler and health monitor for notification is stored (for example, the DAS server’s TCP/IP hostname).
E-mail and pager notifications from the DB2 administration server can be local or remote. A contact list is required to ensure that notifications are sent to the correct hostname. When the Admin Server is created at a later point in time, you must catalog it in order to enable the Control Center to be known by the correct hostname. The catalog command is similar to the catalog local node command:
db2 catalog admin local node system <hostname> ostype <ostype>