suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT17993 Status: Closed

TAKEOVER CAN TIMEOUT DUE TO WAITING ON NEW CONNECTIONS TO AUTHENTICATE
WHEN /ETC/GROUP FILE IS VERY LARGE

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
An HADR Takeover can timeout due to waiting for new connections
to authenticate and look up their group values in /etc/group at
the OS level.  The delay is caused by a large number of groups
in the /etc/group file.

During takeover processing pooled agents cannot disassociate
from the database because they are queued up for authentication
on a new connection request and slowly going through the
security plugin used to fetch group information.  Agents are
serialized through this fetching due to a latch that is obtained
and hence get queued up.

The fix is to have such agents to drop out of the security
plugin immediately upon discovering a TAKEOVER is occurring.
This means agents will drop out of the plugin immediately (once
they obtained the latch) and skip fetching any group information
and therefore shouldn't spend much time in the security plugin.
This will allow all agents to be able to disassociate from the
database in a reasonable amount of time.
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to DB2 10.5 Fix Pack 8                               *
****************************************************************
Local Fix:
Workaround by setting the DB2_ALTERNATE_GROUP_LOOKUP registry
variable.  This causes a different API call to be used (on AIX,
getgrset) and avoid the
long wait on /etc/group.  Additional information about this
recommendation can be found here:
http://www-01.ibm.com/support/docview.wss?uid=swg21455469
Solution
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : IT11286 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
16.11.2016
13.03.2017
13.03.2017
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)