LOG_
ARCHIVE_DEST series of parameters:
■ LOG_ARCHIVE_STATE_ n Defines one of two different states for each archive log destination. If set to ENABLE, the ARCH process will consider the destination associated with this state as a valid archive log destination. If set to DEFER, the ARCH process will not archive logs to the related LOG_ARCHIVE_DEST_ n location.
■ LOG_ARCHIVE_FORMAT Provides a template for Oracle to use when naming archived redo logs. As Oracle creates the archived redo logs, it renames them in such a way that each of the archived redo logs has a unique name assigned to it. Using the LOG_
ARCHIVE_FORMAT parameter, you can manipulate the default naming standard as you require. This parameter has no effect for archived redo logs being created in the FRA.
■ LOG_ARCHIVE_START This parameter is obsolete in Oracle Database 10 g and later versions. Oracle will now start the ARCH process for you automatically.
■ LOG_ARCHIVE_MAX_PROCESSES This parameter defines the number of ARCH
processes that Oracle initially starts when the database is started.
NOTE
If you are running Oracle Database 9 i or earlier, you will need to make sure you set the LOG_ARCHIVE_START parameter to TRUE
when configuring your database for ARCHIVELOG mode. This is
no longer required in Oracle Database 10 g and later.
Each of the different parameters mentioned thus far is defined in the Oracle Database 11 g Reference Manual (which is part of the overall Oracle documentation), should you need further information on them.
In the following example, we have a database we want to put in ARCHIVELOG mode. We will create three different archive log destination directories, including one to a service name that supports an Oracle standby database. We will also enforce the requirements that at least two of these destinations must be written to in order for the movement of the archived redo log to be considered complete, and that the standby database must be one of those two locations. Here is
64 Part II: Setup Principles and Practices
an example of the use of the various database parameter file parameters related to ARCHIVELOG
mode operations:
log archive dest 1 'location d:\oracle\oraarc\robt mandatory'
log archive dest 2 'location z:\oracle\oraarc\robt optional'
log archive dest 3 'service recover1 mandatory'
log archive min succeed dest 2
log archive format "robt %s %t.arc"
In this example, our first archive log destination goes to d:\oracle\oraarc\robt. The second archive log destination is to a secondary location on the Z: drive. We have made this an optional archiving location because it is a networking device (which may not be all that reliable). The third destination is to an Oracle Net service (probably a standby database) called recover1. This will cause Oracle to send the archived redo logs through Oracle Net as they are generated.
Proceeding through the example, by using the LOG_ARCHIVE_MIN_SUCCEED_DEST
parameter, we have indicated that the archived redo logs must be successfully copied to at least two different locations. The format of the archived redo log is defined with the LOG_ARCHIVE_
FORMAT parameter.
The Flash Recovery Area
The flash recovery area (FRA) allows you to centralize storage of all recovery-related files. The FRA can use locally attached storage, the Oracle Cluster File System (OCFS), or Automatic Storage Management (ASM) features. Table 3-1 lists the file types that can be contained within the FRA.
The FRA helps with the management of overall disk space allocation and provides a centralized storage area for all recovery-related files.
Retention of files in the FRA is determined by the RMAN retention policy. This is set via the RMAN configure retention policy command. This command and RMAN retention will be discussed in much more detail later in this chapter. If a file does not have a retention policy associated with it or it’s a permanent file, then it will never be deleted. If a file is not
ARCHIVE_DEST series of parameters:
■ LOG_ARCHIVE_STATE_ n Defines one of two different states for each archive log destination. If set to ENABLE, the ARCH process will consider the destination associated with this state as a valid archive log destination. If set to DEFER, the ARCH process will not archive logs to the related LOG_ARCHIVE_DEST_ n location.
■ LOG_ARCHIVE_FORMAT Provides a template for Oracle to use when naming archived redo logs. As Oracle creates the archived redo logs, it renames them in such a way that each of the archived redo logs has a unique name assigned to it. Using the LOG_
ARCHIVE_FORMAT parameter, you can manipulate the default naming standard as you require. This parameter has no effect for archived redo logs being created in the FRA.
■ LOG_ARCHIVE_START This parameter is obsolete in Oracle Database 10 g and later versions. Oracle will now start the ARCH process for you automatically.
■ LOG_ARCHIVE_MAX_PROCESSES This parameter defines the number of ARCH
processes that Oracle initially starts when the database is started.
NOTE
If you are running Oracle Database 9 i or earlier, you will need to make sure you set the LOG_ARCHIVE_START parameter to TRUE
when configuring your database for ARCHIVELOG mode. This is
no longer required in Oracle Database 10 g and later.
Each of the different parameters mentioned thus far is defined in the Oracle Database 11 g Reference Manual (which is part of the overall Oracle documentation), should you need further information on them.
In the following example, we have a database we want to put in ARCHIVELOG mode. We will create three different archive log destination directories, including one to a service name that supports an Oracle standby database. We will also enforce the requirements that at least two of these destinations must be written to in order for the movement of the archived redo log to be considered complete, and that the standby database must be one of those two locations. Here is
64 Part II: Setup Principles and Practices
an example of the use of the various database parameter file parameters related to ARCHIVELOG
mode operations:
log archive dest 1 'location d:\oracle\oraarc\robt mandatory'
log archive dest 2 'location z:\oracle\oraarc\robt optional'
log archive dest 3 'service recover1 mandatory'
log archive min succeed dest 2
log archive format "robt %s %t.arc"
In this example, our first archive log destination goes to d:\oracle\oraarc\robt. The second archive log destination is to a secondary location on the Z: drive. We have made this an optional archiving location because it is a networking device (which may not be all that reliable). The third destination is to an Oracle Net service (probably a standby database) called recover1. This will cause Oracle to send the archived redo logs through Oracle Net as they are generated.
Proceeding through the example, by using the LOG_ARCHIVE_MIN_SUCCEED_DEST
parameter, we have indicated that the archived redo logs must be successfully copied to at least two different locations. The format of the archived redo log is defined with the LOG_ARCHIVE_
FORMAT parameter.
The Flash Recovery Area
The flash recovery area (FRA) allows you to centralize storage of all recovery-related files. The FRA can use locally attached storage, the Oracle Cluster File System (OCFS), or Automatic Storage Management (ASM) features. Table 3-1 lists the file types that can be contained within the FRA.
The FRA helps with the management of overall disk space allocation and provides a centralized storage area for all recovery-related files.
Retention of files in the FRA is determined by the RMAN retention policy. This is set via the RMAN configure retention policy command. This command and RMAN retention will be discussed in much more detail later in this chapter. If a file does not have a retention policy associated with it or it’s a permanent file, then it will never be deleted. If a file is not
Similar Books
