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 IT10256 Status: Geschlossen

DB2 pureScale: RSCT APAR IV74148: BACKLEVEL RESOURCE MANAGERS MAY HANG
UNDER ERROR CONDITIONS

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
This DB2 APAR has been opened to reference an RSCT APAR that 
impacts pureScale. 
 
Please refer to 
http://www-01.ibm.com/support/docview.wss?uid=isg1IV74148 
 
The impact to DB2 is : 
 
DB2 pureScale V9.8 FP5, V10.1 FP5, and V10.5 FP6 are all current 
pureScale versions using TSA MP 3.2.2.8 or less, which ships 
with 
RSCT 3.1.5.5 or less. TSA MP's resource managers such as 
IBM®.RecoveryRM or IBM.GblResRM , as a result, were built with 
pre- 3.2 RSCT and therefore are exposed to this RSCT APAR when 
executing on AIX system using RSCT 3.2. AIX 7.1 TL3 SP and AIX 
6.1 TL9 SP4. Both of these AIX levels shipped RSCT 3.2.0.0. The 
net result is that customers using the defined DB2 pureScale 
versions are exposed to this RSCT APAR when running on  AIX 7.1 
TL3 SP4 and AIX 6.1 TL9 SP4 or higher, or have updated their 
RSCT 
level to 3.2.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* See Error Description                                        * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* See Local Fix                                                * 
****************************************************************
Local-Fix:
Reboot server.
Lösung
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
22.07.2015
20.01.2016
20.01.2016
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.7 FixList