home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Neueste VersionenFixList
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IT03544 Status: Geschlossen

CREATE DATABASE AS A SYSCTRL USER MAY CAUSE DATABASE CONFIGURATIONS TO NOT
BE APPLIED CORRECTLY

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
Problem description 
 
When you create a database as a SYSCTRL user, under the covers 
DB2 Autoconfigure is called to set the default values for 
database  configurations. DB2 Autoconfigure 
requires SYSADM authority, which causes DB2 Autoconfigure to 
fail returning no errors when you create the database as SYSCTRL 
user. 
 
This may cause certain parameters such as dft_table_org to 
remain as ROW and not update to COLUMN under 
DB2_WORLOAD=ANALYTICS db2 v105 BLU environment setting
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Problem Description above.                               * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Version 10.5 Fix Pack 5.                      * 
****************************************************************
Local-Fix:
Run the create database as SYSADM or run the db2 autoconfigure 
on the database after the database is created as SYSADM
Lösung
First fixed in Version 10.5 Fix Pack 5.
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
01.08.2014
27.03.2015
27.03.2015
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.5 FixList