Troubleshooting Guide

Control Center

The Control Center is used to manage systems, DB2 Universal Database instances, DB2 for OS/390 subsystems, databases, and database objects, such as tables and views. In the Control Center, you can display all of your systems, databases, and database objects and perform administration tasks on them.

If you have problems starting the Control Center, see "Control Center Installation and Configuration." You can find this document in the file x:\sqllib\cc\prime\readme.htm where x is the drive where you installed DB2.

The Control Center Administration Engine Log (db2cc.log) records information about the errors generated while using the Control Center. The log is always active while the Control Center is active. The log file is kept in the home directory of the executable that invokes the Control Center, that is, in the bin subdirectory of the sqllib subdirectory. The log can be viewed and updated using an ASCII file editor.

The log file records the error message type, a time stamp, a process identifier (PID), a thread identifier (TID), and an SQL error message. The process ID and the thread ID are used to identify the operating system that generated the log. By combining information from the log files with the Control Center trace information, the DB2 Service and Support personnel are able to determine which Control Center task caused the error. This information is only of use to the DB2 Service and Support personnel.

See Taking Other Traces for more information on taking a Control Center trace.

If you encounter other problems using the Control Center, you can search for troubleshooting tips using the search utility for DB2 online information.

Using Search Utility for DB2 Online Information

Troubleshooting tips for the Control Center are available through the search utility for DB2 online information. To use the Search utility, perform the following steps:

Start the Control Center. (There are different ways to do this depending on your operating system. For example, you could:
- Use the db2cc command on the command line
- (On OS/2) Select the Control Center icon from the DB2 folder
- (On Windows NT) Select Start -->Programs -->DB2 for Windows NT -->Control Center.
Press F1 to display online help.
Click Search near the top of the online help. This opens the DB2 online information search form.
Type troubleshooting in the search field.
Select Online help from the information list.
Click the Search button. This will open a list of search results.
Select a topic to view troubleshooting tips.

Troubleshooting Tips

This section describes how to deal with some frequently encountered problems faced by users working with the Control Center.

Online Help Not Coming Up on OS/2

Symptom: When you press F1 or press the Help button on a window, the online help does not come up, or you get an error message and the online help does not come up.
Action: Ensure that the subdirectory that contains the Netscape executable (by default in <drive>\netscape\program\netscape.exe) is included in your PATH environment.

Online Help Not Coming Up on UNIX Based Systems

Symptom: When you press F1 or press the Help button on a window, the online help does not come up, or you get an error message and the online help does not come up.
Action: Ensure that Netscape 4.51 is installed, and that the directory that contains the Netscape script file (for example, /usr/bin) is included in your PATH environment variable.

SQL4400N Received When Attempting Commands in the Control Center

Symptom: The error message SQL4400N is received when attempting to run certain commands through the Control Center. As an example, the BACKUP command may cause this error.
Possible Cause: The user ID being used does not have the correct authority on the DAS instance.
Action: The user must manually attach using a user ID which has the correct authority on the DAS. Validation of the manual attach does not get validated immediately. The Control Center stores the authority and uses it when attempting a particular task (like a backup).

DBA4745N Received When Attempting to Administer a EEE AIX V5.2 Server

Symptom: The error message DBA4745N is received when attempting to administer a DB2 UDB Enterprise - Extended Edition for AIX Version 5.2 server from the Control Center on the client.
Possible Cause: The db2ccmlst process run by the DB2AS user ID was not started; and the db2ccmsvr port was not defined in the services file on the server.
Action: A port for graphical tool administration with an EEE system must be allocated. The db2ccmlst process must be started on each node.

[ Top of Page | Previous Page | Next Page ]