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 IC86257 Status: Closed

RICHTEXTTOOL.SH SCRIPT MAY FAIL IF A THIRD PARTY AUTHENTICATION METHOD IS
CONFIGURED ON UNIX

product:
DB2 FOR LUW / DB2FORLUW / A10 - DB2
Problem description:
If the unix machine where the Rich text feature is installed 
uses a third party authentication method at the operating system 
level, the richtextTool.sh script may fail when trying to enable 
or disable the feature. The script relies on information in the 
/etc/passwd file to resolve the instance owner's home directory 
and if the authentication method does not use (or update) the 
local /etc/passwd file the script may fail with the following 
error: 
 
CIE00424E The DB2 Text Search configuration directory named "%1" 
for  the DB2 instance named "%2" does not exist.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to V10.1 FP2                                         * 
****************************************************************
Local Fix:
Hardcode the required value in the script: 
 
#DB2INSTANCE_HOME=`awk -F: '$1 ~ /^'"$DB2INSTANCE"'$/ {print 
$6}' /etc/passwd` <--- comment out 
   DB2INSTANCE_HOME=<your instance home directory>     <----- 
add this line with your instance home directory hard coded
Solution
/etc/passwd file will not be helpful if any third party 
authentication method is in use. 
This has been changed to use db2usrinf utility.
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
31.08.2012
31.12.2012
31.12.2012
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)