Backup and Recovery Scenarios

Backup and Recovery Scenarios

Doc ID: 94114.1

In this Document

Purpose

Last Review Date

Instructions for the Reader

Troubleshooting Details

BACKUP SCENARIOS

a) Consistent backups

b) Inconsistent backups

c) Database Archive mode

d) Backup Methods

e) Incremental backups

f) Support scenarios

RECOVERY SCENARIOS

1. Online Block Recovery.

2. Thread Recovery.

3. Media Recovery.

Media Failure and Recovery in Noarchivelog Mode

Media Failure and Recovery in Archivelog Mode

a) Point in Time recovery:

b) Recovery without control file

c) Recovery of missing datafile with rollback segments

d) Recovery of missing datafile without undo segments

e) Recovery with missing online redo logs

f) Recovery with missing archived redo logs

g) Recovery with resetlogs option

h) Recovery with corrupted undo segments.

i) Recovery with System Clock change.

j) Recovery with missing System tablespace.

k) Media Recovery of offline tablespace

l) Recovery of Read-Only tablespaces

Applies to:

Oracle Server – Enterprise Edition – Version: 7.2 to 10.2

Oracle Server – Personal Edition – Version: 7.2 to 10.2

Oracle Server – Standard Edition – Version: 7.2 to 10.2

Information in this document applies to any platform.

BACKUP SCENARIOS

a) Consistent backups

A consistent backup means that all data files and control files are consistent to a point in time. I.e. they have the same SCN. This is the only method of backup when the database is in NO Archive log mode.

b) Inconsistent backups

An Inconsistent backup is possible only when the database is in Archivelog mode. You must apply redo logs to the data files, in order to restore the database to a consistent state. Inconsistant backups can be taken using RMANwhen the database is open.

Inconsistant backups can also be taken using other OS tools provided the tablespaces (or database) is put into backup mode.

ie: SQL> alter tablespace data begin backup;

SQL> alter database begin backup; (version 10 and above only)

c) Database Archive mode

The database can run in either Archivelog mode or noarchivelog mode. When you first create the database, you specify if it is to be in Archivelog mode. Then in the init.ora file you set the parameter log_archive_start=true so that archiving will start automatically on startup.

If the database has not been created with Archivelog mode enabled, you can issue the command whilst the database is mounted, not open.

SQL> alter database Archivelog;.

SQL> log archive start

SQL> alter database open;

SQL> archive log list

This command will show you the log mode and if automatic archival is set.

d) Backup Methods

Essentially, there are two backup methods, hot and cold, also known as online and offline, respectively. A cold backup is one taken when the database is shutdown. The database must be shutdown cleanly. A hot backup is on taken when the database is running. Commands for a hot backup:

For non RMAN backups:

1. Have the database in archivelog mode (see above)

2. SQL> archive log list

–This will show what the oldest online log sequence is. As a precaution, always keep the all archived log files starting from the oldest online log sequence.

3. SQL> Alter tablespace tablespace_name BEGIN BACKUP;

or SQL> alter database begin backup (for v10 and above).

4. –Using an OS command, backup the datafile(s) of this tablespace.

5. SQL> Alter tablespace tablespace_name END BACKUP

— repeat step 3, 4, 5 for each tablespace.

or SQL> alter database end backup; for version 10 and above

6. SQL> archive log list

—do this again to obtain the current log sequence. You will want to make sure you have a copy of this redo log file.

7. So to force an archived log, issue

SQL> ALTER SYSTEM SWITCH LOGFILE

A better way to force this would be:

SQL> alter system archive log current;

8. SQL> archive log list

This is done again to check if the log file had been archived and to find the latest archived sequence number.

9. Backup all archived log files determined from steps 2 and 8.

10. Back up the control file:

SQL> Alter database backup controlfile to ‘filename’

For RMAN backups:

see Note.<397315.1> RMAN – Sample Backup Scripts 10g

or the appropriate RMAN documentation.

e) Incremental backups

These are backups that are taken on blocks that have been modified since the last backup. These are useful as they don’t take up as much space and time. There are two kinds of incremental backups Cumulative and Non cumulative.

Cumulative incremental backups include all blocks that were changed since the last backup at a lower level. This one reduces the work during restoration as only one backup contains all the changed blocks.

Noncumulative only includes blocks that were changed since the previous backup at the same or lower level.

Using rman, you issue the command “backup incremental level n”

Oracle v9 and below RMAN will back up empty blocks, oracle v10.2 RMAN will not back up empty blocks

f) Support scenarios

When the database crashes, you now have a backup. You restore the backup and

then recover the database. Also, don’t forget to take a backup of the control

file whenever there is a schema change.

RECOVERY SCENARIOS

Note: All online datafiles must be at the same point in time when completing recovery;

There are several kinds of recovery you can perform, depending on the type of failure and the kind of backup you have. Essentially, if you are not running in archive log mode, then you can only recover the cold backup of the database and you will lose any new data and changes made since that backup was taken. If, however, the database is in Archivelog mode you will be able to restore the database up to the time of failure. There are three basic types of recovery:

1. Online Block Recovery.

This is performed automatically by Oracle.(pmon) Occurs when a process dies while changing a buffer. Oracle will reconstruct the buffer using the online redo logs and writes it to disk.

2. Thread Recovery.

This is also performed automatically by Oracle. Occurs when an instance crashes while having the database open. Oracle applies all the redo changes in the thread that occurred since the last time the thread was checkpointed.

3. Media Recovery.

