IBM Support

Error: The database manager resources are in an inconsistent state, when using ClearQuest with DB2

Technote (troubleshooting)


Problem(Abstract)

This technote provides a possible solution to the following error in IBM® Rational® ClearQuest® when using IBM® DB2® database:
"The database manager resources are in an inconsistent state. The database manager may have been incorrectly terminated or another application may be using system resources in a way which conflicts with the way the database manager uses system resources. System resource cleanup may be required."

Cause

The request failed because the database manager resources are in an inconsistent state. This can occur if:

  • DB2 was incorrectly terminated (on UNIX® - based systems, for example, this may occur if the processes were terminated with the "kill" command, rather than the stop database manager command).
  • Another application or user may have removed the database manager resources (on UNIX-based systems, for example, a user with sufficient privilege may have accidentally removed an Interprocess Communication (IPC) resource owned by the database manager, using the "ipcrm" command).
  • Another applications use of system resources conflicts with the database manager's use of system resources (on UNIX-based systems, for example, another application may be using the same keys that the database manager uses for creating IPC resources).
  • Another instance of the database manager may be using the same resources. This could occur on UNIX-based systems if the two instances are on different file systems and the sqllib directories happen to have the same i-node (i-nodes are used to get the IPC keys).

Resolving the problem

Resource cleanup may be required:

    • Remove all the database manager processes running under the instance id (on UNIX-based systems, you can use "ps -eaf -u <instance id> | grep db2" to list all the database manager processes running under the instance id, and the "kill -9 <process id>" command to remove them).
    • Ensure that no other application is running under the instance id, and then remove all resources owned by the instance id (on UNIX-based systems, you can use the "ipcs | grep <instance id>" command to list all IPC resources owned by the instance id, and the "ipcrm -[q|m|s] <id>" command to remove them).
      1. If there is another instance of the database manager running, and it is on a different filesystem, and an i-node conflict is suspected, then change the i-node by the following steps:
      2. Create another directory at the same level as sqllib
      3. Move everything from under sqllib to the new directory
      4. Delete sqllib
      5. Rename the new directory to sqllib
      6. Restart the database manager instance.

Note: This requires the assistance of the DB2 administrator who set up the databases.



Historical Number

146546995

Document information

More support for: Rational ClearQuest
Database Configuration/Connectivity - DB2

Software version: 7.0, 7.0.0.1, 7.0.0.2, 7.0.1, 2002.05.00, 2002.05.20, 2003.06.00, 2003.06.12, 2003.06.13, 2003.06.14, 2003.06.15, 2003.06.16

Operating system(s): Platform Independent

Reference #: 1131509

Modified date: 30 July 2007