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
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.
1 CDB1 is a container database.
2There are several pluggable databases (PDBs) in CDB1.
5Each PDB has several tables with referential integrity constraints.
6FLASHBACK DATABASE is ON.
7 UNDO RETENTION GUARANTEE is enabled.
Multiple undesired multitable changes were made in all the PDBs.
Which method can be used to undo the changes using a single command?
restore and recover database
flashback transaction
flashback database
flashback table and transaction
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
Needed to perform an Oracle Database installation?
OSASM
OSRACDBA
OSKMDBA
OSDBA
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.
SQL Performance Analyzer (SPA) has reported several regressed SQL
Statements for one of your databases.
Which action could help in the performance management of these regressed
SQL statements?
Create SQL plan directives for each of the regressed statements.
Use The SQL Tuning Advisor for each of the regressed statements.
Create an adaptive execution plan for each of the regressed statements.
Use the SQL Access Advisor for each of the regressed statements.
How do you configure a CDB for local undo mode?
Open the CDB instance in restricted mode. In CDB$ROOT, drop the UNDO
Tablespace. Execute ALTER DATABASE LOCAL UNDO ON in each PDB, and then
Restart the CDB
Instance.
Open the CDB instance in upgrade mode. In CDB$ROOT, execute ALTER
DATABASE LOCAL UNDO ON, and then restart the CDB instance.
Open the CDB instance in upgrade mode. In each PDB, execute ALTER
DATABASE LOCAL UNDO ON, create an UNDO tablespace, and then restart the
CDB instance.
Open the CDB instance in restricted mode. In CDB$ROOT, execute ALTER
DATABASE LOCAL UNDO ON. create an UNDO tablespace in each PDB, and
Then restart the CDB instance.
Tablespace from one database to another. The UNIVERSITY tablespace is
Currently open read/write. The source and destination platforms have the
Same endian Examine this list of steps:.
1. Make the UNIVERSITY tablespace read-only on the source
2. Export the UNIVERSITY tablespace metadata using EXPDP.
3. Create a cross-platform backup set from the UNIVERSITY
Source system, using an RMAN command that includes the DATAPUMP clause.
4. Copy the cross-platform backup sets to the destination system.
5. Copy the Data Pump dump set from the source to the destination system.
6. Restore the cross-platform backup set on the destination system using an
RMAN command that includes the DATAPUMP clause.
7. Import the UNIVERSITY tablespace metadata using IMPDP.
8. Make the UNIVERSITY Tablespace read/write on the destination system.
Which are the minimum number of steps required, in the correct order, to transport the UNIVERSITY Tablespace?
3,4,6
2,3,4,5,6,7
1,3,4,6,8
1,2,3,4,5,6,7,8
On the 10th of August, you implement an incremental database backup
Strategy and configure a recovery window of five days.
Level 0 backups are taken on the 10th, 17th, and 24th of August.
Differential level 1 incremental backups are taken daily between the level 0
Backups. Today is the 26th of August.
Which backups will be obsolete?
) all backups prior to 10th of August
) all backups prior to 22nd of August
) all backups prior to 20th of August
) all backups prior to 24th of August
我来回答:
