DB2 - Problem description
Problem IC73630 | Status: Closed |
ADDING A USER PUBLIC TO A DEFINED DB2AUDIT POLICY CRASH THE INSTANCE AT THE COORDINATOR NODE. | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problem description: | |
Adding a userid named PUBLIC to a defined db2audit policy will crash the instance at the coordinator node. It should return error SQL0567N as PUBLIC is not a valid user to add db2audit to. In addition to "PUBLIC" adding any of "ADMINS", "GUESTS", "USERS", "LOCAL", can crash DB2 in the same way. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users that add a userid named PUBLIC, ADMINS, GUESTS, USERS * * or LOCAL to a defined db2audit policy. * **************************************************************** * PROBLEM DESCRIPTION: * * Adding a userid named PUBLIC to a defined db2audit policy * * will * * crash the instance at the coordinator node. It should return * * error SQL0567N as PUBLIC is not a valid user to add db2audit * * to. * * * * In addition to "PUBLIC" adding any of "ADMINS", "GUESTS", * * "USERS", "LOCAL", can crash DB2 in the same way. * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.7 fixpack 5 * **************************************************************** | |
Local Fix: | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows | |
Solution | |
Fixed in v9.7 fixpack 5 | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.01.2011 19.12.2011 19.12.2011 |
Problem solved at the following versions (IBM BugInfos) | |
9.7.FP5 | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.5 |