Ansicht
Dokumentation

CPFBB49 - Automatic merge of cluster partitions failed. ( OS/400 )

ABAP Short Reference   BAL Application Log Documentation  
This documentation is copyright by IBM.


Message : CPFBB49
Automatic merge of cluster partitions failed.

Message Long Text :

Cause . . . . . : A failure has occurred on cluster node &2 for cluster &1 during the merge of cluster partitions. The reason code is &3. Possible reason codes are:
1 -- Communication failure has been detected. The errno value is &4. Some of the possible errno values are:
0 - The TCP/IP interface address for cluster node &2, or the local node, may not be active.
3425 - The INETD server is not active on cluster node &2.
3429 - A route to cluster node &2 is not available.
3447 - No response from cluster node &2 in allowed time.
2 -- A mismatch on the cluster membership list has been detected.
3 -- A mismatch on the current cluster version or current cluster version modification level has been detected.
4 -- A mismatch on the cluster performance and tuning parameters has been detected.
5 -- A mismatch on the device domain &5 has been detected.
6 -- A mismatch on the cluster message queue, failover wait time, or failover default action has been detected.
Recovery . . . : Recovery actions for each reason code are:
1 -- If TCP/IP is not active on this system, start TCP/IP communications using the Start TCP/IP (STRTCP) command. If the INETD server is not active on cluster node &2, have the system operator on that system start it using the Start TCP/IP Server (STRTCPSVR) command. For the following error values:
0 - Start the TCP/IP interface address, if it is currently not active, using the Start TCP/IP Interface (STRTCPIFC) command.
3425 - Start the INETD server using the Start TCP/IP Server (STRTCPSVR) command.
3429 or 3447 - Start the TCP/IP interface address, if it is currently not active, using the Start TCP/IP Interface (STRTCPIFC) command on cluster node &2. If the interface on cluster node &2 is IPv4, ensure that all active cluster nodes have an available IPv4 route to that interface. If the interface on cluster node &2 is IPv6, ensure that all active cluster nodes have an active IPv6 route to that interface.
2 -- Fix the inconsistency in the cluster membership list by either removing the node(s) or ending all the nodes in one partition and restarting them again from another partition.
3 -- Upgrade current cluster version or apply the modification to all cluster nodes in one of the partitions.
4 -- Use the QcstChgClusterResourceServices API to change the cluster performance and configuration parameters so that they are the same on both partitions.
5 -- In one partition, remove the nodes from device domain &5. When the cluster is no longer partitioned, add the nodes back into the device domain.
6 -- Use the QcstChgClusterResourceServices API to change the cluster configuration parameters so that they are the same on both partitions.

Message File : QCPFMSG
Library Message File : QSYS2924


CL_GUI_FRONTEND_SERVICES - Frontend Services   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by IBM.

Length: 3265 Date: 20240426 Time: 131455     sap01-206 ( 3 ms )