IBM Support

JR27776: INSTANCE CRASH AT SQLELDAPREADNODE().

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The stack shows:
    
    =>[1] 0xffffffff75d1ef18(0xffffffff7ffeb848, 0xffffffff77a154c8,
    0xffffffff77b900c8, 0x3c00, 0x3d38, 0x20002c080), at
    0xffffffff75d1ef17
      [2] sqleLdapReadNode(0x102f890c4, 0xffffffff7ffeb93c,
    0x102f759b4, 0x4044, 0x5000, 0x5290), at 0xffffffff775fe270
      [3] sqledsLdapReadDBMSI(0x102f85080, 0x18400, 0x8001, 0x8000,
    0x184e8, 0xffffffff77a154c8), at 0xffffffff775ff108
      [4] sqlenerd(0x102f85080, 0xfffffffffffffbb7, 0x4,
    0xffffffff7ffebc6c, 0x18280000, 0xffffffff77bbf9f0), at
    0xffffffff776132b8
      [5] sqlehdir(0x102f85080, 0x20002edd0, 0x4031,
    0xffffffff77a154c8, 0x1, 0x8004), at 0xffffffff7760faac
      [6] sqleUCgetDirInfo(0x102f55c60, 0x102f759b4, 0x0, 0x0, 0x0,
    0x7fff), at 0xffffffff7727b610
      [7] sqleUCappConnect(0x102f85080, 0x102c41088,
    0xffffffff77bbf9f0, 0x19a00000, 0x0, 0xffffffff77a154c8), at
    0xffffffff77275338
      [8] CLI_sqlConnect(0x102f75080, 0x102f759b4, 0x102f75180,
    0x20000000, 0xffffffff77b366d9, 0x803b50005a030), at
    0xffffffff774c865c
      [9] SQLConnect2(0xffffffff77accb70, 0x102f75080, 0x0,
    0x102f77351, 0x102f50f00, 0x0), at 0xffffffff7741fb00
      [10] SQLDriverConnect2(0x102f77380, 0x20, 0x8, 0x102f77344,
    0x3, 0x0), at 0xffffffff77429ac8
      [11] SQLDriverConnect(0x29, 0x0, 0x102c4ac80, 0x0, 0x0,
    0xffffffff77accb70), at 0xffffffff774217c0
      [12] DRDA_Connection::connect(0x102d16a20, 0x400, 0x1,
    0x102c80c80, 0x19600000, 0xffffffff76cb7546), at
    0xffffffff76c9ca14
      [13] FencedServer::connect(0x102d03080, 0x102d15fa0,
    0xffffffff7ffee110, 0xffffffff76e4ed00, 0x102ba6b58,
    0x19300000), at 0x101a33bd0
      [14] FencedServer::connect_current_user(0x102d03080,
    0xffffffff7ffee1e0, 0x0, 0x102bad000, 0x0, 0x0), at 0x101a333bc
      [15] sqlqgConnect(0xffffffff7ffeee24, 0xffffffff7ffee340, 0x0,
    0x1, 0x100000000, 0x2bad000), at 0x101a38780
      [16] sqlqg_FMP_FedStart(0xffffffff7ffeed80, 0x0, 0x1,
    0x2bad000, 0x100000000, 0x102bad000), at 0x101a3e230
      [17] sqlqgRouter(0x102dc99c0, 0xffffffff7ffee590, 0x102e4ec80,
    0x100000000, 0x0, 0x2ff8), at 0x101a2c8ac
      [18] sqlqg_fedstp_hook(0x102e4ec80, 0x102c516e0, 0x1026dcc1a,
    0xffffffff7ffee660, 0x1, 0x0), at 0xffffffff7824d0d8
      [19] sqlqgDyload(0x102e4ec80, 0x100000000, 0x26dcc00,
    0x1026dcc00, 0x1c900000, 0x100000000), at 0x101cc5dac
      [20] sqlriFedInvokerTrusted(0x102e4ec80, 0xffffffff7ffee810,
    0xffffffff7ffee8a0, 0x102e4efc0, 0x102e4efc0, 0x102e4efe8), at
    0x10142bf20
      [21] sqlriFedInvokeInvoker(0x102e4ec80, 0x1, 0x0, 0x0, 0x1,
    0x100000000), at 0x10142c0b8
      [22] sqlqg_Call_FMP_Thread(0x102dc99c0, 0xffffffff7ffeed50,
    0x0, 0x102bf4e00, 0x0, 0x102c49548), at 0x1019fa5c4
      [23] sqlqgFedStart(0x102dc6080, 0x102c49fa0, 0x22069ec80, 0x0,
    0x0, 0x8a10), at 0x1019f3354
      [24] sqlqgOpen(0x102cfc510, 0x0, 0x102c49f40, 0x102bad328,
    0x8000, 0x102dc6080), at 0x1019e6354
      [25] sqlri_djx_rta(0x102c41e80, 0x102cfc608, 0x0, 0x102bad578,
    0x102cfc610, 0x1b800000), at 0x101386bd8
      [26] sqlriExecThreadFunc(0x102c41e80, 0x102cfc6b8,
    0x102cfc6b8, 0x0, 0x102cfd728, 0x1), at 0x101398e24
      [27] sqlriunn(0x102c41e80, 0x102cfc3b0, 0x0, 0x102cfc3d8,
    0x102cfc3d8, 0x0), at 0x1013f3154
      [28] sqlriset(0x102c41e80, 0x102c49360, 0x1, 0x1, 0x0, 0x0),
    at 0x1013f2bec
      [29] sqlriExecThreadFunc(0x102c41e80, 0x102cfc380,
    0x102cfc380, 0x0, 0x0, 0x0), at 0x101398e24
      [30] sqlriSectInvoke(0x102c41e80, 0x102cfc380, 0x0, 0x0, 0x0,
    0x0), at 0x1013985d4
    
    db2diag.log shows:
    

Local fix

  • not to use LDAP catalog.
    

Problem summary

  • see problem description
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.5, FixPak 1
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR27776

  • Reported component name

    DB2 UDB ESE WIN

  • Reported component ID

    5765F4101

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2007-11-06

  • Closed date

    2008-05-16

  • Last modified date

    2008-05-16

  • APAR is sysrouted FROM one or more of the following:

    JR26370

  • APAR is sysrouted TO one or more of the following:

Fix information

  • Fixed component name

    DB2 UDB ESE WIN

  • Fixed component ID

    5765F4101

Applicable component levels

  • R910 PSY

       UP

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSEPGG","label":"DB2 for Linux, UNIX and Windows"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
16 May 2008