IC84261: STORED PROCEDURE MAY TRAP WITH SIGILL DURING RUNTIME PROCESSING

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • Execution of a stored procedure may trap during runtime
    processing by database manager in the following stack:
    
    -------Frame------ ------Function + Offset------
    0x0900000007049A88 sqlriSectInvoke(sqlrr_cb *, sqlri_opparm *) +
    0x090000000707C0E8 sqlrr_process_execute_request(sqlrr_cb *,
    0x090000000707C3B4 sqlrr_execute(db2UCinterface *, UCstpInfo *)
    0x0900000004FA6CC8 pvmPackage::executeSection(sqlca *, unsigned
    0x0900000004F9B504 PVM::executeQuery(unsigned int, bool) + 0x1BC
    0x0900000004F99CA4 PVM::run(void) + 0xFC
    0x0900000004F97258 pvm_entry + 0x10
    0x09000000070D635C sqloInvokeFnArgs + 0xD4
    0x0900000002F83314 sqloInvokeFnArgs@glue4D5 + 0x78
    0x090000000357CF58 sqlriInvokerTrusted(sqlri_ufob *,
    
    The trap file and db2diag.log will report the following signal:
    
    Signal #4 (SIGILL): si_addr is 0x0000000000000000, si_code is
    0x0000001E (ILL_ILLOPC:Illegal opcode.)
    
    The trap will cause instance to crash. However, trapping in this
    code path is sustainable and it should not trigger an intstance
    crash. Database manager should be able to apply the trap
    resilience and return an error message to the application which
    calls the stored procedure, without bringing down the instance.
    

Local fix

  • Recompiling the stored procedure may alleviate the problem.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to DB2 V10.1 FP1 or subsequent fix pack.             *
    ****************************************************************
    

Problem conclusion

  • Problem First Fixed in DB2 Version 10.1 Fix Pack 1
    

Temporary fix

Comments

APAR Information

  • APAR number

    IC84261

  • 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-06-13

  • Closed date

    2013-02-12

  • Last modified date

    2013-02-12

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

    IC79381

  • 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



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 #:

IC84261

Modified date:

2013-02-12

Translate my page

Machine Translation

Content navigation