Performing Oracle User-Managed Backups - OCP: Oracle Database 12c Administrator Certified Professional - page 50

Exam Essentials
The following topics are specifically listed as essential test items and part of the content of
the Oracle Database 12 c OCP Exam.
Describe types of database failures. Understand the kinds of database failures that can
occur. Also understand what causes those failures and what kind of recovery is required in
the event those failures occur.
Describe tools available for backup and recovery tasks. Understand the various tools/
methods (ie: shell scripts) that are available to backup and recover and Oracle database.
Describe generally how each tool works.
Describe RMAN and maximum availability architecture. Understand and be able to
describe the benefits of Oracle's Maximum Availability Architecture (MAA). Also be able
to describe what RMAN is and what it's used for.
Configure your control file and online redo logs for recoverability. Understand the benefit
of multiplexing the control files and the online redo logs. Understand why it is important to
back up your control file. Understand the different methods of backing up your control file.
Understand what a backup control file is.
Describe and tune instance recovery. Understand what instance recovery is and why it's
critical to database availability. Describe how to monitor and configure the database for
optimal instance recovery performance.
Perform backup and recovery in NOARCHIVELOG mode. Understand the steps that
need to be performed to do an offline backup. Understand the difference between an offline
backup and an online backup and how these differences can be used to decide the optimal
backup strategy.
Enable ARCHIVELOG mode. Understand what ARCHIVELOG mode is, and how to
configure the database so that it's running in ARCHIVELOG mode. Understand what
archived redo logs are and why they are important, how they are created and where they
are created.
Back up a control file to trace. Understand how to create a backup of the control file to a
trace file, and where that trace file is located.