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

DB2IDROP MIGHT CAUSE SEGFAULT IN DB2HAVEND32 PROCESS, IF ISSUED ON THE
SYSTEM WHERE TSA IS NOT INSTALLED.

Produkt:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problembeschreibung:
When db2idrop is performed on the system where TSA is not 
configured, db2havend32 process might have segfault. 
The default install directory of TSA is /usr/sbin/rsct/, and if 
TSA is not installed, the directory does not exist. 
 
In the syslog, the following entry might be recorded. 
 
Example of Linux platform: 
db2havend32[12713]: segfault at 0 ip 0000000008071c12 sp 
00000000ffffb71c error 4 in db2havend32[8048000+1c0000] 
 
Depending on the system settings, core file might be generated. 
 
This problem does not occur on Windows platforms.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All who use the system where TSA is not installed. (TSA is   * 
* installed by default.)                                       * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to Version 9.7 Fix Pack 10                           * 
****************************************************************
Local-Fix:
As long as db2idrop runs successfully with DBI1070I, just ignore 
the segfault.
Lösung
Problem was first fixed in DB2 UDB Version 9.7 Fix Pack 10
Workaround
keiner bekannt / siehe Local-Fix
Bug-Verfolgung
Vorgänger  : APAR is sysrouted TO one or more of the following: IC98882 
Nachfolger : 
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
24.12.2013
24.11.2014
24.11.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
9.7.FP10
Problem behoben lt. FixList in der Version
9.7.0.10 FixList