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

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

product:
DB2 CONNECT / DB2CONNCT / A10 - DB2
Problem description:
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 Summary:
**************************************************************** 
* 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:
Solution
This problem was first fixed in V10.1 Fix Pack 5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
04.07.2014
27.07.2015
27.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList