Oracle Grid Infrastructure 19c Patching and VIP Relocation

Grid Infrastructure upgrades and patching

Answer Correct answer: B — When performing rolling patches, the VIPs for the node being patched are relocated to another node.

Which statement is true concerning the installation of an Oracle Grid Infrastructure 19c patchset and its status during the installation?

They can be applied in-place.
When performing rolling patches, the VIPs for the node being patched are relocated to another node. Correct Answer
Some Grid Infrastructure patchsets may not be intalled in a rolling fashion.
When performing rolling patches, crsctl query crs softwareversion always displays the earliest version of the software running anywhere in the cluster.

Community Votes

75%

25%

75% of anonymous learners picked answer B. Votes are pick records left by other test-takers — they are not the verified answer.

Community Insight

The exam tests knowledge of rolling patch mechanics, specifically the trap of assuming VIPs remain static or that all patches support rolling upgrades.

This question addresses the behavior of Virtual IP (VIP) relocation during rolling patches of Oracle Grid Infrastructure 19c. It establishes that VIPs are moved to other nodes to maintain connectivity while a node is being patched.

Many candidates choose option C because they recall that some patches require downtime, but fail to recognize that option B describes the standard, correct behavior for supported rolling patches.

Community Discussion (4 comments)

Tunglinfo9 👍 1 Selected: C

C: Some Grid Infrastructure patchsets may not be installed in a rolling fashion." This statement is true Rolling patches cannot be done when the Oracle software files are stored in a shared cluster file system, which requires a complete outage to patch or upgrade B: "When performing rolling patches, the VIPs for the node being patched are relocated to another node." This statement is false. The sources do not describe any relocation of VIPs (Virtual IP Addresses) during patching, although services are migrated between nodes. While database instances and services might be migrated off the node being patched, the VIP associated with the node is not moved. This is also not mentioned in the context of zero downtime patching

lcoleandro 👍 1 Selected: B

A. They can be applied in-place. This statement is not always true as some patches require downtime. B. When performing rolling patches, the VIPs for the node being patched are relocated to another node. This statement is true. During rolling patches, the Virtual IP addresses (VIPs) are relocated to other nodes to ensure high availability and minimize disruption. C. Some Grid Infrastructure patchsets may not be installed in a rolling fashion. While some critical patches might not support rolling upgrades, this is less common with regular patchsets. D. When performing rolling patches, crsctl query crs softwareversion always displays the earliest version of the software running anywhere in the cluster. This is incorrect. crsctl query crs softwareversion shows the version of the software on the node where the command is run. To see the cluster-wide version, you would use crsctl query crs activeversion.

217972f 👍 1 Selected: B

Rolling fashon: Nodes are restarted sequentially, so that only one node at a time will be offline, while all other nodes in the cluster remain online. VIP must be move to another node while patching the node

krwi1 👍 1 Selected: B

it is B

Comments & Corrections

No comments yet — spotted an error or have a note? Share it below.

Expert Analysis

Why the Answer Is Correct

Option B is correct because during a rolling patch operation in Oracle Grid Infrastructure, the cluster ensures high availability by relocating the Virtual IP (VIP) addresses from the node being patched to another active node in the cluster. This prevents client connections from dropping due to network interface changes on the offline node.

Why the Other Options Are Wrong

Option A is incorrect because 'in-place' upgrades typically imply stopping services on all nodes, which contradicts the 'rolling' nature described in the context of maintaining uptime. Option C is technically true for specific non-rolling patches, but in the context of 'rolling patches' mentioned in options B and D, it is not the defining characteristic being tested; furthermore, most GI patches do support rolling installation. Option D is false because crsctl query crs softwareversion reports the version currently running on the local node, not necessarily the earliest version in the cluster.

Community Comment Notes

The community is split, with a majority voting for B. As user Tunglinfo9 noted, option C is true only when files are on shared storage requiring outage, but option B is the standard mechanism for rolling patches. User lcoleandro confirmed B is true because VIPs move to ensure high availability. The consensus among experts aligns with B as the intended answer for general rolling patch behavior.

Exam Strategy

When asked about 'rolling' operations in Oracle RAC/GI, always consider the impact on network interfaces (VIPs) and database instances. Rolling patches are designed to keep the cluster online, so mechanisms like VIP relocation are key indicators of correct answers.

Frequently Asked Questions

Why are VIPs relocated during a rolling patch?

VIPs are relocated to prevent client connection drops. If the VIP remained on the patched node, clients connecting via that VIP would lose connectivity while the node's stack was down.

Can all Grid Infrastructure patches be applied in a rolling fashion?

No. Some patches, especially those affecting the cluster file system or requiring kernel updates, may necessitate a complete cluster outage. However, the question focuses on the mechanics of rolling patches where possible.

More 1Z0-078 FAQ →

Related Analysis

← Back to 1Z0-078 Study Guide