Working Notes

RMAN: SQL commands  Description: This is one of those 'duh' features that makes so much sense that Oracle decided to implement four version after the introduction of RMAN. Previous to 12c, RMAN would execute SQL statements like so: NOTE: the SELECT statement is executed, but no results are returned to the user. While this is useful for scripting DDL statements. Now, with Oracle 12c, we get results like so: Voila! Results. Use Cases: Verifying that object recovery is successful.  Scripting additional changes to be implemented immediately upon recovery.  Enabling Data Guard commands Any shell scripts which execute RMAN commands, and then exits RMAN to connect to SQLPlus can be immediately simplified to perform these actions in one context.  NOTE: RMAN !=SQLPlus. Formatting options are not available here. RMAN is providing better SQL Client functionality, but nothing nearly as robust as SQLPlus. 

RMAN: SYSBACKUP Role Oracle has released several roles specifically for administers to perform specific actions. With the release of Oracle 12c, there is a new role specifically for managing recovery operations. the SYSBACKUP role allows named credentials to be used to restore partitions, tables views and so on, without necessarily needing to connect to with the SYSDBA privilege. Simply grant the role to the user, like you normally would and then that user can connect with named credentials. The SYSBACKUP role includes the following privileges by default: Select any transaction Unlimited tablespace Resumable Create any cluster Drop tablespace Alter session Audit any Create any table Create any dictionary Alter system Alter database Select any dictionary Alter tablespace SELECT_CATALOG_ROLE NOTE: no object grants are included in this privilege. Backup Operator does not necessarily need access to the data, only to recover data a specific point...