|
Problem IT04590
|
Status: Closed |
FP4 ONLY: DB2STOP WILL RETURN SQL6037N IF DB2_NUM_CKPW_DAEMONS=0. |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
The db2stop command returns timeout error as below when db2set
DB2_NUM_CKPW_DAEMONS=0.
$ db2stop
2014-09-10 14:25:22 0 0 SQL6037N START or STOP DATABASE
MANAGER timeout value was reached.
SQL6037N START or STOP DATABASE MANAGER timeout value was
reached.
Once this error is occurred, subsequent db2stop fails with
SQL1072C.
$ db2stop
2014-09-10 14:25:58 0 0 SQL1072C The request failed
because the database manager resources are in an inconsistent
state. The database manager might have been incorrectly
terminated, or another application might be using system
resources in a way that conflicts with the use of system
resources by the database manager.
SQL1072C The request failed because the database manager
resources are in an inconsistent state. The database manager
might have been incorrectly terminated, or another application
might be using system resources in a way that conflicts with the
use of system resources by the database manager.
You will see the following entry in your db2diag.log.
2014-09-10-14.15.23.306454+540 E21227A445 LEVEL: Error (OS)
PID : 14614764 TID : 258 PROC : db2ckpwd 0
INSTANCE: db2inst1 NODE : 000
HOSTNAME: host1
EDUID : 258 EDUNAME: db2wdog 0 db2inst1
FUNCTION: DB2 UDB, oper system services, sqloEDUPost, probe:10
MESSAGE : ZRC=0x83000001=-2097151999
CALLED : OS, -, unspecified_system_function
OSERR : EPERM (1) "Not owner" |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* V10.5 FP4 only *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 UDB version 10.5 fixpack 5. *
**************************************************************** |
| Local Fix: |
Unset DB2_NUM_CKPW_DAEMONS variable as below:
1. Stop the instance.
$ db2_kill
2. Unset DB2_NUM_CKPW_DAEMONS variable, then start the instance.
$ db2set DB2_NUM_CKPW_DAEMONS=
$ db2start |
| Solution |
Problem was first fixed in DB2 UDB Version 10.5 FixPack 5. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.09.2014
22.12.2014
22.12.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.5
|
 |
