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

DB2SUPPORT COMMAND FAILS FOR SOLARIS 10 USERS WHEN WHOAMI COMMAND IS NOT
AVAILABLE FOR SHELL

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
For Solaris 10 users when whoami command is available in path 
"/usr/ucb/whoami" not covered by shell PATH environment 
variable, db2support will not work: 
 
db2support -h 
sh: whoami: command not found 
 
Initialization of main control block has failed: Failed
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Solaris 10 users                                             * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 Cancun Release 10.5.0.4 (also known as Fix    * 
* Pack 4) or higher.                                           * 
****************************************************************
Local Fix:
a) add /usr/ucb to PATH environment variable 
b) create a symbolic link of whoami command in /usr/bin
available fix packs:
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

Solution
Fixed in DB2 Cancun Release 10.5.0.4 (also known as Fix Pack 4)
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
25.03.2014
03.11.2014
03.11.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList