Details on incompatibilities 1
In the forced startup of a cluster application is issued, data corruption may occur if you start cluster applications when nodes without running RMS exist in the cluster.
Therefore, to deal with issue, the function is added. This function forcibly shuts down the nodes without running RMS before forced start the cluster application.
Changes
In the forced startup of a cluster application is issued, even if the nodes without running RMS exist in the cluster and it may cause the data corruption, forcibly starts the cluster application according to the user's operation.
For reducing the risk of data corruption in the forced startup of a cluster application is issued, forcibly starts the cluster application after forcibly shuts down the nodes without running RMS.
Note
For details, see "4.2 Operator Intervention Messages" in "PRIMECLUSTER Messages."
Details on incompatibilities 2
With the default settings made when the cluster was installed, the operator intervention request is always enabled.
For details, see "5.2 Setting up Fault Resource Identification and Operator Intervention Request."
Changes
The operator intervention request will not work with the default setting at installation.
The default value of AppWatch set when the cluster was installed is set to OFF, and the operator intervention request will not work with this default value.
The operator intervention request will work with the default setting at installation.
The operator intervention request, is disabled only when the AppWatch parameter is set to OFF with clsetparam.
Note
After you have changed the AppWatch parameter with clsetparam, you have to restart all the nodes to validate the setting.
