nerdexam
Oracle

1Z0-060 · Question #185

You connect to the root container of a multitenant container database (CDB) with SYSDBA privileges by using SQL*Plus. The CDB has several pluggable databases (PDBs) open in read/write mode. There…

The correct answer is C. the shutdown proceeds as soon as all transactions in the CDB are either committed or rolled. SHUTDOWN TRANSACTIONAL from the CDB root waits only for active transactions in the root container to complete, not for PDB transactions.

New Features for Database Infrastructure and Architecture

Question

You connect to the root container of a multitenant container database (CDB) with SYSDBA privileges by using SQL*Plus. The CDB has several pluggable databases (PDBs) open in read/write mode. There are ongoing transactions in both the CDB and the PDBs. What happens after issuing the SHUTDOWN TRANSACTIONAL statement?

Options

  • Athe statement results in an error because there are open PDBs
  • Bthe shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled
  • Cthe shutdown proceeds as soon as all transactions in the CDB are either committed or rolled
  • Dthe shutdown proceeds immediately

How the community answered

(35 responses)
  • A
    3% (1)
  • B
    11% (4)
  • C
    80% (28)
  • D
    6% (2)

Why each option

SHUTDOWN TRANSACTIONAL from the CDB root waits only for active transactions in the root container to complete, not for PDB transactions.

Athe statement results in an error because there are open PDBs

SHUTDOWN TRANSACTIONAL is a valid command regardless of PDB state and does not raise an error due to open PDBs.

Bthe shutdown proceeds as soon as all transactions in the PDBs are either committed or rolled

SHUTDOWN TRANSACTIONAL connected to the root only considers root container transactions; waiting for all PDB transactions is the behavior that would apply if issued from within each individual PDB.

Cthe shutdown proceeds as soon as all transactions in the CDB are either committed or rolledCorrect

When issued from the CDB root, SHUTDOWN TRANSACTIONAL waits for all active transactions in the current container - the root - to commit or roll back before proceeding. The scope of 'transactional' shutdown is limited to the container the session is connected to, so PDB transactions do not block it.

Dthe shutdown proceeds immediately

Immediate or abort modes proceed without waiting for transactions; TRANSACTIONAL specifically waits for the current container's active transactions to finish.

Concept tested: Oracle CDB SHUTDOWN TRANSACTIONAL container-level scope

Source: https://docs.oracle.com/en/database/oracle/oracle-database/19/admin/starting-up-and-shutting-down.html

Topics

#CDB shutdown#SHUTDOWN TRANSACTIONAL#multitenant#PDB transactions

Community Discussion

No community discussion yet for this question.

Full 1Z0-060 Practice