This is required when a data file is restored from backup. The checkpoint count in the data files here are not equal to the check point count in the control file.

Now let’s explain a little about Redo vs Undo.

Redo information is recorded so that all commands that took place can be repeated during recovery. Undo information is recorded so that you can undo changes made by the current transaction but were not committed. The Redo Logs are used to Roll Forward the changes made, both committed and non- committed changes. Then from the Undo segments, the undo information is used to

rollback the uncommitted changes.

Media Failure and Recovery in Noarchivelog Mode

In this case, your only option is to restore a backup of your Oracle files. The files you need are all datafiles, and control files. You only need to restore the password file or parameter files if they are lost or are corrupted.

Media Failure and Recovery in Archivelog Mode

In this case, there are several kinds of recovery you can perform, depending on what has been lost. The three basic kinds of recovery are:

1. Recover database – here you use the recover database command and the database must be closed and mounted. Oracle will recover all datafiles that are online.

2. Recover tablespace – use the recover tablespace command. The database can be open but the tablespace must be offline.

3. Recover datafile – use the recover datafile command. The database can be open but the specified datafile must be offline.

Note: You must have all archived logs since the backup you restored from, or else you will not have a complete recovery.

a) Point in Time recovery:

A typical scenario is that you dropped a table at say noon, and want to recover it. You will have to restore the appropriate datafiles and do a point-in-time recovery to a time just before noon.

Note: you will lose any transactions that occurred after noon. After you have recovered until noon, you must open the database with resetlogs. This is necessary to reset the log numbers, which will protect the database from having the redo logs that weren’t used be applied.

The four incomplete recovery scenarios all work the same:

Recover database until time ‘1999-12-01:12:00:00’;

Recover database until cancel; (you type in cancel to stop)

Recover database until change n;

Recover database until cancel using backup controlfile;

Note: When performing an incomplete recovery, the datafiles must be online. Do a select * from v$recover_file to find out if there are any files which are offline. If you were to perform a recovery on a database which has tablespaces offline, and they had not been taken offline in a normal state, you will lose them when you issue the open resetlogs command. This is because the data file needs recovery from a point before the resetlogs option was used.

b) Recovery without control file

If you have lost the current control file, or the current control file is inconsistent with files that you need to recover, you need to recover either by using a backup control file command or create a new control file. You can also recreate the control file based on the current one using the ‘SQL> backup control file to trace’ command which will create a script for you to run to create a new one. Recover database using backup control file command must be used when using a control file other that the current. The database must then be opened with

resetlogs option.

c) Recovery of missing datafile with rollback segments

The tricky part here is if you are performing online recovery. Otherwise you can just use the recover datafile command. Now, if you are performing an online recovery, you will need to create a new undo tablespace to be used. Once the old tablespace has been recovered it can be dropped once any uncommitted transactions have rolled back.

d) Recovery of missing datafile without undo segments

There are three ways to recover in this scenario, as mentioned above.

1. recover database;

2. recover datafile ‘c:orantdatabaseusr1orcl.ora’;

3. recover tablespace user_data;

e) Recovery with missing online redo logs

Missing online redo logs means that somehow you have lost your redo logs before they had a chance to archived. This means that crash recovery cannot be performed, so media recovery is required instead. All datafiles will need to be restored and rolled forwarded until the last available archived log file is applied. This is thus an incomplete recovery, and as such, the recover

database command is necessary.

As always, when an incomplete recovery is performed, you must open the database with resetlogs.

Note: the best way to avoid this kind of a loss, is to mirror your online log files.

f) Recovery with missing archived redo logs

If your archives are missing, the only way to recover the database is to restore from your latest backup. You will have lost any uncommitted

transactions which were recorded in the archived redo logs. Again, this is why Oracle strongly suggests mirroring your online redo logs and duplicating copies of the archives.

g) Recovery with resetlogs option

Reset log option should be the last resort, however, as we have seen from above, it may be required due to incomplete recoveries. (recover using a backup control file, or a point in time recovery). It is imperative that you backup up the database immediately after you have opened the database with reset logs. It is possible to recover through a resetlogs, and made easier with Oracle V10, but easier

to restore from the backup taken after the resetlogs

h) Recovery with corrupted undo segments.

If an undo segment is corrupted, and contains uncommitted system data you may not be able to open the database.

The best alternative in this situation is to recover the corrupt block using the RMAN blockrecover command next best would be to restore the datafile from backup and do a complete recovery.

If a backup does not exist and If the database is able to open (non system object) The first step is to find out what object is causing the rollback to appear corrupted. If we can determine that, we can drop that object.

So, how do we find out if it’s actually a bad object?

1. Make sure that all tablespaces are online and all datafiles are online. This can be checked through via the v$recover_file view.

2. Put the following in the init.ora:

event = “10015 trace name context forever, level 10”

This event will generate a trace file that will reveal information about the transaction Oracle is trying to roll back and most importantly, what object Oracle is trying to apply the undo to.

Note: In Oracle v9 and above this information can be found in the alert log.

Stop and start the database.

3. Check in the directory that is specified by the user_dump_dest parameter (in the init.ora or show parameter command) for a trace file that was generated at startup time.

4. In the trace file, there should be a message similar to: error recovery tx(#,#) object #.

TX(#,#) refers to transaction information.

The object # is the same as the object_id in sys.dba_objects.

5. Use the following query to find out what object Oracle is trying to perform recovery on.

select owner, object_name, object_type, status

from dba_objects where object_id =