|
Problem IT22619
|
Status: Closed |
"DB2IUPDT -COMMIT_LEVEL " FAILED WITH DBI1558E SAYING CF IS NOT SAME LEVEL WITH MEMBER
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
The issue happens when a host is used as multiple members and a
CF. A sample db2nodes.cfg looks like the following:
0 hostA.torolab.ibm.com 0 hostA - MEMBER
1 hostA .torolab.ibm.com 1 hostA - MEMBER
128 hostA.torolab.ibm.com 0 hostA - CF
hostA:/db2/software/10.5.7/instance#./db2iupdt -d -commit_level
db2sdin1
DBI1446I The db2iupdt command is running.
DBI1558E The install utility determined that not all DB2
members or cluster caching facilities (CFs) in the current
instance use the same code level. The install
fix pack operation cannot be committed
if the members and CFs do not all use the
same code level.
"db2pd -rustat" shows the CF is still with old level:
hostA:/home/db2sdin1$db2pd -rustat
ROLLING UPDATE STATUS: Disk Value
Memory Value
Record Type = INSTANCE
ID = 0
Code Level = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Not Applicable
Architecture Level = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Not Applicable
State = [UPDATE IN PROGRESS][OFFLINE UPDATE
INITIATED]
Last updated = 2016/05/19:16:03:51
Memory values are not available because an attachment to the
instance on member 0 cannot be established.
Memory values are not available because an attachment to the
instance on member 1 cannot be established.
Record Type = MEMBER
ID = 0
Code Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Memory Value Not Available
CECL = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Memory Value Not Available
Architecture Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Memory Value Not Available
CEAL = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Memory Value Not Available
Section Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Memory Value Not Available
Target Code Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Not Applicable
State = [NONE]
Last updated = 2016/05/20:16:11:54
Record Type = MEMBER
ID = 1
Code Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Memory Value Not Available
CECL = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Memory Value Not Available
Architecture Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Memory Value Not Available
CEAL = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Memory Value Not Available
Section Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Memory Value Not Available
Target Code Level = V:10 R:5 M:0 F:7 I:0 SB:0
(0x0A05000700000000) Not Applicable
State = [NONE]
Last updated = 2016/05/20:16:11:54
Record Type = CF
ID = 128
Code Level = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Not Applicable
Architecture Level = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Not Applicable
Target Code Level = V:10 R:5 M:0 F:5 I:0 SB:0
(0x0A05000500000000) Not Applicable
State = [NONE]
Last updated = 2016/05/19:16:03:46 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* The users are running multiple members and a *
* CF on the same host. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 V11.1 FP2 or later. *
**************************************************************** |
| Local Fix: |
Run the following before running "db2iupdt -commit_level
":
//Assuming DB2V105FP7 is installed in /db2/software/10.5.7/
//run the following as the instance owner (not root)
//Make sure each command is successful before trying the next
one
db2stop
db2stop instance on
LD_LIBRARY_PATH= /db2/software/10.5.7/bin/db2ALmanager
-invalidate 128 -offline -instance -verbose
LD_LIBRARY_PATH= /db2/software/10.5.7/bin/db2ALmanager -update
128 -offline -instance -verbose
LD_LIBRARY_PATH= /db2/software/10.5.7/bin/db2ALmanager
-revalidate 128 -instance -verbose
db2pd -rustat
//If db2pd -rustat shows all members and CFs on the target
//level, then commit the new level. |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : IT15526
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 02.10.2017
17.10.2017
17.10.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
