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

SEVERE ERROR IS REPORTED IN SLES 11 ENV. 'COULD NOT FIND
/USR/BIN/SPIDENT'

product:
DB2 FOR LUW / DB2FORLUW / 970 - DB2
Problem description:
When starting DB2 9.7 instance in SUSE Linux Enterprise Server 
11 environment, the following error may appear.  The key message 
is "Could not find /usr/bin/SPident". 
 
=-!-= 
2009-11-13-14.14.57.542827-480 E5240661E350        LEVEL: Severe 
PID     : 11108                TID  : 47434210884592PROC : 
db2star2 
INSTANCE: db2inst1             NODE : 000 
FUNCTION: DB2 UDB, oper system services, 
sqloKADetermineServiceLevel, probe:10 
DATA #1 : <preformatted> 
Could not find /usr/bin/SPident, or it is not readable and 
executable. 
 
2009-11-13-14.14.57.543391-480 E5241012E372        LEVEL: Severe 
PID     : 11108                TID  : 47434210884592PROC : 
db2star2 
INSTANCE: db2inst1             NODE : 000 
FUNCTION: DB2 UDB, oper system services, 
sqloKADetermineServiceLevel, probe:50 
MESSAGE : ECF=0x9000001A=-1879048166=ECF_FILE_DOESNT_EXIST 
          File doesn't exist 
DATA #1 : Codepath, 8 bytes 
0 
 
2009-11-13-14.14.57.601952-480 E5241385E270        LEVEL: Severe 
PID     : 11108                TID  : 47434210884592PROC : 
db2star2 
INSTANCE: db2inst1             NODE : 000 
FUNCTION: DB2 UDB, oper system services, sqloKAAnalyze, probe:10 
DATA #1 : Codepath, 8 bytes 
3 
=-!-= 
 
SPident is an executable, provided by SUSE Linux, which 
idetifies the Service Pack level of the Linux.  This executable 
is included in the previous version of SLES, but not in SLES 11. 
 The following webpage from Novell has a brief explanation on 
it. 
http://www.novell.com/linux/releasenotes/x86_64/SUSE-SLES/11/ 
 
Since DB2 tries to determine the Service Pack level of the OS 
during db2start time, the error above will appear in db2diag.log 
file.  However, this does not affect DB2's functionality in any 
way. 
 
To avoid the error message, via this APAR fix, DB2 will use a 
different command, sam, to retrieve the Service Pack level in 
SLES 11.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* SLES 11 users                                                * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* Same as ERROR DESCRIPTION                                    * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 9.7 Fix Pack 2.                               * 
****************************************************************
Local Fix:
The error can be safely ignored.  It has absolutely no impact on 
DB2's functionality.
available fix packs:
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows

Solution
The error can be safely ignored.  In addition, it will not 
appear in DB2 9.7 Fix Pack 2.
Workaround
not known / see Local fix
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC66964 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
02.03.2010
26.04.2010
26.04.2010
Problem solved at the following versions (IBM BugInfos)
9.7.FP2
Problem solved according to the fixlist(s) of the following version(s)
9.7.0.2 FixList