DB2 - Problembeschreibung
Problem IC96967 | Status: Geschlossen |
SQL ROUTINES THAT USE THE SAME VARIABLE FOR BOTH THE IN AND OUT PARAMETERS MAY RETURN NULL | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
If a routine uses the same variable for both the IN and OUT parameters, the OUT may be NULL when the routine is called after it has been rebound. The following is an example of a call to a routine that is using the parameters in this way. call proc1(myvar, myvar) | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * SQL routine users who use the same variable for the IN and * * OUT parameters rather than using an INOUT parameter. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to DB2 Version 10.1 Fix Pack 4. * **************************************************************** | |
Local-Fix: | |
The issue will not occur if an INOUT parameter is used. Variables that will be both passing (IN) data and receiving data (OUT) can be declared as INOUT rather than passing in the variable twice. For example if the procedure was called as proc1(myvar, myvar), it can be called as proc1(myvar) if an INOUT rather than an IN and OUT parameter is used. For additional information on the INOUT parameter please see the Create procedure statement at the following Infocenter page. http://pic.dhe.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=%2 Fcom.ibm.db2.luw.sql.ref.doc%2Fdoc%2Fr0003493.html | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
First Fixed in Version 10.1 Fix Pack 4. | |
Workaround | |
Change the procedure to use an INOUT variable to both pass and receive the data. | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 17.10.2013 30.06.2014 30.06.2014 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.4 |