DB2 - Problem description
Problem IT19642 | Status: Closed |
DB2UPDV10 FAILS WITH ERROR GRANTING EXECUTE ON ADMIN_GET_VALID_BREAKPOINTS TO ROLE SYSDEBUGPRIVATE, -204 | |
product: | |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 | |
Problem description: | |
When upgrading from v10.1 GA to v10.1 Fixpack 6 and then running the db2updv10 it will fail with the following: $ db2updv10 -a -d sample ________________________________________________________________ _________ _____ DB2 Service Tools _____ I B M db2updv10 This tool is a service utility designed to update a DB2 Version 10.1 database to the current fix pack level. ________________________________________________________________ _________ DB2 Universal Database Version 10.1, 5622-044 (c) Copyright IBM Corp. 2011 Licensed Material - Program Property of IBM IBM DATABASE 2 Database update to current fix pack tool MESSAGE: SYSCAT.ROUTINEAUTH had 0 rows successfully updated. MESSAGE: SYSCAT.MODULEAUTH had 0 rows successfully updated. MESSAGE: Error granting execute on SYSIBMINTERNAL.ADMIN_GET_VALID_BREAKPOINTS to role SYSDEBUGPRIVATE, -204 MESSAGE: Rolling back work due to sqlcode: -204 on line 891. db2updv10 processing failed for database 'sample'. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Db2 10.5 Fix Pack 9 or higher * **************************************************************** | |
Local Fix: | |
Upgrade to v10.1 Fixpack 2, 3 or 4. Run the db2updv10 and then upgrade to v10.1 Fixpack 6 and run the db2updv10 again. | |
Solution | |
First fixed in Db2 10.5 Fix Pack 9 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 10.03.2017 29.09.2017 29.09.2017 |
Problem solved at the following versions (IBM BugInfos) | |
9.0. | |
Problem solved according to the fixlist(s) of the following version(s) |