DB2 - Problem description
Problem IC80396 | Status: Closed |
ERROR SQL0727N WITH SYSTEM ACTION TYPE "5" AND SQLCODE "-551" CALLING A STORED PROCEDURE AFTER RUNNING: "DB2UPDV97 -A" | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
When the database configuration parameter auto_reval is set to DISABLED and you run "db2updv97 -a" it updates the DEFINER column to 'SYSIBM' in the system catalog table SYSIBM.SYSROUTINES for any stored procedure that uses the UTL_FILE module. Consequently, you might get error SQL0727N with system action type "5" and SQLCODE "-551" when you call that stored procedure. The error message is like this: SQL0727N An error occurred during implicit system action type "5". Information returned for the error includes SQLCODE "-551", SQLSTATE "42501" and message tokens .........|EXECUTE|.......". SQLSTATE=56098 Note that if you upgrade a database from Version 9.5 or earlier, the database configuration parameter auto_reval is set to DISABLED. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of DB2 for Linux, UNIX and Windows * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * . * **************************************************************** | |
Local Fix: | |
As a workaround you can drop the stored procedure and create it again. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows | |
Solution | |
Problem was first fixed in Version 9.7 Fix Pack 6. At a minimum, this fix should be applied on the database server. | |
Workaround | |
As a workaround you can drop the stored procedure and create it again. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC84487 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 13.12.2011 12.06.2012 12.06.2012 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP6 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.6 |