Information Catalog Manager Administration Guide

Solving problems

The Information Catalog Manager gives you some resources to help you solve problems. These resources are:

• Online information and messages.
• A utility for resetting a logged-on administrator user ID.
• A procedure for restoring your information catalog using backed up data.
• Information Catalog Manager trace file.

Using online information and messages

The Information Catalog Manager provides extensive online information and messages to help you solve problems. When you or your users receive a message, use the online help first to resolve the problem.

You can find help for Information Catalog Manager messages and explanations, and extended codes for Information Catalog Manager reason codes in the DB2 Universal Database Message Reference. The extended codes are also described in the Information Catalog Manager Programming Guide and Reference.

Resolving administrator logon problems

If the Information Catalog Manager closes unexpectedly while you are working on your information catalog, you must reset any administrator user ID that was logged on when the problem occurred. If you try to log on without resetting the administrator ID, you will get an error message telling you that another administrator is already logged on.

From an MS-DOS command prompt, enter the command:

X:\Program Files\SQLLIB\BIN\CLEARKA

where X is the drive where the DB2 Universal Database is installed.

When prompted, enter the name, user ID, and password for the information catalog, separated by blanks. For example:

ICMSAMP longods secret

Then open your information catalog again.

If your information catalog is stored in a DB2 UDB for OS/390 Version 4.1 database and the Information Catalog Manager is forced to close because communication with the database is lost, you might need to increase the value of the DB2 UDB for OS/390 system parameter IDTHTOIN.

Recovering Information Catalog Manager components and data

If you experience a hardware or software failure, you can lose your information catalog database, your descriptive data, and parts of the component. If you backed up the necessary components and data, you can restore your system, the Information Catalog Manager, and data.

If a system failure occurs, perform the following steps after the database server's hard disk is restored and before your users access the information catalog:

1. Recover your database management system and reinstall the Information Catalog Manager, as necessary.
2. Restore the information catalog databases by using your backup files.
   • If your backup file is a database image copy:
     1. See the documentation for your database management system for information on restoring your information cataloginformation catalog database.
     2. Bind the restored databases to the Information Catalog Manager by issuing the SQLBIND command from a command prompt. Table 15 indicates the bind files that you should use for the Information Catalog Manager component that you are restoring.
        

        Table 15. Information Catalog Manager Version 5.2 bind files
        

        If you are using:	Use these bind files:
        Information Catalog Manager for Windows Administrator	FLGNJKA1.BND FLGNJKW1.BND FLGNJKX1.BND
        Information Catalog Manager for Windows User	FLGNJKW1.BND FLGNJKX1.BND

        Specify the following parameter values for the bind files:

        Datetime format

        ISO

        Grant execute privilege

        PUBLIC

        Row blocking

        ALL (does not apply to FLGNJKA0.BND or FLGNJKA1.BND)

   • If your backup file is an Information Catalog Manager tag language file that is produced by the Information Catalog Manager export process:
     1. Define your information catalog again using the Initialize Information Catalog window.
     2. Import the tag language file to restore your data.

Using trace files for problem diagnosis

The Information Catalog Manager automatically creates a file, called a trace file, that can help you diagnose problems.

The trace file is created each time you log on to the Information Catalog Manager. It includes the time and date you started the Information Catalog Manager, product version, service level, and information about what is happening in the Information Catalog Manager while it is running.

The Information Catalog Manager gives the trace file the name of the information catalog you are using plus an extension of TRC. The Information Catalog Manager for Windows places the trace file on the drive and path that are specified by the DGWPATH environment variable. (On Windows NT, you can find this variable on the Control Panel under Environment Variables. On Windows 95, you can find this variable in your AUTOEXEC.BAT file.) For example, if you are using the DGIVP information catalog, the trace file is named DGIVP.TRC on the drive and path that are specified by the DGWPATH environment variable.

The Information Catalog Manager overwrites the trace file each time you log on.

Important

If the Information Catalog Manager unexpectedly closes, immediately go to a command prompt and rename the trace file before you call IBM Software Support. Otherwise, when you restart the Information Catalog Manager you will overwrite the trace file and clear the records that you need to explain your problem.

You can trace Information Catalog Manager activities at five levels. The default level is 0. At this level, the Information Catalog Manager records only error messages that you see on the screen. If the Information Catalog Manager encounters a severe error, it automatically increases the trace level to record the error number and any associated extended codes. You can look up the error numbers and some extended codes in the online book DB2 Universal Database Message Reference. An extended code is an additional explanatory code that provides more information about an error in a specific situation. However, the trace file can contain extended codes for the Information Catalog Manager or Structured Query Language (SQL) statements. You might have to look in the associated message reference for additional information.

You might need higher trace levels to help IBM Software Support diagnose a problem. To do so, you must start the Information Catalog Manager from a command prompt and use the /TRACE option. See Importing a tag language file from the command line for more information.

Figure 21 shows an example of a trace file.

Figure 21. Trace file showing Information Catalog Manager reason and extended codes

******************************************************* * Information Catalog Manager Trace File * * Date and Time : Fri Jan 21 10:15:38 2000 * Product Version : V7.1 * ******************************************************* Starting Trace... >> PID/TID = 319 / 320" Starting Trace Level: 0 FLGGETReg >> PID/TID = 319 / 320" New Reason Code: 1008 --------------------

What to do with trace files:

1. Look up error messages in the DB2 Universal Database Message Reference.
2. Follow the actions that are recommended in the book.
3. If you see an extended code, look it up in the following documentation:

   For SQL codes and Information Catalog Manager extended codes see the DB2 Universal Database Message Reference. The extended codes are also described in the Information Catalog Manager Programming Guide and Reference.

In Figure 21, the New Reason Code: 1008 specifies that the FLGGETReg API could not retrieve an icon file.