|
Problem IC66770
|
Status: Closed |
DB2 ON LINUX: SQLOKADETERMINEKERNELINTEGRITY "INDETERMINABLE OPERATING SYSTEM" MESSAGE IN DB2DIAG.LOG |
| product: |
DB2 FOR LUW / DB2FORLUW / 980 - DB2 |
| Problem description: |
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 Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 v9.8 installations on Linux where /etc/issue has been *
* modified. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description. *
****************************************************************
* RECOMMENDATION: *
* Apply fixpack 3 or do not modify the /etc/issue file. *
**************************************************************** |
| Local Fix: |
If you can, do not modify the /etc/issue file. |
| available fix packs: |
DB2 Version 9.8 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.8 Fix Pack 4 for AIX and Linux
DB2 Version 9.8 Fix Pack 5 for AIX and Linux
|
| Solution |
First fixed in DB2 UDB Version 9.8, FixPak 3 |
| Workaround |
see Local Fix. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.03.2010
17.01.2011
17.01.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.8.
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.8.0.3
|
 |
