Entering content frame

Background documentation Overwrite Mode for the Log Area Locate the document in its SAP Library structure

Use this log setting to control whether the log area can be overwritten or not without backing up the log entries.

Normal Log Backups

By default, the log area can be overwritten only if the appropriate log entries have been backed up. You must therefore make regular log backups (see Backing Up).

The log entries of the log area and the log backups are then available if you need to restore the database. If these entries and the data backups are complete and available without gaps, you can restore the database up to any point in time.

If you change the overwrite mode, and then reactivate the default setting, you must then make a complete data backup.

Overwriting the Log Area Without a Log Backup

The log area is overwritten cyclically, even if you do not perform any log backups.

This interrupts the log backup history. Only the log entries of the log area are available if you need to restore the database. This usually means that you cannot restore your database instance up to the last COMMIT before the crash, or to any other time; instead, you can restore it only to the state it had at the time of the last data backup.

You can only restore the database to a time of your choice if all the log entries written after the data backup exist in the log area (which means that the log area has not been overwritten since the data backup).

Procedure

You can set the overwrite mode with the database instance in the operational state ADMIN or ONLINE. Use, for example, the Database Manager GUI, as described in Changing Log Settings (Configuration Wizard).

 

 

Leaving content frame