|
Problem IT22620
|
Status: Closed |
DB2PREREQCHECK REPORTS MISSING OF LIBIPATHVERBS.I686 INCORRECTLY
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
db2prereqcheck reports missing of 32bit lib libipathverbs.i686:
[root@host01 server_t]# ./db2prereqcheck -v 10.5.0.7 -p -t
MULTI_ROCE_PORT_CLUSTER
================================================================
==========
Checking prerequisites for DB2 installation with the DB2
pureScale Feature. Version: "10.5.0.7". Operating system:
"Linux".
Validating "Linux distribution " ...
Required minimum operating system distribution: "RHEL";
Version: "5"; Service pack: "9".
Actual operating system distribution Version: "6"; Service
pack: "5".
Requirement matched.
...
Validating "libipathverbs-rdmav2.so: libipathverbs.i686" ...
The db2prereqcheck utility was unable to find the following
Mellanox package: libipathverbs.i686
ERROR : Requirement not matched.
...
Requirement not matched for DB2 database "Server" with pureScale
feature . Version: "10.5.0.7".
Summary of prerequisites that are not met on the current system:
The db2prereqcheck utility was unable to find the following
Mellanox package: libipathverbs.i686
For both Intel and Power systems, the libipathverbs.i686 library
is not required on RoCE networks on RHEL 6.x. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 2 Fix Pack 2 or higher *
**************************************************************** |
| Local Fix: |
Install the redundant library libipathverbs.i686 to pass the
prereqcheck. |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT16136
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.10.2017
24.10.2017
24.10.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
