When you attach a zone, if the original host and the new host have packages at the same patch level but at different intermediate patch histories, the zone attach might fail.
The goal to compare two databases that are at the same patch level and have the same configuration parameters but are not operating at the same performance levels.
For example, if one cluster is running 3.2 software that has been fully patched, and the partner cluster is running software that has been fully patched, then both clusters should be brought to the same patch level as soon as possible.
All nodes that are currently part of the cluster are selected automatically as candidates for any nodes in the cluster are down or not available, a warning message appears stating that those nodes will not be patched. These nodes must be patched to the same patch level as the rest of the nodes when they are brought back online.
All nodes that are currently part of the cluster are selected automatically as candidates for any nodes in the cluster are down or not available, a warning message appears stating that those nodes will not be patched. These nodes will be disabled by Oracle Clusterware, and must be patched to the same patch level as the rest before they can rejoin the cluster.
Examples are used only to help you translate the word or expression searched in various contexts. They are not selected or validated by us and can contain inappropriate terms or ideas. Please report examples to be edited or not to be displayed. Potentially sensitive, inappropriate or colloquial translations are usually marked in red or in orange.