|
Problem IT04711
|
Status: Closed |
ISSUING MULTIPLE DB2START RESTART COMMANDS (USUALLY THROUGH DB2GCF) CAN LEAD TO A HANG |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
There is some retry logic in the db2start code that attempts to
re-read the db2nodes.cfg file if the initial read leads to an
error indicating a host-port pair is not unique. The retry logic
is in error and can lead to an endless loop that manifest as a
hang. The following db2diag.log entry should appear
multiple times.
2014-09-03-18.57.57.856681-240 I423890E782 LEVEL:
Severe
PID : 27066 TID : 139665254389536 PROC :
db2start
INSTANCE: bculinux NODE : 000
HOSTNAME: keiko09
FUNCTION: DB2 UDB, base sys utilities, sqleUpdateNodesFile,
probe:11268
MESSAGE : ZRC=0x870F0091=-2029059951=SQLO_ERR_DB2NODES_CFG
"db2nodes.cfg has error"
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -6030 sqlerrml: 1
sqlerrmc: 7
sqlerrp : SQLEUPNF
sqlerrd : (1) 0x00000000 (2) 0x00000000 (3)
0x00000000
(4) 0x00000000 (5) 0x00000000 (6)
0x00000000
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* User running v10.5 FP4 or lower *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 v10.5 FP5 or higher *
**************************************************************** |
| Local Fix: |
N/A |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.10.2014
25.01.2016
25.01.2016 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.7
|
 |
