|
Problem IT26264
|
Status: Closed |
DB2CLUSTER -CFS -ENTER -MAINTENANCE MIGHT FAIL WITH 2610-602 RSCT ERROR
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
After "db2cluster -cm -enter -maintenance" successfully
completed, "db2cluster -cfs -enter -maintenance" might fail with
2610-602 RSCT error when mc_start_session() RSCT api is issued
inside the db2cluster command. But "db2cluster -cfs -enter
-maintenance" do not retry the api. It is the problem which this
APAR focuses.
note : The root cause of 2610-602 RSCT error should be analyzed
in each case.
When the error occur, you might see error messages similar to
the following :
Opening a session to the cluster manager failed. Refer to the
diagnostic logs (db2diag.log for the current member or
/tmp/ibm.db2.cluster.*) and the DB2 Information Center for
details.
Unable to enter file system maintenance mode on the local host.
See the DB2 Information Center for more details.
A diagnostic log has been saved to
'/tmp/ibm.db2.cluster.3evMaa'.
The diagnostic log might contain :
2018-08-11-08.09.41.273910+540 I1914A420 LEVEL: Error
PID : 16384392 TID : 1 PROC : db2cluster
INSTANCE: xxxxxxxx NODE : 128
HOSTNAME: xxxxxxxx
EDUID : 1
FUNCTION: DB2 UDB, high avail services, getLastErrMsg, probe:327
DATA #1 : signed integer, 4 bytes
2
DATA #2 : String, 84 bytes
Line # : 327--- 2610-602 A session could not be established with
the RMC subsystem. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Db2 11.1 Mod 4 Fixpack 4 or higher *
**************************************************************** |
| Local Fix: |
Rerun "db2cluster -cfs -enter -maintenance". |
| Solution |
|
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner :
follow-up : IT26323 |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 12.09.2018
03.12.2018
03.12.2018 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
