SAPDBA: Archive mode

If you work with an Oracle database with an OPS configuration (see Oracle Databases and Parallel Server Option (OPS)), you can use the Select thread/instance option to choose the parallel instance for which you want to perform one of the possible operations.

You can change both the database mode (Toggle database log mode) and the archiving mode (Toggle automatic archival).

Prerequisites

LOCAL INSTANCE: C11
DATABASE LOG MODE: archivelog

SELECTED INSTANCE: C11
INSTANCE STATE: opened
AUTOMATIC ARCHIVAL: enabled

a	Toggle database log mode
b	Toggle automatic archival
c	Show all archive information
d	Show complete archive history
e	Select thread/instance
f	Refresh information
q	Return

Features

Use the option Show complete archive history to obtain an overview of the redo entries and answer the following questions:

• Which online redo entries are affected?
• Which of the offline redo entries are still in the archiving directory on disk?
• Which of the files have already been archived to another volume?
• Which redo entries are needed to make the backup consistent?

For each database instance the following information is displayed:

• Last complete backup of the database (LAST FULL BACKUP) and the redo log files written during the backup (HAS BEGUN AND ENDED AT LOG: an interval of log sequence numbers is usually specified for an online backup).
• Log sequence number of the offline and online redo log files (the offline redo logs are numbered starting with First_LOG, the current online redo log file is Curr_LOG)
• Log sequence numbers of the offline redo log files that have already been archived (up to and including the file with the log sequence number SAVED_LOGS)

If an error situation occurs in the database, making a recovery necessary, you should view this information before starting the recovery.

To display an overview of the status of the archiving process in your database, use the option Show all archive information. If the local and selected instance correspond (particularly in the case of a non-OPS configuration), the following information appears:

• LOCAL INSTANCE
: Name of the local instance (e.g. C11)
LOCAL INSTANCE STATE: Status of the instance (for example, open, open for DBAs, mounted)
DATABASE LOG MODE: Database mode (archivelog/noarchivelog)
AUTOMATIC ARCHIVAL: Archiving mode (enabled/disabled)
• MAX LOGSIZE
: Size of the individual online redo log files (SAP delivers the online redo log files with a size of 20 MB each).
• Archive directory details:
LOG DIRECTORY (path), FREE SPACE (size of available freespace), LOGS ARCHIVED (number of offline redo log files).
• Details for online redo log files:
ONLINE REDO LOGS (number of redo log files), ONLINE REDO GROUPS (redo log groups), OLDEST ONLINE LOG (log number of oldest online redo log file), NEXT TO ARCHIVE (log number of next online redo log file for archiving), CURRENT LOG (Number of the current online redo log file)
• LOG STATUS
: O.K. or a warning ( danger of archiver stuck or archiver stuck).

If the local and selected instance do not match, the following appears:

• Information on the local instance:
LOCAL INSTANCE, LOCAL INSTANCE STATE, DATABASE LOG MODE
• Information on the selected parallel instance:
INSTANCE (THREAD), AUTOMATIC ARCHIVAL, NEXT TO ARCHIVE, CURRENT LOG, LOG STATUS