DB2 - Problem description
Problem IC66616 | Status: Closed |
DB2 ON LINUX: SQLOKADETERMINEKERNELINTEGRITY "INDETERMINABLE OPERATING SYSTEM" MESSAGE IN DB2DIAG.LOG | |
product: | |
DB2 FOR LUW / DB2FORLUW / 970 - 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: ALL USERS ON LINUX PLATFORM Problem Description: See Error Description. Problem Summary: See Error Description. | |
Local Fix: | |
If you can, do not modify the /etc/issue file. | |
available fix packs: | |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows | |
Solution | |
First fixed in DB2 UDB Version 9.7, FixPak 2 (build s100514) | |
Workaround | |
see Local Fix. | |
BUG-Tracking | |
forerunner : APAR is sysrouted TO one or more of the following: IC66770 IC66773 follow-up : | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 25.02.2010 09.06.2010 09.06.2010 |
Problem solved at the following versions (IBM BugInfos) | |
9.7. | |
Problem solved according to the fixlist(s) of the following version(s) | |
9.7.0.2 |