CCNA Core Administration And Cdb Pdb Architecture Questions

The ALTER PLUGGABLE DATABASE ... SAVE STATE command saves the current open mode of the PDB so that it is automatically restored when the CDB instance restarts. This is the correct method to ensure a PDB opens automatically in a specific mode. The command stores the state in the CDB's data dictionary and applies it during instance startup.

When a PDB is in MOUNTED state its data files are associated but the PDB is not open for user traffic, so applications receive initialization errors. Issuing ALTER PLUGGABLE DATABASE SALESPDB OPEN from the root transitions the PDB to READ WRITE and immediately allows sessions to connect. This is the precise, minimal command for the reported symptom.

Dedicated local users exist only within a single pluggable database, not in the root container, satisfying the requirement for characteristics unique to PDBs. Unlike common users, who are created in the root and shared across all containers, local users are scoped strictly to their own PDB and cannot authenticate elsewhere in the multitenant architecture.

PDB$SEED is a read-only template containing the system and sysaux datafiles that Oracle copies when you issue CREATE PLUGGABLE DATABASE. It supplies the starting file structure for every new PDB, matching the stem's template purpose.

This command transitions HRPDB from MOUNTED to READ WRITE with no restrictions, which is exactly the state needed. It is issued from the CDB root, requires no instance restart, and immediately makes the PDB's services accept ordinary user connections. This is the correct and minimal action to recover from the junior DBA's CLOSE IMMEDIATE.

UNPLUG writes the PDB's metadata into its own XML manifest and closes it, letting you move the data files and plug them into a different CDB via CREATE PLUGGABLE DATABASE. This satisfies the no-Data-Pump constraint by relocating files directly.

An XML file holds the PDB metadata generated during unplugging, capturing the datafiles, tablespaces and options needed to plug the PDB into another CDB. This satisfies the requirement to preserve structural metadata independently of the datafiles themselves.

Issuing this command opens every pluggable database whose current open mode is mounted, transitioning each to read-write, provided the CDB itself is open. It satisfies the requirement to bring all PDBs online simultaneously without naming them individually, respecting each PDB's saved state and any instance-restriction settings.

DBMS_PDB.CHECK_PLUG_COMPATIBILITY validates a non-CDB's data dictionary against the target CDB before migration, reporting violations that would block plugging. It satisfies the stem's requirement to detect compatibility issues prior to starting, unlike DBMS_PDB.DESCRIBE, which only generates the XML manifest without performing any compatibility checks.

V$RSRCPDBMETRIC_HISTORY provides historical resource usage metrics for PDBs, similar to V$RSRCPDBMETRIC but with a time dimension. It allows you to analyze trends and past performance. This view is crucial for historical analysis of PDB resource consumption. It is a valid view in Oracle Database 23ai and complements the real-time view for comprehensive monitoring.

Generating an XML metadata file captures the PDB's structure and data definitions before unplugging, satisfying the requirement to preserve the pluggable database's metadata for later re-plugging into another container. Without this export, the unplugged PDB's datafiles would lack the manifest needed to register them elsewhere.

ALTER PLUGGABLE DATABASE ... CLOSE IMMEDIATE closes a single PDB without affecting the CDB instance or other PDBs. It rolls back that PDB's active transactions and disconnects its users. This is the correct way to isolate maintenance to one container while keeping the rest of the CDB available.

This command transitions SALESPDB from MOUNTED to READ WRITE in one step and is issued from the CDB root. Because the PDB datafiles are already open at the CDB instance level when the PDB is MOUNTED, opening it requires no additional instance startup and is the standard, lowest-effort recovery action for this exact symptom.

Must be unique for each database in a Data Guard configuration.

A multitenant container database shutdown cascades to its pluggable databases: the CDB closes every PDB first, then shuts itself down. This ordered teardown satisfies the default behaviour, whereas PDBs cannot remain open once the root container and instance terminate.

Reissuing the OPEN command without the RESTRICTED clause transitions REPORTSPDB to READ WRITE mode with normal connection semantics, allowing the developer to connect and create a local user. Because the statement names only REPORTSPDB, other PDBs in FINCDB retain their current open modes, satisfying the requirement to limit the change to one PDB.

SHOW CON_NAME returns the name of the container to which the current session is connected, directly answering the requirement to display the active container. It works in both CDB root and PDB contexts without needing to query data dictionary views.

