IBM Support

IC91455: ERROR RAISED INCORRECTLY FROM SQLEFEDFMPMANAGER::DISCONNECT UPON SUBAGENT CLEANUP

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • When a subagent working on behalf of a coordinator agent is
    cleanup up, it may get sent an interrupt signal
    depending on the code currently executing in that subagent's
    code path.
    
    If the subagent is also associated with a db2fmp process
    executing federated code, then this may lead to the following
    sequence of errors in the db2diag.log :
    
    2012-08-17-02.49.02.110085+060 I4453399E448        LEVEL: Severe
    PID     : 14992                TID  : 46920542185792PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE
    APPHDL  : 0-58304              APPID:
    9.10.11.12.34514.120817014904
    AUTHID  : DB2INST1
    EDUID   : 49486                EDUNAME: db2agntp (SAMPLE) 0
    FUNCTION: DB2 UDB, base sys utilities,
    sqleFedFMPManager::disconnect, probe:30
    RETCODE : ZRC=0x00000048=72
    
    2012-08-17-02.49.02.110218+060 I4453848E451        LEVEL: Severe
    PID     : 14992                TID  : 46920542185792PROC :
    db2sysc 0
    INSTANCE: db2inst1             NODE : 000          DB   : SAMPLE
    APPHDL  : 0-58304              APPID:
    172.16.10.140.34514.120817014904
    AUTHID  : DB2INST1
    EDUID   : 49486                EDUNAME: db2agntp (SAMPLE) 0
    FUNCTION: DB2 UDB, base sys utilities,
    sqleFedFMPManager::disconnect, probe:30
    RETCODE : ZRC=0xFFFFFB95=-1131
    
    This marks db2fmp as unstable and can lead to error SQL20357N
    failing a commit statement.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade the database server to V10.1 Fix Pack 3              *
    ****************************************************************
    

Problem conclusion

  • This problem was first fixed in DB2 V10.1 Fix Pack 3
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC91455

  • 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

    2013-04-10

  • Closed date

    2013-10-21

  • Last modified date

    2013-10-21

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

    IC88426

  • 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 PSN

       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":"10.1","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
21 October 2013