|
Problem IC96837
|
Status: Closed |
DB2UPDV10 RETURN ERROR: SYSDEBUGPRIVATE, -204 |
| product: |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 |
| Problem description: |
When execute db2updv10 on DB2 10.1 FP3 on a v101GA database it
fails with error -204.
db2updv10 -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 SYSPROC.
ADMIN_REVALIDATE_DB_OBJECTS_NEW to role SYSDEBUGPRIVATE, -204
MESSAGE: Rolling back work due to sqlcode: -204 on line 833.
db2updv10 processing failed for database 'SAMPLE'.
Additionally, debugging a stored procedure from Data Studio may
also see a message stating that a SQLException occurred:
"SYSDEBUGPRIVATE" is an undefined name, SQLCODE=-204,
SQLSTATE=42704 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 10.1 FP3 *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to DB2 10.1 Fix Pack 4 *
**************************************************************** |
| Local Fix: |
|
| available fix packs: |
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows
|
| Solution |
DB2 10.1 FP4 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 11.10.2013
18.04.2014
18.04.2014 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 10.1.0.4
|
 |
