DB2 FOR LUW / DB2FORLUW / A10 - DB2

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

**************************************************************** 
* USERS AFFECTED:                                              * 
* db2haicu users                                               * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 version 10.1.0.5                              * 
****************************************************************

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.

Fixed in DB2 version 10.1.0.5

keiner bekannt / siehe Local-Fix

Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:

24.02.2015
13.07.2015
13.07.2015