suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT28424 Status: Closed

UNABLE TO CREATE STORED PROCEDURES WITH SAME NAME BUT DIFFERENT PARAMETERS
WHEN SQL_COMPAT ='NPS'

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
Can not create stored procedures with the same name, even if
their signatures are different when using SQL_COMPAT ='NPS'.

The following script reproduces the error:

--#SET TERMINATOR !
SET SQL_COMPAT='NPS'!
CALL SET_ROUTINE_OPTS('REOPT ONCE DYNAMICRULES RUN VALIDATE
RUN')!

CREATE PROCEDURE tst_2Sig(DATE)
RETURNS INTEGER
LANGUAGE NZPLSQL
AS BEGIN_PROC
DECLARE
pCOB ALIAS FOR $1;

vRC INTEGER;
BEGIN

vRC := 0;
return vRC;
end;
END_PROC
!

CREATE PROCEDURE tst_2Sig(DATE, INTEGER)
RETURNS INTEGER
LANGUAGE NZPLSQL
AS BEGIN_PROC
DECLARE
pCOB ALIAS FOR $1;
pID_FS ALIAS FOR $2;

vRC INTEGER;
BEGIN

vRC := 0;
return vRC;
end;
END_PROC
!

This will result in a SQL0456N error
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* ALL                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Upgrade to Db2 11.5 fixpack 1 or later                       *
****************************************************************
Local Fix:
Solution
Workaround
not known / see Local fix
Comment
See Error Description
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
12.03.2019
04.07.2019
04.11.2019
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)