Answer: B,C 

Explanation: 

The value for TBS_PERCENT_USED specifies the percentage of the tablespace quota when a tablespace is considered full. The value for TBS_PERCENT_FREE specifies the targeted free percentage for the tablespace. When the percentage of the tablespace quota reaches the value of TBS_PERCENT_USED, ADO begins to move data so that percent free of the tablespace quota approaches the value of TBS_PERCENT_FREE. This action by ADO is a best effort and not a guarantee. 

Answer: A,E 

Explanation: * Because temp files cannot be backed up and because no redo is ever generated for them, RMAN never restores or recovers temp files. RMAN does track the names of temp files, but only so that it can automatically re-create them when needed. 

* If you use RMAN in a Data Guard environment, then RMAN transparently converts primary control files to standby control files and vice versa. RMAN automatically updates file names for data files, online redo logs, standby redo logs, and temp files when you issue RESTORE and RECOVER. 

Answer: A 

Explanation: Schema objects are referenced with varying usage patterns; therefore, their cache behavior may be quite different. Multiple buffer pools enable you to address these differences. You can use a KEEP buffer pool to maintain objects in the buffer cache and a RECYCLE buffer pool to prevent objects from consuming unnecessary space in the cache. When an object is allocated to a cache, all blocks from that object are placed in that cache. Oracle maintains a DEFAULT buffer pool for objects that have not been assigned to one of the buffer pools. 

Answer: A,C 

Explanation: 

Block corruptions can be divided Into Interblock corruption and intrablock corruption. In intrablock corruption. th. corruption occurs within the block itself and can be either physical or logical corruption. In interblock corruption, the corruption occurs between blocks and can only be logical corruption. (key word) * The VALIDATE command checks for intrablock corruptions only. Only DBVERIFY and the ANALYZE statement detect Interblock corruption. VALIDATE Command Output ..> List of Control File and SPFILE. 

File TYPE >.. SPFILE or Control File. 

Status >.. OK if no corruption, or FAILED If block corruption is found. 

Blocks Failing ... The number of blocks that fail the corruption check. These 

blocks are newly corrupt. 

Blocks Examined ... Total number of blocks in the file. 

Oracle' Database Backup and Recovery User's Guide 

12c Release 1 (12.1) - 16 Validating Database Files and Backups 

Answer: B,C 

Explanation: B: Job priorities are used only to prioritize among jobs in the same class. 

Note: Group jobs for prioritization Within the same job class, you can assign priority values of 1-5 to individual jobs so that if two jobs in the class are scheduled to start at the same time, the one with the higher priority takes precedence. This ensures that you do not have a less important job preventing the timely completion of a more important one. 

C: Set resource allocation for member jobs Job classes provide the link between the Database Resource Manager and the Scheduler, because each job class can specify a resource consumer group as an attribute. Member jobs then belong to the specified consumer group and are assigned resources according to settings in the current resource plan. 

Answer: A,B 

Explanation: A: Below we see a case where we set the row archival visibility parameter to "all" thereby allowing us to see all of the rows that have been logically deleted: 

alter session set row archival visibility = all; 

We can then turn-on row invisibility back on by changing row archival visibility = "active": alter session set row archival visibility = all; 

B: To use ora_archive_state as an alternative to deleting rows, you need the following settings and parameters: 

1. Create the table with the row archival clause 

create table mytab (col1 number, col2 char(200)) row archival; 

2. Now that the table is marked as row archival, you have two methods for removing rows, a permanent solution with the standard delete DML, plus the new syntax where you set ora_archive_state to a non-zero value: 

update mytab set ora_archive_state=2 where col2='FRED' 

3. To make "invisible rows" visible again, you simply set the rows ora_archive_state to zero: 

update mytab set ora_archive_state=0 where col2='FRED' Note: 

* Starting in Oracle 12c, Oracle provides a new feature that allow you to "logically delete" a row in a table without physically removing the row. This effectively makes deleted rows "invisible" to all SQL and DML, but they can be revealed at any time, providing a sort of "instant" rollback method. 

To use ora_archive_state as an alternative to deleting rows. 

Answer: C 

Explanation: 

Note: 

* In a container architecture, the parameters for PDB will inherit from the root database. That means if statistics_level=all in the root that will cascade to the PDB databases. 

You can over ride this by using Alter system set, if that parameter is pdb modifiable, there is a new column in v$system_parameter for the same. 

Answer: B,C,E 

Explanation: * A fundamental aspect of the workload repository is that it collects and persists database performance data in a manner that enables historical performance analysis. The mechanism for this is the AWR snapshot. On a periodic basis, AWR takes a “snapshot” of the current statistic values stored in the database instance’s memory and persists them to its tables residing in the SYSAUX tablespace. 

* AWR is primarily designed to provide input to higherlevel components such as automatic tuning algorithms and advisors, but can also provide a wealth of information for the manual tuning process. 

Answer: B,C 

Reference: http://docs.oracle.com/cd/E11882_01/network.112/e36292/authorization.htm#DBSEG9987 

8 (the functionality of roles)