1Z0-078 — Frequently Asked Questions

In RAC, OPatch is cluster-aware and defaults to All-Node patching when no rolling or minimize-downtime option is provided.

No; it patches only the Oracle Home from which the command is run, not every home of the same release.

They protect memory structures accessed only by processes inside a single instance, so they never serialize access across the instances of a multi-instance database.

The Global Cache Service (GCS) coordinates database block buffers through cache fusion, while the Global Enqueue Service (GES) manages enqueues across all instances.

Because CDB1 has six instances, but prod_pool has cardinality 3, so only three instances are in the pool; a singleton service is restricted to its server pool.

Singleton means AR runs on exactly one instance in prod_pool at a time and can fail over to another instance within that same pool.

Staging is part of the patching workflow, but the question targets OPatch's documented environment prerequisite: setting PATH to $ORACLE_HOME/OPatch before invoking the utility.

No. Oracle requires updating PATH only on the node where you will run OPatch; other nodes' environments are irrelevant unless you execute OPatch there.

CTSSD decides its mode by checking whether the NTP daemon is active, not whether configured time servers respond, so unreachable servers leave CTSSD in observer mode.

No. CTSSD starts automatically at clusterware startup and selects observer mode when NTP is active; you must deactivate NTP on all nodes for active mode.

SYSREPL is not part of Oracle's privilege set. ACFS replication is administered with acfsutil repl by root, grid or an ASM administrator, not through a replication-specific role.

No. Standby redo logs are database Data Guard objects; ACFS replication transfers file system change data directly to the standby ACFS file system without database redo streams.