Use Flashback Database. Which two features or parameters manage space
Availability in the fast recovery area?
Media management interface (MMI).
Which two are true about the use of
The RMAN MMI?
You can use it to create proxy copies for database files.
You can use it to create proxy copies for entire file systems.
You can use it to create image copies for entire file systems.
You can use it to create image copies for database files.
Container database (CDB) that contains pluggable databases (PDBs).
Examine the query and its output:
SQL> SELECT * FROM v$PWFILE_users;
USERNAME
SYSDB SYSOP SYSAS SYSBA SYSDG SYSKM CON_ID
---------------------------------------------------------------------
---
SYS
TRUE TRUE
FALSE
FALSE
FALSE
FALSE
0
Which two tasks must you perform to add users with the SYSBACKUP,
SYSDG, and SYSKM prileges to the password file?
Your container database, CDB1, is in local undo mode.
You successfully execute this command while connected to CDB1:
CREATE PLUGGABLE DATABASE pdb1
ADMIN USER pdb1_admin IDENTIFIED BY pdb123 ROLES= (CONNECT)
CREATE_FILE_DEST='/u01/app/oracle/oradata/cdb1/pdb1' ;
Which three are true about PDB1?
Recovery catalog?
Which three are true about unified auditing in full mode?
The unified audit trail is written to a read-only table.
The unified audit trail is written to a read-only external file.
Audit records are created for COMMIT, ROLLBACK, and SAVEPOINT statements.
Audit records are created for SYS.
Explicitly?
CDB$ROOT and pluggable databases (PDBs)?
the data dictionary in CDB$ROOT
the log writer process (LGWR)
SYSAUX tablespaces
temporary tablespaces
Current release of an Oracle multitenant database:
$ sqlplus system/oracle .
SQL> col name for a10
SQL> select name, open_mode from v$pdbs;
NAME
OPEN_MODE
---------------------------------------
PDB$SEED
READ ONLY
PDB1
READ WRITE
PDB2
MOUNTED
SQL> exit
Next you execute:
$ expdp system/oracle full=y
What is the outcome?
It fails because Data Pump cannot be used while connected to the root
Container.
It creates a full export of the root container and PDB1.
It creates a full export of the root container and all PDBs.
It creates a full export of the root container and all open PDBs.
Examine this configuration:
1CDB1 is a container database.
2 APP_ROOT is an application root in CDB1.
3APP_PDB1 is an application PDB in APP_ROOT.
4FLASHBACK DATABASE is ON.
You execute these commands:
$ sqlplus sys/orac1e_4U@localhost:1521/cdb1
SQL> SELECT current_scn FROM v$database;
CURRENT_SCN
-----------------------
2074756
SQL> CREATE TABLE cdb1_tab(c1 NUMBER) ;
Table created.
SQL> ALTER SESSION SET CONTAINER=app_root;
Session altered.
SQL> CREATE TABLE app_root_tab (c1 NUMBER) ;
Table created.
SQL> ALTER SESSION SET CONTAINER=app_pdb1;
Session altered.
SQL> CREATE TABLE app_pdb1_tab (c1 NUMBER) ;
Table created.
SQL> conn / as sysdba
Connected.
SQL> ALTER PLUGGABLE DATABASE app_root CLOSE;
Pluggable database altered.
SQL> FLASHBACK PLUGGABLE DATABASE app_root TO SCN 2074756;
Flashback complete.
Which table or set of tables will exist after the Flashback operation has
Completed?
CDB1_TAB, APP_ROOT_TAB, and APP_PDB1_TAB
CDB1_TAB and APP_PDB1_TAB
CDB1_TAB and APP_ROOT_TAB
CDB1_TAB only
You are managing this configuration:
1CDB1 is a container database.
2 PDB1 and PDB2 are two pluggable databases in CDB1.
3 USER1.EMP is a table in PDB1 and USER2.DEPT is a table in PDB2 .
CDB1 user SYS executes these commands after connecting successfully to
PDB2:
SQL> ALTER SESSION SET CONTAINER=pdb1;
Session altered.
SQL> INSERT INTO user1.emp VALUES (100, 'Alan' ,1) ;
1 row created.
SQL> INSERT INTO user1.emp VALUES (101, 'Ben' ,1) ;
1 row created.
SQL> ALTER SESSION SET CONTAINER=pdb2;
Session altered.
SQL> INSERT INTO user2.dept VALUES(1, 'IT');
Which two are true? (Choose two.)
Current release of an Oracle multitenant database: $ sqlplus system/oracle .
SQL> col name for a10
SQL> select name, open_mode from v$pdbs;
NAME OPEN_MODE
---------------------------------------
PDB$SEED READ ONLY
PDB1 READ WRITE
PDB2 MOUNTED
SQL> exit
Next you execute: $ expdp system/oracle full=y What is the outcome?
It fails because Data Pump cannot be used while connected to the root container.
It creates a full export of the root and pdb1.
It creates a full export of the root and all pdbs
.
It creates a full export of the root container and all open pdbs.
It creates a full export of only the root container
(TDE)?
1CDB1 is a container database.
2 DEFAULT_SHARING is METADATA.
3APP_ROOT is an application root contained in CDB1.
4APP_PDB1 is an application PDB contained in APP_ROOT.
5COMPANYAPP is an application contained in APP_ROOT.
6EMP is a common table created in APP_ROOT and all its application PDBs,
Created when version 1.0 of COMPANYAPP was installed.
You execute these commands:
$ sqlplus sys/orac1e@localhost:1521/cdb1 as sysdba
SQL> ALTER SYSTEM SET DEFAULT_SHARING=DATA;
System altered.
SQL> ALTER SESSION SET CONTAINER=app_root;
Session altered.
SQL> ALTER PLUGGABLE DATABASE APPLICATION companyapp BEGIN
UPGRADE '1.0' TO '2.0';
Pluggable database altered.
SQL> ALTER TABLE emp ADD (sal NUMBER NOT NULL) ;
Table altered.
SQL> ALTER PLUGGABLE DATABASE APPLICATION companyapp END
UPGRADE TO '2.0';
Pluggable database altered.
SQL> ALTER SESSION SET CONTAINER=app_pdb1;
Session altered.
SQL> DESC emp;
Name
Null?
Type
--------------------------------------------------------------
ENO
NUMBER
ENAME
VARCHAR2 (20)
SQL> SELECT * FROM emp;
ENO
ENAME
---------------------------------
100
Alan
200
Ben
SQL> ALTER PLUGGABLE DATABASE APPLICATION companyapp SYNC;
What will be the outcome and why?
SAL will be added to APP_PDB1.EMP, with 0 in columns of existing rows.
SAL will be added to APP_PDB1.EMP, with NULLs in columns of existing rows.
It will return an error because the SYNC operation is not allowed when
Constraints are added to common objects.
It will return an error because EMP is not empty in APP_ROOT.
Profiling performed by the SQL Tuning Advisor?
It is a set of recommendations by the optimizer to change the access methods
Used.
It is auxiliary information collected by the optimizer for a SQL statement to eliminate estimation error.
It is a set of recommendations by the optimizer to restructure a SQL statement to avoid suboptimal execution plans.
It is auxiliary information collected by the optimizer for a SQL statement to
Help use better joins orders.
我来回答: