IBM Support

IC83718: Signal #11 crash or 901 when calling SQL procedure while CASTing an OUT parameter marker or host variable

Subscribe

You can track all active APARs for this component.

APAR status

  • Closed as program error.

Error description

  • DB2 will terminate abnormally when calling an SQL procedure
    under the following conditions:
    
    - The procedure is declared with at least one OUT parameter of
    type CHAR;
    - The corresponding parameter in the CALL statement is a
    parameter marker that has been cast to an INTEGER type.
    
    For example:
    
    create or replace procedure proc1(out param CHAR(5))
    begin
    end
    %
    call proc1(CAST(? as INTEGER));
    %
    
    You will observe a stack trace similar to the following:
    
    ossDumpStackTraceEx
    OSSTrapFile6dumpEx
    sqlo_trce
    sqloEDUCodeTrapHandler
    __restore_rt
    sqlddFreeDD
    sqlnq_describe_call_parms
    sqlnq_describe
    sqlnn_cmpl
    sqlnn_cmpl
    sqlra_compile_var
    sqlra_find_var
    (truncated stack)
    
    ALSO :
    901 can be reported while executing CALL stmt with NOOP CAST on
    OUT/INOUT type parameter
    
    CREATE or replace PROCEDURE  P_INOUT
    INOUT RES FLOAT)
    begin
    end
    %
    CREATE or replace PROCEDURE CALLER1
    LANGUAGE SQL
    P1:
    BEGIN
      DECLARE V1 FLOAT;--
      CALL  P_INOUT(double(V1));--
    END
    %
    

Local fix

  • Do not use CAST on OUT/INOUT parameter markers
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * ALL                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See Error Description                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply v9.7 Fixpack 7 to the DB2 database server.             *
    ****************************************************************
    

Problem conclusion

  • This is a server side fix.  First fixed in v9.7 Fixpack 7.
    

Temporary fix

  • See LOCAL FIX.
    

Comments

APAR Information

  • APAR number

    IC83718

  • Reported component name

    DB2 FOR LUW

  • Reported component ID

    DB2FORLUW

  • Reported release

    970

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-05-24

  • Closed date

    2012-10-20

  • Last modified date

    2012-10-20

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

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

    IC88350

Fix information

  • Fixed component name

    DB2 FOR LUW

  • Fixed component ID

    DB2FORLUW

Applicable component levels

  • R970 PSN

       UP



Document information

More support for: DB2 for Linux, UNIX and Windows

Software version: 9.7

Reference #: IC83718

Modified date: 20 October 2012