home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC99307 Status: Geschlossen

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

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
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 db2V105_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-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL USERS of DB2 LUW V10.5                                   * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 LUW V10.5 FP3 or Later.                       * 
****************************************************************
Local-Fix:
N/A
verfügbare FixPacks:
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

Lösung
First fixed in DB2 LUW V10.5 FP3
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
11.02.2014
22.12.2014
22.12.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList