Neueste VersionenFixList
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
Haben Sie Probleme? - Kontaktieren Sie uns.
Kostenlos registrieren anmeldung-x26
Kontaktformular kontakt-x26

DB2 - Problembeschreibung

Problem IC66773 Status: Geschlossen

DB2 ON LINUX: SQLOKADETERMINEKERNELINTEGRITY "INDETERMINABLE
OPERATING SYSTEM" MESSAGE IN DB2DIAG.LOG

Produkt:
DB2 FOR LUW / DB2FORLUW / 950 - DB2
Problembeschreibung:
DB2 on Linux (Redhat or Suse) uses the /etc/issue file during 
db2start to determine the operating system. This file typically 
contains a string like: 
 
"SUSE Linux Enterprise Server 11 (x86_64)" 
 
Some system admistrators may change the /etc/issue file due to 
security concerns and remove that default string. 
 
db2start will then cause the following message in db2diag.log: 
 
2010-02-18-11.18.17.579021+060 E3493E313           LEVEL: Info 
PID     : 27765                TID  : 47311355225152 PROC : 
db2star2 
INSTANCE: db2i07               NODE : 000 
FUNCTION: DB2 UDB, oper system services, 
sqloKADetermineKernelIntegrity, probe:30 
DATA #1 : <preformatted> 
Indeterminable operating system. 
 
Note: This message is informational only and will not effect any 
DB2 server functionality. Nevertheless this APAR was opened 
to implement an alternative way to safely determine the 
operating system.
Problem-Zusammenfassung:
**************************************************************** 
* USERS AFFECTED:                                              * 
* ALL Users on Linux platforms                                 * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* DB2 on Linux (Redhat or Suse) uses the /etc/issue fileduring * 
* db2start to determine the operating system.This file         * 
* typically contains a string like:"SUSE Linux Enterprise      * 
* Server 11 (x86_64)"Some system admistrators may change the   * 
* /etc/issue file dueto security concerns and remove that      * 
* default string.db2start will then cause the following        * 
* message indb2diag.log:2010-02-18-11.18.17.579021+060         * 
* E3493E313          LEVEL:InfoPID    : 27765                  * 
* TID  : 47311355225152 PROC :db2star2INSTANCE: db2i07         * 
*      NODE : 000FUNCTION: DB2 UDB, oper system                * 
* services,sqloKADetermineKernelIntegrity, probe:30DATA #1 :   * 
* <preformatted>Indeterminable operating system.Note: This     * 
* message is informational only and will not effectany DB2     * 
* server functionality. Nevertheless this APAR wasopened to    * 
* implement an alternative way to safely determinethe          * 
* operating system.                                            * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 UDB Version 9.5 FixPak 6                      * 
****************************************************************
Local-Fix:
If you can, do not modify the /etc/issue file.
verfügbare FixPacks:
DB2 Version 9.5 Fix Pack 6a for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.5 Fix Pack 10 for Linux, UNIX, and Windows

Lösung
First fixed in DB2 UDB Version 9.5 FixPak 6
Workaround
see Local Fix.
Weitere Daten
Datum - Problem gemeldet    :
Datum - Problem geschlossen :
Datum - der letzten Änderung:
03.03.2010
09.09.2010
09.09.2010
Problem behoben ab folgender Versionen (IBM BugInfos)
9.5.
Problem behoben lt. FixList in der Version