Creating the XML metadata file during unplugging captures the PDB's data dictionary, tablespace definitions and service details, which the destination CDB requires to register and integrate the plugged-in PDB correctly. Without this manifest, the target CDB cannot reconcile the PDB's structure, so the operation fails to preserve data integrity across the two containers.

When cloning a PDB locally using CREATE PLUGGABLE DATABASE ... FROM, the source PDB must be in READ ONLY mode to ensure a consistent copy. This prevents changes to the source during the cloning process, guaranteeing the clone is a point-in-time snapshot. If the source is open READ WRITE, the command will fail.

DBMS_PDB.CHECK_PLUG_COMPATIBILITY validates a non-CDB's data dictionary against 23ai CDB requirements before plugging, reporting violations that would block migration. It satisfies the stem's pre-migration compatibility assessment constraint, unlike DBMS_PDB.DESCRIBE (metadata only) or transportable tablespace checks, which do not evaluate full plug-in readiness.

Issuing ALTER PLUGGABLE DATABASE SALESPDB OPEN READ ONLY transitions the PDB into a read-only state where users can query data but cannot perform DML or DDL against the PDB. This matches the audit requirement while leaving other PDBs untouched, because the command names only SALESPDB and the root container does not change its own open mode.

SAVE STATE records the PDB's current open mode so that on subsequent CDB startups the PDB is automatically reopened in that same mode. Opening it READ ONLY first and then saving state captures exactly the desired behavior. This is the supported mechanism for persisting a non-default open mode across restarts.

SQL*Plus remains the standard command-line tool for administering CDB and PDB configuration in Oracle 23ai, satisfying the requirement for a native, always-available interface. It connects directly to the root or a pluggable database, letting you run ALTER SYSTEM and ALTER DATABASE statements to modify container-level parameters without extra tooling.

V$PDBS lists every pluggable database within a container database, including its open mode and restricted status, directly satisfying the requirement to report open status across all PDBs. Querying it from the CDB root returns one row per PDB, unlike V$DATABASE, which describes only the current container.

The CDB instance manages all background processes, including root-level tasks and PDB-level operations, across every container in the multitenant architecture. It satisfies the constraint of spanning all containers, unlike a PDB instance which only governs its own pluggable database's processes.

CLOSE IMMEDIATE rolls back uncommitted transactions, disconnects all sessions, and closes the PDB promptly without waiting for users to log off. It is the correct choice when a maintenance window requires fast, forced disconnection of all sessions and the PDB must become unavailable immediately.

Background processes such as DBWn, LGWR, CKPT and SMON belong to the CDB instance and serve every PDB; PDBs have no separate processes. This shared instance-level architecture is what distinguishes a CDB from non-CDB deployments.

The PDB XML metadata file records datafile locations so the PDB can be cloned or plugged in elsewhere with correct file paths. This satisfies the requirement by capturing the physical storage layout needed for relocation.

In a multitenant architecture, each PDB has its own data dictionary and schema objects. If the developer connects to the CDB root, they will not see tables that reside in a PDB. The error suggests they are not in the correct container. They must connect directly to the PDB using its service name.

Snapshot Carousel retention is capped by the MAX_PDB_SNAPSHOTS parameter, which defaults to 8 and can be raised to 1024. This satisfies the stem's constraint by defining the exact per-PDB snapshot limit, rather than leaving retention unbounded or fixed at a single value.

RESTRICTED mode blocks all connections except those holding the RESTRICTED SESSION privilege, which administrators grant to specific users for maintenance. This satisfies the stem's constraint precisely: only privileged sessions may connect while the pluggable database remains open to those accounts alone.

The SAVE STATE clause records the current open mode of the PDB in the CDB's metadata. When the CDB instance restarts, the PDB will be opened to that saved state automatically. This is the standard and supported method to ensure a PDB starts automatically. It is simple, reliable, and does not require custom scripting.

Dropping the CDB removes the root container that every PDB depends on, so all PDBs are dropped along with it. This satisfies the stem's constraint: a PDB cannot exist independently of its CDB, since the CDB supplies the shared instance, data dictionary and system metadata the PDB requires.

ALTER PLUGGABLE DATABASE OPEN READ ONLY transitions the PDB from MOUNTED to a queryable state while blocking DML, satisfying the READ ONLY requirement. The OPEN clause is mandatory because a PDB must be opened before any read-only access is possible.

A Proxy PDB presents a remote PDB through a local database link, so applications connect locally while the actual data resides elsewhere. This satisfies the requirement of accessing remote PDB data without duplicating it, since queries are forwarded to the source PDB.