|
Problem IC91703
|
Status: Closed |
DB2PD -LATCHES OR -APINFO MAY RETURN NO DETAILS IF HOST HAS MULTIPLE ENTRIES IN THE /ETC/HOSTS FILE |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When the /etc/hosts file contains multiple entries for the same
host, only the last entry is validated/used. If that particular
entry is invalid then the utility will return no output.
This can cause db2pd -latches or -apinfo to return no
information or no latch waiters/holders.
$db2pd -latches
Database Partition 4294967295 -- Active -- Up 0 days 20:55:30 --
Date
08/01/2012 11:20:53
Latches:
Address Holder Waiter Filename LOC LatchType
No latch holders.
No latch waiters. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to inclusive fixpack *
**************************************************************** |
| Local Fix: |
One of the following options can be used as a temp workaround:
1. db2pd "-dbp 0" option can be used in the db2pd command. For
example: "db2pd -dbp 0 -latches"
or
2. Set the registry variable DB2NODE=0, for example ("export
DB2NODE=0")
or
3. Remove invalid entries for the host from the /etc/hosts file. |
| available fix packs: |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 21.04.2013
02.10.2013
02.10.2013 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.3
|
 |
| 10.1.0.3
|
|
