IC88727: DB2 MAY CRASH WHEN USING NON-THREADSAFE WRAPPER AND DB2FMP PROCESS IS TERMINATED

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • You may encounter crash when using non-threaded wrapper and
    db2fmp process is terminated.
    
    Here is the stack:
    <StackTrace>
    -----FUNC-ADDR---- ------FUNCTION + OFFSET------
    0x00002B51CA399B45 ossDumpStackTraceEx + 0x0301
                    (/home2/db2inst1/sqllib/lib64/libdb2osse.so.1)
    0x00002B51CA3941B6 _ZN11OSSTrapFile6dumpExEmiP7siginfoPvm +
    0x0270
                    (/home2/db2inst1/sqllib/lib64/libdb2osse.so.1)
    0x00002B51C5C8052D sqlo_trce + 0x04df
                    (/home2/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00002B51C5D8239B sqloEDUCodeTrapHandler + 0x0467
                    (/home2/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00002B51C21D4C10 address: 0x00002B51C21D4C10 ; dladdress:
    0x00002B51C21C7000 ; offset in lib: 0x000000000000DC10 ;
                    (/lib64/libpthread.so.0)
    0x00002B51C40412E4
    _ZN17sqleFedFMPManager18getFmpFromProcPoolEP23sqle_FedFMP_Proc_A
    nchorP13sqlerFmpParmsP14sqlerFmpHandle + 0x00b8
                    (/home2/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00002B51C4041B61
    _ZN17sqleFedFMPManager14getFmpFromPoolEP13sqlerFmpParmsP14sqlqg_
    Fmp_InfoP14sqlerFmpHandle + 0x0505
                    (/home2/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00002B51C41C3371
    _Z27sqlerFedInvokeFencedRoutineP13sqlerFmpParmsP14sqlqg_Fmp_Info
    + 0x019d
                    (/home2/db2inst1/sqllib/lib64/libdb2e.so.1)
    0x00002B51C67E8BB9
    _Z21sqlriFedInvokeInvokerP10sqlri_ufobP14sqlqg_Fmp_Info + 0x0327
    
    You can use the following steps to reproduce:
    1. set FENCED_POOL to 1 and KEEPFENCED to no
    2. make sure db2_threadsafe is n
    3. open two sessions and query the nicknames
    
    db2 connect to testdb;
    db2 "alter wrapper net8 options(set db2_threadsafe 'n')";
    db2 "select * from nickname1";
    
    4. connect reset in two sessions
    
    db2 connect reset;
    
    5. db2fmpterm all process with 0x000000004
    
    db2pd -fmp | grep 0x00000004 | awk '{ system("db2fmpterm "$2) }'
    
    6. query nickname in one of the sessions
    => db2 connect to testdb;
    => db2 "select * from nickname1"
    SQL1224N  The database manager is not able to accept new
    requests, has
    terminated all requests in progress, or has terminated the
    specified request
    because of an error or a forced interrupt.  SQLSTATE=55032
    

Local fix

  • 1. Avoid the trigger to terminate the db2fmp
    2. Increasing FENCED_POOL to large value
    3. Use thread-safe mode if wrapper supports
    

Problem summary

  • User affected:
      Users who use fenced wrapper of  in InfoSphere Federation
    Server
    Problem description and summay:
      See error description
    

Problem conclusion

  • Problem was fistly fixed in Version 10, FixPak 1. This
    fix should be applied on the federation Server.
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC88727

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    A10

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-11-29

  • Closed date

    2013-01-04

  • Last modified date

    2013-01-04

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

    JR44006

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

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • RA10 PSY

       UP



Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

DB2 for Linux, UNIX and Windows

Software version:

10.1

Reference #:

IC88727

Modified date:

2013-01-04

Translate my page

Machine Translation

Content navigation