Database Reference
In-Depth Information
FILE_TYPE PERCENT_SPACE_USED PERCENT_SPACE_RECLAIMABLE NUMBER_OF_FILES
----------------------- ------------------ ------------------------- ---------------
CONTROL FILE 3.6 0 1
REDO LOG 71.4 0 7
ARCHIVED LOG 3.4 .8 3
BACKUP PIECE 0 0 0
IMAGE COPY 0 0 0
FLASHBACK LOG 0 0 0
FOREIGN ARCHIVED LOG 0 0 0
AUXILIARY DATAFILE COPY 0 0 0
8 rows selected.
■
Oracle's documentation states that files that are required for Stream may be deleted from the Fra. ensure
you have backups of these files, for example by creating intra-day archivelog backups
Caution
The above usage of the Fast Recovery Area does not relieve you from the task of monitoring of the archive
destination. It should however allow you to simplify the management of archived redo logs on systems where they
are not constantly backed up and purged by RMAN.
Data Guard specifics for Pluggable Databases
Pluggable Databases are one of the most interesting new features of Oracle 12c and you can read a lot about them in
Chapter 7. There are a few specifics when it comes to Data Guard and Pluggable Databases. No need to worry, all the
previous examples have been using a Container Database (CDB). The following cases need closer examination:
•
Creation of a new Pluggable Database on the primary database
•
Plugging in a previously unknown PDB into the primary database
•
Unplugging a PDB from the primary
•
Dropping a PDB
As of this writing the scope of Data Guard is the Container Database, not the individual Pluggable Database.
As you saw earlier in the chapter, role changes are performed for the Container. Following that logic you will notice
that managed recovery is active for the CDB, not selectively for individual PDBs.
Using Data Guard with the Active Data Guard option greatly simplifies management of the standby databases.
Without Active Data Guard the behavior is similar to that of transportable tablespaces in releases before 12c.
When you plan to plug in a transportable tablespace set in the primary, it is your responsibility to make the same
transportable tablespace data set available at the standby. The following examples will use the transparent solution
with Active Data Guard in an effort not to extend the chapter even further. Be warned though that you need to be
appropriately licensed to use the steps described here.
Creating a new Pluggable Database on the primary database
The creation of a new PDB is transparent to the end user. With Active Data Guard implemented the “create pluggable
database” statement is executed on the standby database and the pluggable database is created. Any files that needed
copying are then copied over the network. This copying is not very spectacular, since it simply works as the example
Search WWH ::
Custom Search