What happens alter issuing the SHUTDOWN TRANSACTIONAL statement?

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

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

A.
The shutdown proceeds as soon as all transactions in the CDB are either committed or
rolled back.

B.
The shutdown proceeds as soon as all transactions in both the CDB and PDBs are either

committed or rolled back.

C.
The statement results in an error because there are open PDBs.

D.
The shutdown proceeds immediately. The shutdown proceeds as soon as all
transactions in the PDBs are either committed or rolled hack.



Leave a Reply 2

Your email address will not be published. Required fields are marked *


rodge

rodge

A is correct, CDB will only wait for it’s own transactions to commit – it will not cascade and wait for associated PDBs.

Demonstrated in the following link:

http://www.orafaq.com/forum/t/190712/