nerdexam
Oracle

1Z0-060 · Question #225

You are connected to a multitenant container database (CDB) with DBA privileges. The STATISTICS_LEVEL parameter is PDB_MODIFIABLE. You issue: SQL> ALTER SYSTEM SET STATISTICS_LEVEL=ALL SCOPE=BOTH…

The correct answer is A. The STATISTICS_LEVEL parameter is immediately set to ALL in all PDBs where the B. The STATISTICS_LEVEL parameter is immediately set to ALL in the CDB instance. C. The STATISTICS_LEVEL parameter is set to ALL on all PDBs when they are opened. Issuing ALTER SYSTEM SET for a PDB_MODIFIABLE parameter from the CDB root immediately affects the CDB instance and open PDBs without a local override, while closed PDBs receive the change upon their next open.

New Features for Database Infrastructure and Architecture

Question

You are connected to a multitenant container database (CDB) with DBA privileges. The STATISTICS_LEVEL parameter is PDB_MODIFIABLE. You issue:

SQL> ALTER SYSTEM SET STATISTICS_LEVEL=ALL SCOPE=BOTH; Which three effects does this have on the CDB and its pluggable databases (PDBs)? (Choose three.)

Options

  • AThe STATISTICS_LEVEL parameter is immediately set to ALL in all PDBs where the
  • BThe STATISTICS_LEVEL parameter is immediately set to ALL in the CDB instance.
  • CThe STATISTICS_LEVEL parameter is set to ALL on all PDBs when they are opened.
  • DThe STATISTICS_LEVEL parameter is immediately set to ALL in all PDBs.
  • EThe STATISTICS_LEVEL parameter is set to ALL in the SPFILE.

How the community answered

(61 responses)
  • A
    64% (39)
  • D
    11% (7)
  • E
    25% (15)

Why each option

Issuing ALTER SYSTEM SET for a PDB_MODIFIABLE parameter from the CDB root immediately affects the CDB instance and open PDBs without a local override, while closed PDBs receive the change upon their next open.

AThe STATISTICS_LEVEL parameter is immediately set to ALL in all PDBs where theCorrect

Open PDBs that have not set their own PDB-level override for STATISTICS_LEVEL inherit the CDB root value, so they are updated to ALL immediately when the CDB root setting changes.

BThe STATISTICS_LEVEL parameter is immediately set to ALL in the CDB instance.Correct

The SCOPE=BOTH clause includes SCOPE=MEMORY, which causes the parameter to take effect immediately in the running CDB root instance.

CThe STATISTICS_LEVEL parameter is set to ALL on all PDBs when they are opened.Correct

The persistent component of SCOPE=BOTH stores the new value so that any PDB currently closed will receive STATISTICS_LEVEL=ALL when it is subsequently opened.

DThe STATISTICS_LEVEL parameter is immediately set to ALL in all PDBs.

Not all PDBs can be updated immediately because closed PDBs have no active memory to modify; they only inherit the new setting at open time, so an immediate effect across all PDBs regardless of state is not possible.

EThe STATISTICS_LEVEL parameter is set to ALL in the SPFILE.

For PDB_MODIFIABLE parameters set from the CDB root, the persistent value is stored in the root container's parameter store and propagated to PDBs at open time rather than being written as a conventional SPFILE entry that applies globally to all containers.

Concept tested: CDB root ALTER SYSTEM impact on PDBs for PDB_MODIFIABLE parameters

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/multi/administering-a-cdb-with-sql-plus.html

Topics

#CDB parameters#PDB_MODIFIABLE#multitenant#ALTER SYSTEM

Community Discussion

No community discussion yet for this question.

Full 1Z0-060 Practice