|
Problem IC71703
|
Status: Closed |
DB2UPDV97 RUN AGAINST A FP2 DATABASE WILL GRANT EXECUTE PRIVILEGE TO PUBLIC FOR ROUTINES ON RESTRICTIVE DATABASES |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2updv97 is an optional tool executed after applying a new fix
pack. When moving from v9.7 Fix Pack 2 to v9.7 Fix Pack 3,
db2updv97 will create two new routines and grant EXECUTE
privilege to PUBLIC. On restrictive databases, PUBLIC is not
supposed to be granted EXECUTE privilege on these routines,
however, it is currently being granted by default.
The two functions that are granted EXECUTE privilege to PUBLIC
on restrictive databases are :
- SYSPROC.MON_GET_APPLICATION_HANDLE
- SYSPROC.MON_GET_APPLICATION_ID |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 Version 9.7 Fix Pack 3 servers on Linux, Unix and *
* Windows platforms, running db2updv97 on a Fix Pack 2 *
* database that was created to be restrictive. *
****************************************************************
* PROBLEM DESCRIPTION: *
* Execute privilege is granted to two newly created routines *
* by db2updv97. *
****************************************************************
* RECOMMENDATION: *
* Apply DB2 Version 9.7 Fix Pack 3a to run db2updv97, or run *
* db2updv97 with the -a option. If you have already run *
* db2updv97 on DB2 Version 9.7 Fix Pack 3, then manually *
* revoke execute privilege from PUBLIC for these two routines. *
**************************************************************** |
| Local Fix: |
If you have applied v9.7 Fix Pack 3 and already run db2updv97,
then issue two revoke execute from public statements against the
two mentioned routines. If you have not yet run db2updv97, then
run it with the -a option like this:
db2updv97 -d <dbname> -a
which will ensure to assign the appropriate privileges for
restrictive and non-restrictive databases alike. |
| available fix packs: |
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
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 3a and all
subsequent Fix Packs. |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 05.10.2010
28.10.2010
28.10.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP3,
9.7.FP3
|
| Problem solved according to the fixlist(s) of the following version(s) |
