Quick Beginnings

Troubleshooting Information

For the latest service information on the Control Center, point your browser to http://www.ibm.com/software/data/db2/udb/db2cc

If you are having problems running the Control Center, check the following:

• Ensure the Control Center JDBC Applet Server (db2jd) is running.
• Verify that the server port number is correct.
• Check that the Control Center JDBC Applet Server is running under a user account that has SYSADM authority.
• Ensure that the Database Administration Server (DAS) is running on any DB2 Universal Database systems you are trying to administer by entering the db2admin start command. On UNIX-based systems, ensure that you are logged in as the DAS instance owner when you issue this command.

If you are having problems running the Control Center as an application, also check the following:

• Verify that the correct JRE is installed. See Table 13 for more information.

If you are having problems running the Control Center as an applet, also check the following:

• Verify that you are running a supported browser. See Table 13 for more information.
• Check your browser's Java console window for diagnostic and trace information for the Control Center.
• Make sure that the client browser does not have CLASSPATH set. To make sure CLASSPATH is not set, open a command window and enter SET CLASSPATH= then start your client browser from this command window. Also, note that if CLASSPATH is not set in a Windows NT or Windows 2000 environment, it may still get picked up from autoexec.bat from a Windows 9x installation on the same machine.
• Ensure that you are using the db2cc.htm file from the machine running the Control Center JDBC Applet Server.
• Remember that the Control Center works within the DB2 client's locale, and that the DB2 client is located at the Control Center JDBC Applet Server's location.