DB2 - Problembeschreibung
Problem IC91806 | Status: Geschlossen |
DB2 INSTALLATION UNDER WINDOWS OS MAY FAIL WHEN EXTENDED SECURITY FEATURE IS ENABLED IN AD ENVIRONMENT. | |
Produkt: | |
DB2 FOR LUW / DB2FORLUW / A10 - DB2 | |
Problembeschreibung: | |
Installation fails with the following message: The creation of the process for the partitioned instance failed. Return value is "4294965337". It's caused by insufficient permission to create DB2USERS, DB2ADMINS domain groups. It happens although a user performing installation belong to the domain administrators group on the domain. Below there is an example of errors in the installation log, which reflects the issue. Action 13:23:35: DeferredCreateDB2ExtendedSecurityGroupsCA. 1: ERROR:Failed to create the "DB2ADMNS" group. 1: ERROR:Failed to create the "DB2USERS" group. Action 13:23:36: DeferredRegisterDataProviderCA. | |
Problem-Zusammenfassung: | |
**************************************************************** * USERS AFFECTED: * * DB2 in AD environment * **************************************************************** * PROBLEM DESCRIPTION: * * Please See Error Description. * **************************************************************** * RECOMMENDATION: * * Please See Error Description. * **************************************************************** | |
Local-Fix: | |
* Create DB2ADMNS, DB2USERS groups before DB2 installation with CMD commands as follow: net group DB2ADMNS /add /domain net group DB2USERS /add /domain * Disable extended security and activate it afterwards. * Add user performing installation to administrative authority on the machine on which the group is being created(Not recommended) | |
verfügbare FixPacks: | |
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows | |
Lösung | |
Workaround | |
keiner bekannt / siehe Local-Fix | |
Weitere Daten | |
Datum - Problem gemeldet : Datum - Problem geschlossen : Datum - der letzten Änderung: | 22.04.2013 02.10.2013 02.10.2013 |
Problem behoben ab folgender Versionen (IBM BugInfos) | |
Problem behoben lt. FixList in der Version | |
10.1.0.3 | |
10.1.0.3 |