DB2 - Problem description
Problem IT21830 | Status: Closed |
SQL0818N RETURNED TO APPLICATION WHEN SQL PROCEDURE INVOKED AFTER THE PRIOR INVOCATION WAS ROLLED BACK. | |
product: | |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 | |
Problem description: | |
Under following sequence of process, DB2 may return SQL0818 to client application for the call of a SQL procedure that was previously marked invalid. 1 CALL the SQL procedure (DB2 implicitly recompiles that stored procedure since it was invalid) 2 transaction is rollback. 3 Call the same SQL procedure using the same CALL statement The issue results because the rollback of the implicit recompilation of the procedure leaves compiled information in DB2s SQL Cache including a new package that was created during the recompilation When the same procedure in being re-invoked, DB2 may still use that rolled back information causing SQL0818N (due to use of the new package that was since rolled back | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher * **************************************************************** | |
Local Fix: | |
When procedures are invalidated (due to some DDL), make them valid by running ADMIN_REVALIDATE_DB_OBJECTS() | |
Solution | |
Workaround | |
not known / see Local fix | |
BUG-Tracking | |
forerunner : IT16250 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.08.2017 24.10.2017 24.10.2017 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |