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

REMOVE SOLARIS OS LEVEL VERIFICATION FROM DB2PREREQCHECK DUE TO
INCONSISTENT /ETC/RELEASE VALUES

product:
DB2 FOR LUW / DB2FORLUW / A50 - DB2
Problem description:
Before this APAR is included, the following error may occur: 
 
Summary of prerequisites that are not met on the current system: 
 
Required minimum kernel level : "5.10" Update "9" 
Actual kernel level: "5.10" Update "8" 
 
Even though the release file shows the proper patch level was 
applied, such as: 
 
# cat /etc/*release 
Solaris 10 10/09 s10s_u8wos_08a SPARC 
Copyright 2009 Sun Microsystems, Inc. All Rights Reserved. 
Use is subject to license terms. 
Assembled 16 September 2009 
 
Solaris 10 9/10 (Update 9) Patch Bundle applied. 
 
Due to inconsistent values stored in the /etc/release files on 
Solaris, this APAR will remove the OS level check from 
db2prereqcheck and the OS level is to be verified manually.
Problem Summary:
**************************************************************** 
* USERS AFFECTED:                                              * 
* Solaris                                                      * 
**************************************************************** 
* PROBLEM DESCRIPTION:                                         * 
* See Error Description                                        * 
**************************************************************** 
* RECOMMENDATION:                                              * 
* Upgrade to DB2 10.5 Fixpack 4                                * 
****************************************************************
Local Fix:
If the Solaris OS level is at or above the correct minimum 
level, the warning can be ignored and DB2 can be installed using 
the "-f sysreq" option to bypass the system requirements check
Solution
First fixed in DB2 10.5 Fixpack 4
Workaround
not known / see Local fix
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
01.07.2014
09.09.2014
09.09.2014
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)
10.5.0.4 FixList