Step1(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 statisticsHere 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.

Incorrect:
Not B: An image copy is an exact copy of a single datafile, archived redo log file, or control file.
Image copies are not stored in an RMAN-specific format. They are identical to the results of
copying a file with operating system commands. RMAN can use image copies during RMAN
restore and recover operations, and you can also use image copies with non-RMAN restore and
recovery techniques.
Not G: You cannot use section size for a full database backup.
Note:
*If you specify the SECTION SIZE parameter on the BACKUP command, then RMAN produces a multisection backup. This is a backup of a single large file, produced by multiple channels in parallel, each of which produces one backup piece. Each backup piece contains one file section of the file being backed up.
*Some points to remember about multisection backups include:

Explanation/Reference:
Explanation:
* SHUTDOWN [ABORT | IMMEDIATE | NORMAL | TRANSACTIONAL [LOCAL]]
Shuts down a currently running Oracle Database instance, optionally closing and dismounting a database.
If the current database is a pluggable database, only the pluggable database is closed. The consolidated instance continues to run.
Shutdown commands that wait for current calls to complete or users to disconnect such as SHUTDOWN NORMAL and SHUTDOWN TRANSACTIONAL have a time limit that the SHUTDOWN command will wait.
If all events blocking the shutdown have not occurred within the time limit, the shutdown command cancels with the following message:
ORA-01013: user requested cancel of current operation
* If logged into a CDB, shutdown closes the CDB instance.
To shutdown a CDB or non CDB, you must be connected to the CDB or non CDB instance that you want to close, and then enter
SHUTDOWN
Database closed.
Database dismounted.
Oracle instance shut down.
To shutdown a PDB, you must log into the PDB to issue the SHUTDOWN command.
SHUTDOWN
Pluggable Database closed.
Note:
* Prerequisites for PDB Shutdown
When the current container is a pluggable database (PDB), the SHUTDOWN command can only be used if:
The current user has SYSDBA, SYSOPER, SYSBACKUP, or SYSDG system privilege.
The privilege is either commonly granted or locally granted in the PDB.
The current user exercises the privilege using AS SYSDBA, AS SYSOPER, AS SYSBACKUP, or AS SYSDG at connect time.
To close a PDB, the PDB must be open.

A: The APPEND keyword tells SQL*Loader to preserve any preexisting data in the table. Other options allow you to delete preexisting data, or to fail with an error if the table is not empty to begin with.
B (not D): Note:
* SQL*Loader-00210: first data file is empty, cannot process the FIELD NAMES record Cause: The data file listed in the next message was empty. Therefore, the FIELD NAMES FIRST FILE directive could not be processed. Action: Check the listed data file and fix it. Then retry the operation
E:
*A comma-separated values (CSV) (also sometimes called character-separated values, because
the separator character does not have to be a comma) file stores tabular data (numbers and text)
in plain-text form. Plain text means that the file is a sequence of characters, with no data that has
to be interpreted instead, as binary numbers. A CSV file consists of any number of records,
separated by line breaks of some kind; each record consists of fields, separated by some other
character or string, most commonly a literal comma or tab. Usually, all records have an identical
sequence of fields.
*Fields with embedded commas must be quoted.
Example:
1997,Ford,E350,"Super, luxurious truck"
Note:
*SQL*Loader is a bulk loader utility used for moving data from external files into the Oracle database.

Block corruptions can be divided Into Interblock corruption and intrablock corruption. In intrablock corruption. the 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