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 IC84275 Status: Geschlossen

DB2ISETUP FAILS TO CREATE AN INSTANCE WHEN THE SQLLIB DIRECTORY IS MISSING

Produkt:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problembeschreibung:
When the sqllib directory of the instance user is missing, 
db2isetup will display a success message but fail to create the 
instance. 
 
If you have the following symptoms, db2isetup will fail to 
create the instance. 
#/opt/IBM/db2/97fp6/instance> ./db2ilist 
db2inst2 
#/opt/IBM/db2/97fp6/instance> ls /home/db2inst2/sqllib 
/home/db2inst2/sqllib not found 
#/opt/IBM/db2/97fp6/instance> ./db2isetup 
 
In db2isetup: 
1) When prompted for a new user or existing user, select 
existing user and type the instance name (in this case 
db2inst2). 
2) After setup is complete, check logs and you will see some 
errors, despite the setup's misleading "Setup has completed 
successfully" message at the top of the window. 
3) "ls /home/db2inst2/sqllib" and you will notice sqllib was not 
created. 
 
After applying the fix, you will be able to create the sqllib 
under the same conditions mentioned above.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When the sqllib directory of the instance user is missing,   * 
* db2isetup will display a success message but fail to create  * 
* the                                                          * 
* instance.                                                    * 
*                                                              * 
* If you have the following symptoms, db2isetup will fail to   * 
* create the instance.                                         * 
* #/opt/IBM/db2/97fp6/instance> ./db2ilist                     * 
* db2inst2                                                     * 
* #/opt/IBM/db2/97fp6/instance> ls /home/db2inst2/sqllib       * 
* /home/db2inst2/sqllib not found                              * 
* #/opt/IBM/db2/97fp6/instance> ./db2isetup                    * 
*                                                              * 
* In db2isetup:                                                * 
* 1) When prompted for a new user or existing user, select     * 
* existing user and type the instance name (in this case       * 
* db2inst2).                                                   * 
* 2) After setup is complete, check logs and you will see some * 
* errors, despite the setup's misleading "Setup has completed  * 
* successfully" message at the top of the window.              * 
* 3) "ls /home/db2inst2/sqllib" and you will notice sqllib was * 
* not                                                          * 
* created.                                                     * 
*                                                              * 
* After applying the fix, you will be able to create the       * 
* sqllib                                                       * 
* under the same conditions mentioned above.                   * 
*                                                              * 
* Problem Description: (describe the problem including         * 
* external symptoms as seen by the customer)                   * 
* Update to IBM DB2 V9.7 Fix Pack 6.                           * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Update to IBM DB2 V10fp1                                     * 
****************************************************************
Local-Fix:
There are two workarounds: 
1) Remove the global registry by using 
"/opt/IBM/db297fp6/instance/db2iset -d db2inst2" and 
re-run "/opt/IBM/db297fp6/instance/db2isetup". 
2) Recreate the instance using 
"/opt/IBM/db297fp6/instance/db2icrt -u db2inst2 db2inst2".
verfügbare FixPacks:
DB2 Version 10.1 Fix Pack 1 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 10.1 Fix Pack 6 for Linux, UNIX, and Windows

Lösung
Update to IBM DB2 V10 fp1
Workaround
keiner bekannt / siehe Local-Fix
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
13.06.2012
23.11.2012
23.11.2012
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.1.0.1 FixList
10.5.0.1 FixList