IBM Support

LI73798: TRAP IN GETENV

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • DB2 crashes due to trap in getenv. A sample stack is pasted
    below. The problem is in ITDS Library that is bundled with V95.
    
    ITDS apar(s) :-
    IO08107
    LDAP client cores during open_connection call to getaddrinfo
    Release - 610
    
    IO09485
    LDAP client cores during open_connection call to getaddrinfo
    Release - 600
    
    
    0        ossDumpStackTrace
    1        OSSTrapFile::dump
    2        sqlo_trce
    3        sqloEDUCodeTrapHandler
    4        __invoke_dynamic_linker
    5        getenv
    6        sqloGetEnvUnCached
    7        sqluhSkipFilteredHistoryRecord
    8        sqluhInsertSingle
    9        sqlubupHistoryFile
    10       sqlubcka
    11       sqlubcka_route_in
    12       sqlerKnownProcedure
    13       sqlerCallDL
    14       sqljs_ddm_excsqlstt
    15       sqljsParseRdbAccessed
    16       sqljsParse
    17       sqljsSqlam
    18       sqljsDriveRequests
    19       sqljsDrdaAsInnerDriver
    20       sqljsDrdaAsDriver
    21       sqeAgent::RunEDU
    22       sqzEDUObj::EDUDriver
    23       sqlzRunEDU
    24       sqloEDUEntry
    25       pthread_cond_timedwait@@GLIBC_2.3.2
    26       clone
    

Local fix

  • 1 - db2set DB2ENVLIST=TISDIR
    2 - export TISDIR=/opt/ibm/ldap/V6.0 into the shell that will
    issue the db2start command
    3 - recycle db2 (db2stop / db2start) , taking care to be in the
    shell mentioned above
    
    TISDIR pointing to a non existent path will help LDAP not
    calling putenv if it is in the environment list.
    

Problem summary

  • TRAP IN GETENV
    

Problem conclusion

  • Problem was first fixed in Version 9.5 Fixpak 4
    

Temporary fix

  • 1 - db2set DB2ENVLIST=TISDIR
    2 - export TISDIR=/opt/ibm/ldap/V6.0 into the shell that will
    issue the db2start command
    3 - recycle db2 (db2stop / db2start) , taking care to be in the
    shell mentioned above
    
    TISDIR pointing to a non existent path will help LDAP not
    calling putenv if it is in the environment list.
    

Comments

APAR Information

  • APAR number

    LI73798

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    950

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-09-16

  • Closed date

    2009-06-02

  • Last modified date

    2009-06-02

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

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

    LI73870

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • 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:
02 June 2009