home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC99208 Status: Closed

THE DB2V10_STOP.KSH SCRIPT DOES NOT KILL THE DB2SYSC PROCESS AS EXPECTED IN
THE CASE WHERE THE HOME DIRECTORY IS NOT ACCESSIBLE.

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In the case where LDAP authentication is used for the instance 
owner ID and the public network adapter is disabled, the 
instance owner's home directory may not be retrievable from the 
LDAP server. In this situation, the db2V10_stop.ksh script does 
not stop or kill the db2sysc process as it is intended to do. 
 
In an HADR/TSA configuration this can result in a split brain 
situation.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL users.                                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 V10.1 FixPack 4 or Later.                     * 
****************************************************************
Local Fix:
N/A
available fix packs:
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
First fixed in DB2 V10.1 FixPack 4.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC99307 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
06.02.2014
01.08.2014
01.08.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.4 FixList