You can keep the Information Catalog Manager running smoothly by:
Your LAN or database administrator can help with most of these tasks, or you can refer to your database documentation for more information.
Regularly monitor the space available on the drive that contains the information catalog database, so that your organization doesn't run out of space as the information catalog grows. If this happens, the Information Catalog Manager can fail, and users will not be able to access the information catalog.
Also monitor the drive on the user's workstation that contains theWindows paging file. On Windows NT, you can view or edit this file:
If your information catalog is stored in a DB2 UDB for OS/2 database: Monitor the space available on the drive where DB2 UDB for OS/2 writes the log files it creates as it runs. If the drive does not have enough space for the log file, DB2 UDB for OS/2 can fail, closing the Information Catalog Manager. You might need to increase the number or size of these log files. To find out about or change the DB2 UDB for OS/2 log files, use the DB2 UDB for OS/2 tools.
If your Information catalog is stored in a DB2 Universal Database: See the online help for the DB2 Universal Database Control Center for information about changing the size of the log files.
When you use the Information Catalog Manager with a DB2 database, each person who accesses your information catalog is considered to be an agent that is using DB2. For information catalogs stored in DB2, the maximum number of idle agents must be higher than the default, which is 3. You should also increase the maximum concurrent agents.
To determine the current setting for idle and concurrent agents, enter the following command from the DB2 Command Line Processor:
get database manager configuration
To change the number of idle agents, enter the following command from the DB2 Command Line Processor: :
update database manager configuration use max_idleagents num
where num is the new number of idle agents.
To change the number of concurrent agents, enter the following command from the DB2 Command Line Processor: :
update database manager configuration use maxagents num
where num is the new number of concurrent agents.
To avoid losing your data in case of a hardware or software failure, establish a routine for backing up your information catalog databases, configuration information, and supporting software.
How frequently you back up these components depends on how frequently you make changes to your information catalog, and on your organization's policies for backups.
Your routine should include the following tasks:
If your information catalog database is on DB2 UDB for OS/390, the Information Catalog Manager uses two table spaces to store the data. You must back up both table spaces at the same time, because the data stored in these table spaces is interrelated.
Work with your LAN or database administrator to carry out your backup routine.
Backing up information catalog databases is crucial to ensure that you can recover your descriptive data if your databases become inconsistent or corrupt.
You can use either of two methods to back up the information catalog databases:
To maintain good performance of the database, it is a good idea to use the DB2 Universal Database RUNSTATS and REORG utilities. The RUNSTATS utility updates statistics in the DB2 UDB system catalog tables to help with the query optimization process. Without those statistics, the database manager might make a decision that can adversely affect the performance of an SQL statement. Use the REORG utility to help arrange the data in tables and indexes more efficiently. See the administration guide for your DB2 database system for the more information.
The Information Catalog Manager creates some configuration information on administrators' and users' workstations. The stored information consists of user-specific data, such as collections and saved searches for a particular information catalog. The Information Catalog Manager for Windows stores this information in the system registry.
Enter REGEDIT at an MS-DOS prompt to view the Windows system registry in the Windows Registry Editor.
To locate the working directory for the Information Catalog Manager for Windows, check the DGWPATH environment variable. (On Windows NT, you can find the environment variable on the Control Panel under Environment Variables. On Windows 95, you can find the environment variable in your AUTOEXEC.BAT file.) Then, search for the working directory name in the Registry Editor.
One branch, or folder, in the registry has the suffix INI for each information catalog that you access. One folder contains wildcard settings, the last user ID that logged on, and the last information catalog that was used. Your administrator folder also includes default export settings.
The online help for the Registry Editor explains how to import and export selected branches or how to restore the entire registry.
Whenever there are any major changes or additions to your information catalog, you should back up your, and all your users', Information Catalog Manager configuration information.