You are administering a multitenant container database (COB) that contains two pluggable databases (PDBs), pdb1 and pdb2. You are connected to pdb2 as a common user with DBA privileges. The…

Question

Options

• AThe statistics_level parameter is set to all when any of the PDBs is reopened.
• BThe statistics_level parameter is set to all only for PDB2 when it is reopened.
• CThe statistics_level parameter is set to all when the root database is restarted.
• DThe statement is ignored because there is no SPFILE for a PDB.

• A
  7% (3)
• B
  71% (32)
• C
  4% (2)
• D
  18% (8)

Explanation

Option B is correct because in Oracle Multitenant, when ALTER SYSTEM SET is executed from within a PDB with SCOPE=SPFILE, the parameter change is stored in the SPFILE scoped to that specific PDB - not the CDB or other PDBs. The change becomes active only when pdb2 is closed and reopened, not necessarily requiring a full CDB restart. SID='*' in a PDB context refers to all RAC instances serving that PDB, not all PDBs.

• A is wrong because the setting is isolated to pdb2; other PDBs retain their own STATISTICS_LEVEL values and are unaffected.
• C is wrong because pdb2 can be independently closed and reopened to activate the change - a full root restart is not required, and C implies a CDB-wide effect.
• D is wrong because Oracle (since 12.2) supports per-PDB parameter storage in the SPFILE; the statement executes successfully and persists the setting for pdb2.

Memory tip: In Multitenant, think "your session's container is your scope." Wherever you're connected when you run ALTER SYSTEM, that's the container whose parameters you're changing. SCOPE=SPFILE in a PDB = survives PDB reopen, not CDB restart.

No community discussion yet for this question.