|
Problem IT32198
|
Status: Closed |
INSTALLFIXPACK TRIES TO EXIT MAINTENANCE MODE WHEN IT SHOULDN'T
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
installFixPack fails with the following output:
TSA version installed on this host : y.y.y.y
TSA version present on the media : y.y.y.y
TSA version after update : y.y.y.y
GPFS version installed on the host: x.x.x.x
GPFS version present on the media : x.x.x.x
GPFS version after update : x.x.x.x
Tasks needed for performing Fixpack update :
============================================
1 : Stopping the instance on the local host
2 : Exiting cluster management software out of maintenance mode
...
Exiting cluster management software out of maintenance mode task
of a rolling update operation failed.
Execution of a rolling update task failed with an error.
Error message:
"Host 'HOSTNAME' is currently not in maintenance mode."
the installFixPack operation cannot exit maintenance mode if
it never entered maintenance mode to being with. This error
happens when both the GPFS and TSA versions are the same
on the media and on system; it doesn't attempt to go into
maintenance mode to update those software. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* all *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to db2_v111m4fp6 or later *
**************************************************************** |
| Local Fix: |
on the node where installFixPack failed, the TSA and GPFS has
already been updated to the target fix pack's required version
so there is no need to go into maintenance again. Simply finish
the installFixPack manually by running the following commands:
1. /bin/db2cluster -cm -verify -maintenance
(ensure its not in maintenance mode)
2. /bin/db2cluster -cfs -verfiy -maintenance
(ensure its not in maintenance mode)
3. /instance/db2iupdt -d -ru_internal_flag
-online
4. login as instance id
5. db2start instance on
5. db2start member or db2start cf (depending
on whether the node hosts a member or cf) |
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 17.03.2020
23.03.2020
24.09.2020 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
