home clear 64x64
en blue 200x116 de orange 200x116 info letter User
suche 36x36
Latest versionsfixlist
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
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT07338 Status: Closed

THE DB2V10_START.KSH SCRIPT FAILS TO ACTIVATE DATABASES IN A C-SHELL (CSH)
ENVIRONMENT

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
In a TSA/HADR environment, the db2V10_start.ksh script fails to 
activate the database(s) during automated instance startup. This 
issue only occurs if the instance owner is using C-Shell (CSH). 
 
This is caused by the following command from the 
db2V10_start.ksh script failing as follows: 
 
$ csh 
> su - db2inst1 -c "LANG=en_US db2 list database directory" | 
grep 
"Database name" 
LANG=en_US: Command not found
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* db2haicu users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5                              * 
****************************************************************
Local Fix:
Remove the 'LANG=en_US' prefix from the following command, i.e. 
su - db2inst1 -c "db2 list database directory" | grep 
"Database name" 
 
The db2V10_start.ksh script is located in the 
/usr/sbin/rsct/sapolicies/db2 directory.
Solution
Fixed in DB2 version 10.1.0.5
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
24.02.2015
13.07.2015
13.07.2015
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.1.0.5 FixList