DB2 - Problembeschreibung
Problem IC73162 | Status: Geschlossen |
WITH FASTGROUPS=TRUE, GROUP LOOKUP IS LIMITED TO 64 GROUPS | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 | |
Problembeschreibung: | |
SQL1060N error returned when user tries to connect to database. The user belongs to a group that has granted connect priviledge. Problem caused by DB2 imposed a limitation of returning 64 groups of a user when FASTGROUPS=TRUE is set. If the user belongs to more than 64 groups then not all groups of the user is being retrieved. So authorization failed when the left out groups are the authorized groups. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * Solaris DB2 users * **************************************************************** * PROBLEM DESCRIPTION: * * SQL1060N error returned when user tries to connect to * * database. * * * * * * The user belongs to a group that has granted connect * * priviledge. * * * * * * Problem caused by DB2 imposed a limitation of returning 64. * * The problem only applies to Solaris operating system and * * also will affect transparent ldap users. * * * * groups of a user when FASTGROUPS=TRUE is set. * * * * * * * * If the user belongs to more than 64 groups then not all * * groups * * of the user is being retrieved. * * * * So authorization failed when the left out groups are the * * * * authorized groups. * **************************************************************** * RECOMMENDATION: * * Upgrade to v9.7 Fixpak 4 * **************************************************************** | |
Local-Fix: | |
Lower the numger of groups the user belongs to or unset FASTGROUPS=TRUE | |
verfügbare FixPacks: | |
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows | |
Lösung | |
Problem was first fixed in v9.7 Fixpak 4 | |
Workaround | |
Lower the numger of groups the user belongs to or unset FASTGROUPS=TRUE | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 09.12.2010 29.04.2011 29.04.2011 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
9.7. | |
Problem behoben lt. FixList in der Version | |
9.7.0.4 |