CREATE DISKGROUP NORMAL REDUNDANCY
*For Oracle ASM to mirror files, specify the redundancy level as NORMAL REDUNDANCY (2-way mirroring by default for most file types) or HIGH REDUNDANCY (3-way mirroring for all files).

* 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.

Explanation/Reference:
Explanation:
You can use the SQL Performance Analyzer to analyze the SQL performance impact of any type of system change. Examples of common system changes include:
Database upgrades

Configuration changes to the operating system, hardware, or database

Database initialization parameter changes

Schema changes, such as adding new indexes or materialized views

Gathering optimizer statistics

SQL tuning actions, such as creating SQL profiles

References: http://docs.oracle.com/cd/B28359_01/server.111/b28318/intro.htm#CNCPT961

* Evolving SQL Plan Baselines *

2. Create the evolve task by using the DBMS_SPM.CREATE_EVOLVE_TASK function.
This function creates an advisor task to prepare the plan evolution of one or more plans for a
specified SQL statement. The input parameters can be a SQL handle, plan name or a list of plan
names, time limit, task name, and description.
1. Set the evolve task parameters.
SET_EVOLVE_TASK_PARAMETER
This function updates the value of an evolve task parameter. In this release, the only valid
parameter is TIME_LIMIT.
4. Execute the evolve task by using the DBMS_SPM.EXECUTE_EVOLVE_TASK function.
This function executes an evolution task. The input parameters can be the task name, execution
name, and execution description. If not specified, the advisor generates the name, which is
returned by the function.
3: IMPLEMENT_EVOLVE_TASK
This function implements all recommendations for an evolve task. Essentially, this function is
equivalent to using ACCEPT_SQL_PLAN_BASELINE for all recommended plans. Input
parameters include task name, plan name, owner name, and execution name.
5. Report the task outcome by using the DBMS_SPM_EVOLVE_TASK function.
This function displays the results of an evolve task as a CLOB. Input parameters include the task
name and section of the report to include.
Reference: Oracle Database SQL Tuning Guide 12c, Managing SQL Plan Baselines

* Overview, example:
-Log into ncdb12c as sys
-Get the database in a consistent state by shutting it down cleanly.
-Open the database in read only mode
-Run DBMS_PDB.DESCRIBE to create an XML file describing the database.
-Shut down ncdb12c
-Connect to target CDB (CDB2)
-Check whether non-cdb (NCDB12c) can be plugged into CDB(CDB2)
-Plug-in Non-CDB (NCDB12c) as PDB(NCDB12c) into target CDB(CDB2).
-Access the PDB and run the noncdb_to_pdb.sql script.
-Open the new PDB in read/write mode.
*You can easily plug an Oracle Database 12c non-CDB into a CDB. Just create a PDB manifest file for the non-CDB, and then use the manifest file to create a cloned PDB in the CDB.
*Note that to plugin a non-CDB database into a CDB, the non-CDB database needs to be of version 12c as well. So existing 11g databases will need to be upgraded to 12c before they can be part of a 12c CDB.