IBM Support

JR31000: DB2 MAY CRASH WHEN THE ODBC DRIVER MANAGER TRIES TO REPORT AN ERROR/WARNING REPEATEDLY

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • The repeated error/warning may cause a "Not enough space" error
    and cause the ODBC library load to fail.
    You may get the following error in db2diag.log.
    ...
    2008-07-24-07.49.51.738012+480 E4114242A678       LEVEL: Error
    (OS)
    PID     : 762110               TID  : 1           PROC :
    db2agent
    (QDFED) 0
    INSTANCE: db2inst1             NODE : 000         DB   : QDFED
    APPHDL  : 0-189                APPID:
    172.17.6.236.41013.080723234929
    AUTHID  : DB2INST1
    FUNCTION: DB2 UDB, oper system services, sqloLoadModule,
    probe:130
    CALLED  : OS, -, dlopen
    OSERR   : ENOENT (2) "No such file or directory"
    MESSAGE : Attempt to load specified library failed.
    DATA #1 : Library name or path, 32 bytes
    /opt/odbc/lib/libodbc.a(odbc.so)
    DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
    262146
    DATA #3 : String, 16 bytes
    Not enough space
    
    2008-07-24-07.49.51.751865+480 E4114921A849       LEVEL: Error
    (OS)
    PID     : 762110               TID  : 1           PROC :
    db2agent
    (QDFED) 0
    INSTANCE: db2inst1             NODE : 000         DB   : QDFED
    APPHDL  : 0-189                APPID:
    172.17.6.236.41013.080723234929
    AUTHID  : DB2INST1
    FUNCTION: DB2 UDB, oper system services, sqloLoadModule,
    probe:140
    CALLED  : OS, -, dlopen
    OSERR   : ENOENT (2) "No such file or directory"
    MESSAGE : Attempt to load specified library augmented with
    object name
    failed.
    DATA #1 : Library name or path, 42 bytes
    /opt/odbc/lib/libodbc.a(odbc.so)(shr_64.o)
    DATA #2 : shared library load flags, PD_TYPE_LOAD_FLAGS, 4 bytes
    262146
    DATA #3 : String, 149 bytes
     0509-022 Cannot load module
    /opt/odbc/lib/libodbc.a(odbc.so)(shr_64.o).
     0509-026 System error: A file or directory in the path name
    does not
    exist.
    

Local fix

  • 1. Try to find the possible reasons for the repeated
    error/warning message, for example, a network problem or expired
    license. That may eliminate the causes for the crash.
    2. Use the fenced wrapper instead.
    

Problem summary

  • Users affected:
      Users of the MSSQL wrapper in InfoSphere Federation Server
    Problem description and summary:
      See error description
    

Problem conclusion

  • Problem was first fixed in Version 9.1, FixPak 7 (s090308). This
    fix should be applied on the federation server.
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR31000

  • Reported component name

    ODBC WRAPPER

  • Reported component ID

    5724N9707

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-11-05

  • Closed date

    2009-05-11

  • Last modified date

    2009-05-11

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

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

Fix information

  • Fixed component name

    ODBC WRAPPER

  • Fixed component ID

    5724N9707

Applicable component levels

  • R910 PSN

       UP

  • R911 PSN

       UP

[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCAVPM","label":"Data Sources and Wrappers - ODBC"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"950","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
11 May 2009