DB2 - Problembeschreibung
Problem IT02710 | Status: Geschlossen |
AFTER UPGRADE TO V105 FP1 OR LATER, A CALL OF THE PROCEDURE MAY RETURNS SQL204N | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problembeschreibung: | |
Description After upgrade to v105 FP1 or later, a call of the procedure may returns SQL204N while the procedure executes normally before upgrading. "db2rbind dbname -l logname" runs correctly but not helpful with the problem. Cause The error of SQL204N is because the table in the procedure is dropped and re-created and hence has a newer creation timestamp than the EXPLICIT_BIND_TIME of the procedure. "db2rbind v95db -l logfile -r conservative" or" db2rbind v95db -l logfile" will not update the EXPLICIT_BIND_TIME and hence will not fix the problem. Workaround If the "any" option is used, the EXPLICIT_BIND_TIME will be updated and should work around the issue. e.g. db2rbind v95db -l logfile -r any. or SYSPROC.REBIND_ROUTINE_PACKAGE() can be invoked to more selectively rebind only the packages for the routines that fail with the SQL204N issue. e.g. call sysproc.rebind_routine_package('P','' , '' ,'<procedure_name_here>, '' ); | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * See Error Description * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Take the workaround in the description * **************************************************************** | |
Local-Fix: | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.06.2014 16.03.2015 16.03.2015 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.5.0.5 |