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

SQLOKAANALYZE MESSAGE LOGGED AS "SEVERE" IN THE DB2DIAG.LOG
DURING DB2START

product:
DB2 FOR LUW / DB2FORLUW / 910 - DB2
Problem description:
When starting up DB2 through db2start, a severe message might be 
logged in the db2diag.log file if DB2 is unable to obtain 
information about your system, such as the architecture of the 
system, the OS ID, etc, as well as support for various features, 
like NUMA, extended I/O, etc. This does not impact DB2's ability 
to correctly operate, and therefore, the message need not be 
treated as severe. The message in question looks similar to the 
following: 
 
2009-11-26-09.59.32.253126-300 E48379E269         LEVEL: Severe 
PID     : 3244                 TID  : 46912637991088PROC : 
db2star2 
INSTANCE: db2hia               NODE : 000 
FUNCTION: DB2 UDB, oper system services, sqloKAAnalyze, probe:10 
DATA #1 : Codepath, 8 bytes 
5 
 
After applying the fix for this APAR, the message will still be 
logged, but at a warning level.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL                                                          * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* When starting up DB2 through db2start, a sqloKAAnalyze       * 
* message might be logged in the db2diag.log file, with a      * 
* severe level, if DB2 is unable to gather information         * 
* pertaining to the system. In actuality, this issue is        * 
* non-severe as it doesn't impact DB2's ability to function    * 
* correctly. The appearance of this message might erroneously  * 
* lead people to believe that DB2 has encountered a severe     * 
* problem when, in fact, no such problem exists.The            * 
* db2diag.log message in questions looks similar to the        * 
* following:                                                   * 
*                                                              * 
* 2009-11-26-09.59.32.253126-300 E48379E269                    * 
* LEVEL:Severe                                                 * 
* PID     : 3244                 TID  : 46912637991088PROC :   * 
* db2star2                                                     * 
* INSTANCE: db2hia               NODE : 000                    * 
* FUNCTION: DB2 UDB, oper system services,                     * 
* sqloKAAnalyze,probe:10                                       * 
* DATA #1 : Codepath, 8 bytes                                  * 
* 5                                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* To resolve the problem, upgrade to DB2 Version 9.1 Fixpack9. * 
****************************************************************
Local Fix:
Treat this message as you would a non-severe message.
available fix packs:
DB2 Version 9.1 Fix Pack 9  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 10  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11  for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12  for Linux, UNIX and Windows

Solution
Problem was first fixed in Version 9.1 Fixpack 9. 
 
With the fix for this APAR, the sqloKAAnalyze message is logged 
 
as a warning: 
 
2009-11-26-09.59.32.253126-300 E48379E269   LEVEL: Warning 
 
PID : 3244    TID : 46912637991088PROC : 
db2star2 
INSTANCE: db2hia NODE : 000 
FUNCTION: DB2 UDB, oper system services, sqloKAAnalyze, 
 
probe:10 
DATA #1 : Codepath, 8 bytes 
 
5
Workaround
see LOCAL FIX
BUG-Tracking
forerunner  : APAR is sysrouted TO one or more of the following: IC65815 IC65827 
follow-up : 
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.01.2010
07.04.2010
13.05.2010
Problem solved at the following versions (IBM BugInfos)
9.1.FP*,
9.1.FP9
Problem solved according to the fixlist(s) of the following version(s)
9.1.0.9 FixList
This site uses cookies to make it easier for us to provide you with our services. By using our site you agree to the use of cookies.