IBM Support

LI73458: "SQLRR_EXECUTE: PUCSTPINFO IS NULL FOR CALL" WHEN DYNAMIC CALL FEDERATED SP IN A SP.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • In a SQL stored procedure, dynamically call federated SP will
    fail with an error -- "sqlrr_execute: pUCstpInfo is NULL for
    CALL".
    The problem is easy to be produced.
    You can reproduce the problem by following the below steps.
    
    1) create a local stored procedure in the source database.
         For example,
         create procedure sp_source
           (in charIN varchar(30), out charOUT varchar(50))
         begin
           set charOUT='INNER the sp_source.';
           return 1;
         end
    
    2) create a federated stored procedure in the target database.
         For example,
         create procedure sp_federated source SOURCEUSER.sp_source
           for server SOURCESERVER
    
    3) create a local stored procedure in the target database.
         For example,
         create procedure sp_call_federated
           ( in charIN varchar(30), out charOUT varchar(70) )
         begin
           declare vSQL varchar(300) default '';
           SET vSQL='CALL sp_federated(''call sp_federated'',?)';
           PREPARE SQL_STATEMENT FROM vSQL;
           EXECUTE SQL_STATEMENT INTO charOUT;
           return 2;
         end
    
    4) call local stored procedure in the target database.
       Then, you will receive an error.
         For example,
    $ db2 "call sp_call_federated('call sp_call_federated',?)"
    SQL0901N  The SQL statement failed because of a non-severe
    system error.
    Subsequent SQL statements can be processed.  (Reason
    "sqlrr_execute:
    pUCstpInfo is NULL for CALL".)  SQLSTATE=58004
    

Local fix

  • Use a static all to federated procedure.
    

Problem summary

  • Users affected:
    All users.
    
    Problem Summary:
    "SQLRR_EXECUTE: PUCSTPINFO IS NULL FOR CALL" WHEN CALLING
    FEDERATED STORED PROCEDURE DYNAMICALLY IN A STORED PROCEDURE.
    
    
    Problem Description:
    See the APAR description.
    

Problem conclusion

  • First fixed in DB2 UDB Version 9.1, FixPak 6.
    

Temporary fix

Comments

APAR Information

  • APAR number

    LI73458

  • Reported component name

    DB2 UDE ESE LIN

  • Reported component ID

    5765F4104

  • Reported release

    910

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-05-26

  • Closed date

    2008-11-09

  • Last modified date

    2008-11-09

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

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

    LI73461

Fix information

  • Fixed component name

    DB2 UDE ESE LIN

  • Fixed component ID

    5765F4104

Applicable component levels

  • R910 PSY

       UP

  • R950 PSY

       UP

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSEPGG","label":"DB2 for Linux- UNIX and Windows"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"910","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Document Information

Modified date:
15 October 2021