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

ABEND IN SQLAK_CALLBDRDAINPUT DUE TO MISALIGNED MEMORY ACCESS, LEADING TO
SIGBUS SIGNAL

Produkt:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problembeschreibung:
A crash with a SIGBUS error in client side code may occur with 
the following stack : 
 
  sqlak_callbDrdaInput 
  sqljrGenSqlDta 
  sqljrDrdaArCall 
  sqleuInvokeActivationRoutine 
  sqleuPerformServerActivationCheck 
  sqleUCappConnect 
  CLI_sqlConnect 
  SQLConnect2 
 
The problems happens when DB2 accesses a 2 byte integer in a 
non-2 byte aligned location. 
Most platforms will handle this gracefully and perform a byte by 
byte copy instead in the kernel but in some cases , this signal 
may be passed to user code and trigger the SIGBUS signal causing 
a failure in the process.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* all                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade the DB2 software to V10.1 Fix Pack 5 or higher (     * 
* This problem was so far only observed on the client side )   * 
****************************************************************
Local-Fix:
Lösung
This problem was first fixed in V10.1 Fix Pack 5
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
04.07.2014
27.07.2015
27.07.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.5 FixList