Performing Manual Archiving

Purpose

This module describes how you can manually archive redo log files.

Topics

This module discusses the following:

	Overview
	Performing Manual Archiving Using SQL*Plus
	Performing Manual Archiving Using EM

Viewing Screenshots

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.

Overview

Back to List of Topics

"Archiving" is defined as the operation in which the archiver background process copies filled online redo log files to offline destinations. An offline copy of an online redo log is called an archived redo log. You must operate the database in ARCHIVELOG mode to archive redo log files.

If automatic archiving is not enabled, you must manually archive groups of filled online redo log files in a timely fashion. If all online redo log file groups are filled, database operation will be suspended until the log writer is able to write to a group.

The manual archiving option is provided so that you can:

	Archive a group when automatic archiving has been stopped because of a problem (for example, the offline storage device specified as the archived redo log destination has experienced a failure or become full)
	Archive a group in a nonstandard fashion (for example, archive one group to one offline storage device, the next group to a different offline storage device, and so on)
	Re-archive a group if the original archived version is lost or damaged

Performing Manual Archiving Using SQL*Plus

Back to List of Topics

You can manually archive groups of online redo log files with the following command. When you issue this command, your user process is used to archive all non-current redo log groups. This command does not start the Archiver background process. You will need to monitor the filling of the online redo log file groups so that you can archive them on a timely basis. If you fail to archive the filled online redo log file before the log writer process needs to write to it again, database operation will be suspended temporarily while waiting for you to do so.

ALTER SYSTEM ARCHIVE LOG ALL;

Performing Manual Archiving Using Enterprise Manager

Back to List of Topics

Note: Oracle Enterprise Manager 9.2 was used in the examples.

Move your mouse over this icon to hide all screenshots