Explanation/Reference:
Explanation:
* With a control file autobackup, RMAN can recover the database even if the current control file, recovery catalog, and server parameter file are inaccessible.
* RMAN uses a recovery catalog to track filenames for all database files in a Data Guard environment. A recovery catalog is a database schema used by RMAN to store metadata about one or more Oracle databases. The catalog also records where the online redo logs, standby redo logs, tempfiles, archived redo logs, backup sets, and image copies are created.

Note:
*An incremental level 0 backup backs up all blocks that have ever been in use in this database.
*In a cumulative level 1 backup, RMAN backs up all the blocks used since the most recent level 0 incremental backup.
*Oracle Block Change Tracking Once enabled; this new 10g feature records the modified since last backup and stores the log of it in a block change tracking file using the CTW (Change Tracking Writer) process. During backups RMAN uses the log file to identify the specific blocks that must be backed up. This improves RMAN's performance as it does not have to scan whole datafiles to detect changed blocks. Logging of changed blocks is performed by the CTRW process which is also responsible for writing data to the block change tracking file.

C: *RMAN provides support for point-in-time recovery for one or more pluggable databases (PDBs). The process of performing recovery is similar to that of DBPITR. You use the RECOVER command to perform point-in-time recovery of one or more PDBs. However, to recover PDBs, you must connect to the root as a user with SYSDBA or SYSBACKUP privilege
D:DB_FLASHBACK_RETENTION_TARGET specifies the upper limit (in minutes) on how far back in time the database may be flashed back. How far back one can flashback a database depends on how much flashback data Oracle has kept in the flash recovery area.
Range of values0 to 231 - 1
Note:
Reference; OracleDatabase,Backup and Recovery User's Guide 12c

* You can include the CONTAINER clause in several SQL statements, such as the CREATE USER, ALTER USER, CREATE ROLE, GRANT, REVOKE, and ALTER SYSTEM statements. * * CREATE ROLE with CONTAINER (optional) clause / CONTAINER = ALL Creates a common role. / CONTAINER = CURRENT Creates a local role in the current PDB.

Explanation/Reference:
Explanation:
DBMS_FGA.ADD_POLICY(object_schema => 'hr',object_name => 'emp',policy_name =>
'chk_hr_emp',audit_condition => 'dept = "SALES" ',audit_column => 'salary'statement_types =>
'insert,update,delete,select');
Default value for statement_types is SELECT
Setting audit_trail to DBMS_FGA.DB sends the audit trail to the SYS.FGA_LOG$ table in the database

and omits SQL Text and SQL Bind.
Setting audit_trail to DBMS_FGA.DB+EXTENDED sends the audit trail to the SYS.FGA_LOG$ table in

the database and includes SQL Text and SQL Bind.
Setting audit_trail to DBMS_FGA.XML writes the audit trail in XML files sent to the operating system

and omits SQL Text and SQL Bind.
Setting audit_trail to DBMS_FGA.XML+EXTENDED writes the audit trail in XML files sent to the

operating system and includes SQL Text and SQL Bind.
Default value fo audit_trail parameter in DBMS_FGA.ADD_POLICY is DB+EXTENDED