This module describes how you can enable automatic archiving of redo log files.
This module discusses the following:
Move your mouse over this icon to show all screenshots.
You can also move your mouse over each individual icon to see only the screenshot
associated with it.
In this module you will learn how to enable automatic archiving. You can do this by setting the LOG_ARCHIVE_START initialization parameter to TRUE. This is not a dynamic parameter, so you must restart your instance after setting the value to TRUE. When the value is TRUE the archiver process starts automatically upon instance startup. Refer to the following sections for detailed instructions:
| Enabling Automatic Archiving at Instance Startup Using SQL*Plus | ||
| Enabling Automatic Archiving at Instance Startup Using EM | ||
You can also start the archiver process without setting the LOG_ARCHIVE_START initialization parameter. However, if you start it in this way, it will not start again if you shut down your instance. This is sometimes referred to as manually starting automatic archiving. Refer to the following sections for detailed instructions:
|
Enabling Automatic Archiving After Instance Startup Using SQL*Plus |
||
| Enabling Automatic Archiving After Instance Startup Using EM | ||
You can enable automatic archiving of filled redo log files with the LOG_ARCHIVE_START initialization parameter. You must set it to TRUE to start the archiver background process at instance startup.
Specify LOG_ARCHIVE_START=TRUE
in the initialization parameter file and restart your instance.
If you are using a server parameter file (SPFILE), you can enable automatic archiving at instance startup by performing the steps below:
| 1. |
Invoke SQL*Plus.
|
| 2. |
Issue the ALTER SYSTEM command to update the LOG_ARCHIVE_START parameter in your SPFILE: ALTER SYSTEM SET log_archive_start=true SCOPE=spfile;
|
| 3. |
Shut down your instance using the NORMAL, IMMEDIATE, or TRANSACTIONAL options: SHUTDOWN IMMEDIATE
|
| 4. |
Restart your instance: STARTUP
|
| 5. |
Verify your changes: ARCHIVE LOG LIST
|
You must set the value of the LOG_ARCHIVE_START initialization parameter to TRUE. You can accomplish that by performing the steps that follow.
Note: Oracle Enterprise Manager 9.2 was used in the examples.
| 1. |
Select START > Programs > Oracle > OraHome92 > Enterprise Manager Console. Select Launch Standalone and click OK.
|
| 2. |
Expand Databases. Expand your database. Expand Instance and select Configuration. You can access the initialization parameters from the General page. Change the value for LOG_ARCHIVE_START to TRUE. You can also specify the destination directory and naming convention for the archived redo log files at this time.
|
| 3. |
Click YES to restart your database instance:
|
You can enable automatic archiving without shutting down the
instance by following the steps outlined below. This does not change the value
of LOG_ARCHIVE_START in the initialization
parameter file. You must set the value to TRUE
to enable automatic archiving when the instance is started again. LOG_ARCHIVE_START
is a static parameter so you cannot change it with the ALTER
SYSTEM command.
Enable archiving at instance startup by performing the steps below:
| 1. |
Invoke SQL*Plus.
|
| 2. |
Issue the ALTER SYSTEM command to start automatic archiving: ALTER SYSTEM ARCHIVE LOG START;
|
| 3. |
Verify your changes: ARCHIVE LOG LIST
|
You can enable automatic archiving without shutting down the instance by following the steps outlined below. This does not change the value of LOG_ARCHIVE_START in the initialization parameter file. You must set the value to TRUE to enable automatic archiving when the instance is started again.
Note: Oracle Enterprise Manager 9.2 was used in the examples.
| 1. |
Select START > Programs > Oracle > OraHome92 > Enterprise Manager Console. Select Launch Standalone and click OK.
|
| 2. |
Expand Databases. Expand your database. Expand Instance and select Configuration. You can enable automatic archiving on the Recovery page:
|
| 3. |
You receive a confirmation that the archiver process is starting.
|