|
Problem IC97734
|
Status: Closed |
DB2START RETURNS SQL6030N START OR STOP DATABASE MANAGER FAILED. REASON CODE "4". |
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Very specific set of entries in db2nodes.cfg creates a situation
where db2nodes.cfg file is not read correctly, resulting in
SQL6030 reason code 4.
The error will occur when the resulting structure for the
db2nodes.cfg is an exact multiple of 4K. The size of the in
memory structure can be viewed by collecting a db2trc of the
failing db2start.
35317 data DB2 UDB oper system services
sqloReadDb2nodesWithHandle cei (3.3.15.453.2.250)
pid 15597704 tid 1 cpid -1 node -1 probe 250
bytes 16392
Data1 (PD_TYPE_DEFAULT,16384) Hexdump:
0000 4000 0095 0094 0000 EA60 0000 EA68
..@........`...h
0000 0095 0000 0000 0000 0000 0000 0000
................
Note the size of the data dump for Data1. It is 16384, which is
an exact multiple of 4K. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Version 10.5 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
Add or remove any netname field from the db2nodes.cfg file |
| available fix packs: |
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows
|
| Solution |
First fixed in Version 10.5 Fix Pack 4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 18.11.2013
09.09.2014
09.09.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.5.0.4
|
 |
