IT19251: CALLING A STORED PROCEDURE AGAINST NON-UDB SERVER RESULTS IN DB21102E

DB2 Version 11.1 Mod 2 Fix Pack 2 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod2 Fix Pack2 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod 3 Fix Pack 3 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix001 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod3 Fix Pack3 iFix002 for Linux, UNIX, and Windows
Db2 Version 11.1 Mod4 Fix Pack4 iFix001 for Linux, UNIX, and Windows

APAR status

• Closed as program error.

Error description

• When you run a procedure against a server of type non-UDB, for
  example DB2 zOS, the procedure may fail with DB21102E error.
  
  
  CREATE PROCEDURE P1
  DYNAMIC RESULT SETS 1
  BEGIN
  DECLARE cur CURSOR WITH RETURN TO CLIENT
  FOR
  SELECT IBMREQD FROM SYSIBM.SYSDUMMY1;
  OPEN cur;
  END
  
  DB20000I  The SQL command completed successfully.
  
  
  When you call the procedure P1 you should get the following
  result:
  
  $ db2 "call p1()?
  
    Result set 1
    --------------
    IBMREQD
    -------
    Y
  
    1 record(s) selected.
  
  When you try to call the procedure P1 against non-UDB server,
  the error appears:
  
  $ db2 "call p1()?
  
  DB21102E  Too many parameters were specified for stored
  procedure ?TEST.P1?
  (expected 0).
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * ALL                                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See Error Description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Upgrade to DB2 11.1 Mod 2 Fix Pack 2 or higher               *
  ****************************************************************
  

Problem conclusion

• First fixed in DB2 11.1 Mod 2 Fix Pack 2
  

Temporary fix

Comments

APAR Information

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

• 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