Exam 1z0-083 topic 1 question 34 discussion

other session to check any transaction Version 19.5.0.0.0 SQL> SQL> alter session set container=ELC20MIG; Session altered. SQL> select * from user1.emp; no rows selected correct answer is A & C

tested in 19c. correct answer is A & C

Instead of my previous comment, F is FALSE. This is because the insert failed, there is no uncommitted insert. There just is no insert at all.

Answer: A, F F is TRUE, there is no commit at all. Reasoning for C being false might be the keyword "parent container".

Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.9.0.0.0 SQL> alter session set container=PDBDEV; Session altered. SQL> insert into hr.emp values(100,'acujar'); 1 row created. SQL> insert into hr.emp values(101,'arozo'); 1 row created. SQL> alter session set container=PDBDEV2; Session altered. SQL> insert into hr.dept values (100, 'afaa'); insert into hr.dept values (100, 'afaa') * ERROR at line 1: ORA-65023: active transaction exists in container PDBDEV SQL>

A C From MyOracleSupport note "Oracle Multitenant: Frequently Asked Questions (Doc ID 1511619.1)" Can a transaction span across PDBS ? No, though "alter session set container" is allowed after starting a transaction in a PDB, only select is allowed in the second PDB.Transaction is preserved and you can do commit or rollback after switch back to original PDB

SQL> alter session set container=ORCLPDB; Session altered. SQL> create table a (col1 varchar2(10)); Table created. SQL> insert into a values ('1'); 1 row created. SQL> alter session set container=APPCON1; Session altered. SQL> create table a (col1 varchar2(10)); create table a (col1 varchar2(10)) * ERROR at line 1: ORA-65023: active transaction exists in container ORCLPDB

A C 100% Here my own test. SQL> insert into in1 values(1); 1 row created. SQL> alter session set container=pdb2; Session altered. SQL> insert into in2 values(2); insert into in2 values(2) * ERROR at line 1: ORA-65023: active transaction exists in container PDB1

I will go for GF. all ddl command when issued on a session automatically commit any existing dml on that same session. that makes G correct.

A and C

i think ac

A+C is correct

Surely A & C sqlplus / as sysdba SQL*Plus: Release 19.0.0.0.0 - Production on Tue Sep 14 16:58:07 2021 Version 19.11.0.0.0 Copyright (c) 1982, 2020, Oracle. All rights reserved. Connected to: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production Version 19.11.0.0.0 SQL> ALTER SESSION SET CONTAINER=PDB1; Session altered. SQL> INSERT INTO USER1.EMP VALUES(100); 1 row created. SQL> INSERT INTO USER1.EMP VALUES(200); 1 row created. SQL> ALTER SESSION SET CONTAINER=PDB2; Session altered. SQL> INSERT INTO USER2.DEPT VALUES(300); INSERT INTO USER2.DEPT VALUES(300) * ERROR at line 1: ORA-65023: active transaction exists in container PDB1 SQL>

A transaction cannot span multiple containers. If you start a transaction and use ALTER SESSION SET CONTAINER to switch to a different container, then you cannot issue DML, DDL, COMMIT, or ROLLBACK statements until you switch back to the container in which you started the transaction.

A and F. Refer to The 12c DBA Guide p. 399.

SQL> alter session set container=PDB1; Session altered. SQL> insert into emp values(1); 1 row created. SQL> alter session set container=PDB2; Session altered. SQL> insert into emp values(2); insert into emp values(2) * ERROR at line 1: ORA-65023: active transaction exists in container PDB1

SQL> alter session set container=ELC20MIG; Session altered. SQL> select * from user1.emp; no rows selected SQL> insert into user1.emp values(100); 1 row created. SQL> insert into user1.emp values(200); 1 row created. SQL> alter session set container=PDB2; Session altered. SQL> insert into user2.emp values(100); insert into user2.emp values(100) * ERROR at line 1: ORA-65023: active transaction exists in container ELC20MIG