Explanation/Reference:
Explanation:
http://www.techonthenet.com/oracle/tablespaces/alter_tablespace.php

Explanation/Reference:
Step 1 (2). Seed column usage
Oracle must observe a representative workload, in order to determine the appropriate column groups.
Using the new procedure DBMS_STATS.SEED_COL_USAGE, you tell Oracle how long it should observe the workload.
Step 2: (3) You don't need to execute all of the queries in your work during this window. You can simply run explain plan for some of your longer running queries to ensure column group information is recorded for these queries.
Step 3. (1) Create the column groups
At this point you can get Oracle to automatically create the column groups for each of the tables based on the usage information captured during the monitoring window. You simply have to call the DBMS_STATS.CREATE_EXTENDED_STATS function for each table.This function requires just two arguments, the schema name and the table name. From then on, statistics will be maintained for each column group whenever statistics are gathered on the table.
Note:
* DBMS_STATS.REPORT_COL_USAGE reports column usage information and records all the SQL operations the database has processed for a given object.
* The Oracle SQL optimizer has always been ignorant of the implied relationships between data columns within the same table. While the optimizer has traditionally analyzed the distribution of values within a column, he does not collect value-based relationships between columns.
* Creating extended statistics
Here are the steps to create extended statistics for related table columns withdbms_stats.created_extended_stats:
1 - The first step is to create column histograms for the related columns.
2 - Next, we run dbms_stats.create_extended_stats to relate the columns together.
Unlike a traditional procedure that is invoked via an execute ("exec") statement, Oracle extended statistics are created via a select statement.

Explanation/Reference:
Explanation:
A: Occasionally a database closes abnormally with one or more distributed transactions in doubt (neither committed nor rolled back). When you reopen the database and recovery is complete, the RECO background process automatically, immediately, and consistently resolves any in-doubt distributed transactions.
C: Crash and instance recovery involve two distinct operations: rolling forward the current, online datafiles by applying both committed and uncommitted transactions contained in online redo records, and then rolling back changes made in uncommitted transactions to their original state.
D: The SMON background process performs instance recovery, applying online redo automatically. No user intervention is required.
References:
https://docs.oracle.com/cd/B28359_01/server.111/b28318/startup.htm
https://docs.oracle.com/database/121/CNCPT/startup.htm

Reference:http://docs.oracle.com/database/121/BRADV/rcmresind.htm#BRADV695(Limitat ions of Recovering Tablesand Table Partitions from RMAN Backups)