IBM Books

Quick Beginnings for DB2 Extended Enterprise Edition for UNIX


Administering Databases with DB2 Tools

You can administer local databases on DB2 servers by using the command line processor. You can also perform database administration tasks remotely from an OS/2, Windows 95, or Windows NT client by using the DB2 administration tools. Use the Control Center to perform administration tasks such as configuring, backing up and recovering data, managing directories, scheduling jobs, and managing media, all from a graphical interface.

In a partitioned database system, you must also have a listener daemon that runs on each machine in the instance. This daemon is called db2cclst, and is used by all instances that are on the machine. The Control Center uses the listener daemon to retrieve status, connection, and snapshot information from each database partition server. The daemon is not associated with a specific instance; rather, it functions as a global server for the machine.

The listener daemon requires a predefined named port. The named port must be called db2ccmsrv and must be defined in the /etc/services file on every machine. The named port can be assigned any unused port number, but the same number must be used for all machines.

You should set up the db2cclst daemon to start at machine reboot time. You can do this by changing the /etc/inittab file as follows:

For AIX:
Run the following command:
   mkitab "db2cclst:2:once:DASINSTHOME/sqllib/bin/db2cclst"

For Solaris:
Edit the /etc/inittab file and add the following:
   cl:234:once:DASINSTHOME/sqllib/bin/db2cclst

where DASINSTHOME is the home directory of the Administration Server.
Note:If you are using DB2 Extended Enterprise Edition for AIX, for serviceability reasons, you should not enable the inittab autorestart option for the db2cclst daemon.

To see if the daemon is running, issue the following command:

   ps -aef | grep db2cclst

Error information for the db2cclst daemon is returned to the syslog file. Errors are written to this file, instead of the db2diag.log file, because the daemon runs independent from the instance.

Managing Databases Using the Control Center

The Control Center displays database objects (such as database partitions, table partitions, and packages) and their relationships to each other. Using the Control Center, you can manage a local database server or multiple remote DB2 servers and the database objects within them, all from a single point of control. See Figure 3 for an example of the main Control Center window. You can choose to install the Control Center on OS/2, Windows 95, or Windows NT workstations.

DB2 Universal Database Extended Enterprise Edition distinguishes between single-partition and multipartition database systems via Discovery. Discovery uses the DB2SYSTEM, DB2ADMINSERVER, and DB2COMM registry values. For more information on these registry values, see Chapter 21. "Controlling Your DB2 Environment".

Figure 3. Control Center Main Window


A screen capture of the Control Center.

From the Control Center, you can perform operations on database objects. These operations include:

For more information on objects in a partitioned database system, see Chapter 3. "Introduction to DB2 Extended Enterprise Edition".

You can also control database manager environments (which are known as DB2 instances) by:

The Control Center provides additional features to assist you in managing your DB2 servers:

Figure scriptce not displayed.

Use the Command Center to enter DB2 commands and SQL statements in an interactive window and see the execution result in a result window. You can scroll through the results and save the output to a file.

Figure commandc not displayed.

Use the Script Center to create mini applications called scripts, which you can store and invoke at a later time. These scripts can contain DB2 commands, SQL statements, as well as operating system commands. Scripts can be scheduled to run unattended. These jobs can be run once or set up to run on a repeating schedule; a repeating schedule is particularly useful for tasks like backups.

Figure journall not displayed.

Use the Journal to view all available information about jobs that are pending execution, executing, or that have completed execution. You can also view the recovery history log, the alerts log, and the messages log; and review the results of jobs that are run unattended.

Figure alertcen not displayed.

Use the Alert Center to monitor your system for early warnings of potential problems or to automate actions to correct problems discovered.

Figure toolsset not displayed.

Use the Tools Setting to change the settings for the Control Center, Alert Center, Replication, and Node Status.

You can run these functions from the Control Center toolbar or from icons in the Administration Tools folder.

You can install the following options for the Control Center:
DB2 Performance Monitor Use the DB2 Performance Monitor to monitor the performance of your DB2 system. You can monitor activity using snapshots of data over a period of time or using data for a particular event. See "Monitoring Databases Using DB2 Performance Monitor" for more information.
Visual Explain Use Visual Explain to graphically analyze and tune SQL statements and to analyze query access plans. See "Viewing SQL Access Plans Using Visual Explain" for more information.

You can find additional information in the Administration Getting Started guide or in the Control Center's online help.

Understanding the Administration Server

The Administration Server satisfies requests from the DB2 Administration Tools. It enables the DB2 Administration Tools to start, stop, catalog, and configure instances of the DB2 server. The Administration Server must reside on every DB2 server that you want to administer and detect. For more information, see Chapter 18. "Using the Administration Server".

Monitoring Databases Using DB2 Performance Monitor

With the DB2 Performance Monitor, you can:

You can choose to monitor snapshots or events. The Snapshot Monitor allows you to capture point-in-time information at specified intervals. The Event Monitor allows you to record information over the duration of an event such as a connection.

Snapshot Monitoring Considerations

The snapshot monitoring function in the Control Center is split between the administrative client and the database server. A separate process is started on behalf of the user to gather snapshot information on the server and return the data to the client. This separate server process runs locally on the server and therefore it must be locally authenticated; because of this, the user must have a valid user ID and password on each server that is monitored. If the server is configured for SERVER authentication, this is transparent to the user. If the server is configured for CLIENT authentication, the user will be prompted for a user ID and password that will be authenticated locally on the server.
Note:DCE authentication for snapshot monitoring is not supported at this time.

You can find additional information in the Administration Getting Started guide or in the online help for DB2 Snapshot Monitor.

Viewing SQL Access Plans Using Visual Explain

Visual Explain helps database administrators and application developers to:

You can find additional information in the Administration Getting Started guide or in the online help for Visual Explain.

Managing Communications on the Server

The Control Center allows you to view, update, and reset server protocol settings. These functions are accessed by clicking with the right mouse button on an instance and selecting the Setup communications option from the pop-up menu. This tool helps database administrators to:

You can find additional information in the online help for the Control Center.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]

[ DB2 List of Books | Search the DB2 Books ]