Database Reference
In-Depth Information
Do you really want to execute the above repair (enter YES or NO)? YES
executing repair script
Once the restore is complete, all we need to do is open the PDB:
RMAN> alter pluggable database mypdb open;
Statement processed
Note that the actions you take to restore a database will differ based on the nature of
the failure. However the Data Recovery Advisor will take into account the nature of the
failure, the type of database you are running (ARCHIVELOG, NOARCHIVLOG, CDB,
non-CDB) and perform the type of restore that would be required for that database and the
failure that was experienced.
Summary
WHEW! This is a long chapter and we have covered quite a bit of material. I think now is a
good time to grab a drink and just mull over everything that you have read. I'd even suggest
something sweet to get your blood sugar level up a little bit because this has been heavy,
skull crushing, reading.
In this chapter, we talked about some advanced RMAN recovery concepts. First, we
talked about changing database incarnations. You will want to know how to change
incarnations of your database because this provides the ability to restore your database
from previous incarnations in certain cases.
The ability of RMAN to duplicate databases is very powerful. The Oracle OCP exam
will include questions about this functionality, and we strongly suggest you go through
the exercise of performing database duplication. The first few times, it can be a frustrating
exercise, but it's well worth the experience.
Oracle Database 12
c
offers a number of different options with respect to database
duplication, so make sure you understand what these different options are and when
they can, or should, be used.
Tablespace point-in-time recovery is an RMAN feature that makes recovering tablespaces
to specific points in time easy to do. We covered the basics of TSPITR, which you will need
to know for your OCP exam, but we encourage you to do further research into more custom-
ized methods of doing TSPITR that might meet your unique needs.
Also in this chapter, we discussed disaster recovery. This is the end game of backup and
recovery (or as one person once told us, it should be called recovery and backup since
recov-
ery
is the really important part). We gave you an outline of the process to follow to get your
database back up to speed should you lose the whole database server.
We also took that discussion a bit further and addressed ways to copy a database to a
new host. We dealt with byte semantic incompatibility issues, database duplication, backup
and restore with RMAN, and other methods that might be used in different cases.
Search WWH ::
Custom Search