← Oracle administration: recovery, performance, and production
01 / 9 · 50 MIN

Containers, services, and resources

Confirm administrative scope and protect services sharing a CDB.

Concept and mechanism

A CDB groups containers, including root and application PDBs. Instance, listener, service, and PDB are related elements with distinct states. An open CDB does not establish that the funds PDB is available. Before changing anything, confirm database identity, connection service, and current container. Record open mode and instance when several instances exist. A common user can have different effective privileges across containers. Shared identity does not automatically authorize every operation. Parameters have their own modifiability, scope, and persistence rules; inspect ISPDB_MODIFIABLE and documentation before applying a local or global change. Administrative access should make the destination explicit rather than relying on a familiar terminal prompt.

Guided application

In a fictional post-maintenance incident, the listener responds but FUNDS_PDB is MOUNTED. Support confirms destination, investigates opening restrictions, and validates service after the authorized procedure. SAVE STATE can preserve open mode for later restarts, with attention to instance scope. It does not replace service and application validation. When workloads compete for CPU, Resource Manager can govern priorities and limits. Decisions should use measurements and service deadlines: prioritizing payments may delay reporting without creating additional capacity. Handover should identify each service owner, expected state, and container-specific diagnosis. Record the expected behavior after restart and the evidence needed before returning traffic.

IN PRACTICE

SELECT SYS_CONTEXT('USERENV','CON_NAME') FROM dual; confirms session container but does not replace complete destination identification.

Common pitfalls

Listener as available application; common user as universal access; root changes without impact assessment.

Related topics: PDB lifecycle and isolation · Backup and recovery evidence · Selective recovery and isolated rehearsals

Take this idea with you

Confirm context, state, and scope before intervening.

Create account

Reference: PDB scope and open state · 1Z0-183 public objectives inspected 2026-09-30; revision date not published