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

DB2V10_START.KSH SCRIPT HANGS IN CASE OF REMOTELY CATALOGED DATABASES

Produkt:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problembeschreibung:
The db2V10_start.ksh script might loop infinitely in 
activateDatabase function  in following while loop: 
 
 while [ $deact -eq 1 ]; 
     do 
         : 
         su - ${DB2INSTANCE?} -c "db2 activate database ${db?}" 
& 
        log info "su - ${DB2INSTANCE?} -c db2 activate database 
${db?}" 
         sleep 5 
        deact=$(su - ${DB2INSTANCE?} -c "db2pd -db ${db?}" | 
grep "not activated" | wc -l) 
      done 
 
It might happen that  loop forever in case the database is 
cataloged  remotely. The reason is that the script is using 
'Database name' in the activation command and it will not work 
for  remotely cataloged databases
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* All users                                                    * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.5 fix pack 4                       * 
****************************************************************
Local-Fix:
Modify the db2V10_start.ksh by changing the following part: 
 
 su - ${DB2INSTANCE?} -c "LANG=en_US db2 list database 
directory" | grep "Database name" \ 
   | tr "[a-z]" "[A-Z]" | awk '{print $4}' > ${dbFN?} 
 
to: 
 
su - ${DB2INSTANCE?} -c "LANG=en_US db2 list db directory" | awk 
'BEGIN{FS="=";} \ 
{if($1 ~ /Database name/)tmp=$2;else if(($1 ~ /Directory entry 
type/) && ($2 !~ /Remote/)) \ 
print tmp}' > ${dbFN?}
verfügbare FixPacks:
DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4) for Linux, UNIX, and Windows
DB2 Version 10.5 Fix Pack 9 for Linux, UNIX, and Windows

Lösung
Problem is fixed in DB2 version 10.5 fix pack 4
Workaround
Modify the db2V10_start.ksh by changing the following part: 
 
 su - ${DB2INSTANCE?} -c "LANG=en_US db2 list database 
directory" | grep "Database name" \ 
   | tr "[a-z]" "[A-Z]" | awk '{print $4}' > ${dbFN?} 
 
to: 
 
su - ${DB2INSTANCE?} -c "LANG=en_US db2 list db directory" | awk 
'BEGIN{FS="=";} \ 
{if($1 ~ /Database name/)tmp=$2;else if(($1 ~ /Directory entry 
type/) && ($2 !~ /Remote/)) \ 
print tmp}' > ${dbFN?}
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
14.02.2014
08.09.2014
08.09.2014
Problem behoben ab folgender Versionen (IBM BugInfos)
Problem behoben lt. FixList in der Version
10.5.0.4 FixList