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 IC75264 Status: Closed

AFTER RUNNING DB2UPDV97, CALLING SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS() WILL
FAIL WITH SQL0204N

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
After updating the instance to a newer fix pack, it is 
recommended to run db2updv97, which modifies system objects and 
in turn mark some of them as invalid. Calling 
SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS immediately after running 
db2updv97, to revalidate these invalid system objects, will fail 
with the below error. 
 
db2 "call sysproc.admin_revalidate_db_objects()" 
call sysproc.admin_revalidate_db_objects() 
SQL20508N  An error occurred during the revalidation of object 
"SYSIBMADM.UTL_MAIL.UTL_MAIL_IMP_ADD_BOUNDARY_TEXT". Operation 
"REVALIDATION" 
failed with SQLCODE "-204", SQLSTATE "42", and message tokens 
"". 
SQLSTATE=5UA03
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Users calling the stored procedure                           * 
* SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS() after running          * 
* db2updv97 on DB2 Version 9.7 Fix Pack 1 through Fix Pack 3a  * 
* on Linux, Windows and Unix.                                  * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When revalidating the system object                          * 
* SYSIBMADM.UTL_MAIL.UTL_MAIL_IMP_ADD_BOUNDARY_TEXT through a  * 
* call to SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS(), SQL0204N will * 
* be returned due to incorrect schema checking.                * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Refer to Local Fix or apply DB2 Version 9.7 Fix Pack 4 and   * 
* re-issue the command.                                        * 
****************************************************************
Local Fix:
A workaround is to run db2rbind, make sure there are no errors 
and then retry calling SYSPROC.ADMIN_REVALIDATE_DB_OBJECTS().
available fix packs:
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
Problem is first fixed in DB2 Version 9.7 Fix Pack 4 and all 
subsequent Fix Packs.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.03.2011
28.04.2011
28.04.2011
Problem solved at the following versions (IBM BugInfos)
9.7.FP4
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.4 FixList