home clear 64x64
en blue 200x116 de orange 200x116 info letter User
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 IC84487 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 / A10 - 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:                                              * 
* All                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.1 FP1 or subsequent fix pack.              * 
****************************************************************
Local Fix:
As a workaround you can drop the stored procedure and create it 
again.
available fix packs:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Solution
Problem First Fixed in DB2 Version 10.1 Fix Pack 1
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
14.06.2012
04.12.2012
04.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.1 FixList
10.5.0.1 FixList