Question 49

Which three conditions must be true for unused block compression to be used automatically while performing backups by using RMAN?

Correct Answer:ABD
About Unused Block Compression When employing unused block compression, RMAN skips reading, and backing up, any database blocks that are not currently allocated to some database object. This is regardless of whether those blocks had previously been allocated. So if a database table is dropped,
RMAN will not back up the space that was occupied by that table until new objects are created in that space. Unused block compression is used automatically when the following conditions are true:
-The COMPATIBLE initialization parameter is set to 10.2 or higher. -There are currently no guaranteed restore points defined for the database. -The data file is locally managed. -The data file is being
backed up to a backup set as part of a full backup or a level 0 incremental backup. -The backup set is created on disk, or Oracle Secure Backup is the media manager.
References: http://docs.oracle.com/database/121/BRADV/rcmcncpt.htm#BRADV89481

Question 50

Examine the command:
SQL> RECOVER DATABASE USING BACKUP CONTROLFILE UNTIL CANCEL;
In which two scenarios is this command required?

Correct Answer:AC
http://searchoracle.techtarget.com/answer/Recover-database-using-backup-controlfile-until-cancel

Question 51

You have installed two 64G flash devices to support the Database Smart Flash Cache feature on your database server that is running on Oracle Linux.
You have set the db_smart_flash_file parameter: DB_FLASH_CACHE_FILE= ‘ /dev/f lash_device_1‘,‘ /dev/f lash_device_2‘ How should the D3_flash_cache_size be configured to use both devices?

Correct Answer:B
* Smart Flash Cache concept is not new in Oracle 12C - DB Smart Flash Cache in Oracle 11g.
In this release Oracle has made changes related to both initialization parameters used by DB Smart Flash cache. Now you can define many files|devices and its sizes for “Database Smart Flash Cache” are
A. In previous releases only one file|device could be defined. DB_FLASH_CACHE_FILE = /dev/sda, /dev/sdb, /dev/sdc DB_FLASH_CACHE_SIZE = 32G, 32G, 64G
So above settings defines 3 devices which will be in use by “DB Smart Flash Cache”
/dev/sda – size 32G
/dev/sdb – size 32G
/dev/sdc – size 64G
New view V$FLASHFILESTAT – it’s used to determine the cumulative latency and read counts of each file|device and compute the average latency
Reference: https://oracle-base.com/articles/12c/database-smart-flash-cache-12cr1

Question 52

Examine the RMAN command: RMAN> RUN {
ALLOCATE CHANNEL c1 DEVICE TYPE sbt; ALLOCATE CHANNEL c2 DEVICE TYPE sbt; ALLOCATE CHANNEL c3 DEVICE TYPE sbt; BACKUP
INCREMENTAL LEVEL = 0 (DATAFILE 1, 4, 5 CHANNEL c1)
(DATAFILE 2, 3, 9 CHANNEL c2)
(DATAFILE 6, 7, 8 CHANNEL c3)
SQL ‘ALTER SYSTEM ARCHIVE LOG CURRENT’;
}
Which statement is true about the command? Choose the best answer.

Correct Answer:B

Question 53

Your database is running in noarchivelog mode. One of the data files belonging to the system tablespace is corrupted. You notice that all online redo logs have been overwritten since the last backup.
Which method would you use to recover the data file?

Correct Answer:C
Reference: https://docs.oracle.com/database/121/BRADV/rcmadvre.htm#BRADV89841

Question 54

Your multitenant container database (CDB) cdb1, which has no startup triggers and contains multiple pluggable databases (PDBs), is started up by using the command:
SQL>STARTUP
Which two statements are true about the successful execution of the command?

Correct Answer:AE
The 12.1.0.2 patchset has introduced the ability to preserve the startup state of PDBs, so you probably shouldn’t be implementing a trigger in the manner discussed in this section. Prior to 12.1.0.2, when the CDB is started, all PDBs remain in mounted mode. There is no default mechanism to automatically start them when the CDB is started. The way to achieve this is to use a system trigger on the CDB to start some or all of the PDBs.

START 1z0-067 EXAM