Which Resource Manager Directive Binds Cost in a Low‑Traffic Multitenant PDB?

Goal

Determine whether a low‑traffic Oracle workload should be moved into a Multitenant PDB or kept as a separate instance to reduce fixed infrastructure costs while avoiding noisy‑neighbor effects.

Constraints and Uncertainty

Consolidation shares the CDB instance, SGA, and background processes, but licensing may still be based on core or named‑user entitlement. Sub‑capacity credit rules vary by release, and the deprecation of non‑CDB architecture may force migration. The main uncertainty is which Resource Manager directive actually enforces a hard cost limit and protects the PDB from other tenants’ bursts.

Specific Questions

1. Which Resource Manager directive—shares, utilization_limit, or parallel_server_limit—provides a hard cap on CPU usage for a low‑traffic PDB?
2. Does setting a utilization_limit on the CDB effectively prevent noisy neighbors from exceeding a defined cost threshold?