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

Mixing NOARChivelOG and ARChivelOG Modes

In the real world, you might find that some of your databases are running in NOARCHIVELOG
mode and some of your databases are running in ARCHIVELOG mode. For example, your
development and test databases may be able to be shut down at night for backups. Addition-
ally, they might not have a need for point-in-time or point-of-failure recovery. Thus, NOAR-
CHIVELOG mode is just fine for them.

You may find that your production databases have different requirements. First, it may
be that shutting down your production systems for backups at any time is not accept-
able to your customer. Further, you probably will also find that people prefer not to lose
data in production and that they would prefer to be able to restore the database and then
recover all work that occurred after the last backup. You will have to put your database in
ARCHIVELOG mode to satisfy those requirements.

Perhaps you are asking yourself, “What about this Fast Recovery Area
thing I've been hearing about?” Since the Fast Recovery Area (FRA, pre-
viously called the Flash Recovery Area) typically is not used for manual
backups, we will defer discussion of the FRA until we discuss RMAN in
later chapters. Thus, the parameters related to the RMAN and the FRA
are not included in Table 1.2.

TABle 1.2 Oracle Parameters Associated with User-Managed Backup and Recovery

Parameter Name Description

LOG_ARCHIVE_DEST Indicates the destination to copy archived redo logs to. Typ-

ically this parameter is not set and the LOG_ARCHIVE_DEST_n
parameter is set instead.

LOG_ARCHIVE_DEST_ n Indicates one of up to 10 destinations to copy archived redo

logs to. The first destination starts with 1 ( LOG_ARCHIVE_
DEST_01 ).

LOG_ARCHIVE_DEST_STATE_n Indicates the state of LOG_ARCHIVE_DEST_n ( ENABLED ,

DEFERRED , or ALTERNATE ).

LOG_ARCHIVE_FORMAT Indicates the format of the archived redo log filenames.