Configuration issues

During configuration, you might experience some problems with the configuration programs. There are some extra debugging steps that can help you and IBM® Software Support determine the cause of these problems.

Database configuration

Because there are so many variables at play during configuration, errors can occur. Some of the factors that can affect this option are:

Which platform, and which version of the operating system, you are using.
Which version of DB2®, and which fix packs are installed for it.
Note: DB2 comes in a wide variety of packages: Personal Edition, Enterprise Edition, Extended Enterprise Edition, and others. Many of these packages are supported across several versions of DB2, and each version can have several available fix packs.
Amount of disk space available in affected drives and partitions.
Third-party software that alters commonly used environment variables.

If the database configuration fails, the bottom-line question is, "What failed, and how do I fix it?" The following sections describe sources of output that can be used to debug configuration problems.

Standard sources of output

There are several "standard" sources of information available:

The output on the screen
All of the configuration programs are either started from a console command-line prompt or open a background console. As the database configuration progresses, status messages (and limited error messages) are displayed in the associated console window. If a problem occurs, copy these messages to the system clipboard and then save them in a file for the IBM Software Support teams.
DB2 log files
If the error is a direct error from DB2, then DB2 often creates message or error files (in the /tmp directory on AIX®, Linux, and Solaris platforms). If you have a database configuration problem on an AIX, Linux, or Solaris system, examine all of the files in the /tmp directory that were created around the time of the attempted configuration.

On Windows systems, examine any DB2 error logs in your DB2 installation directory. The error logs are under the directory that is named for the instance you were trying to configure. For example, if you were trying to create an instance and database named ldapdb2, and if your DB2 was installed in D:\sqllib, examine the files in the D:\sqllib\ldadb2 directory if it exists. In particular, look for and examine the file named db2diag.log in that directory.

Creating advanced debug output

See Server debug mode for information about using debugging tools that are provided.