There is a growing need to provide maximum availability of mission critical systems.
Oracle provides several alternatives to help maintain high availability. One alternative is the use of standby databases. A standby
database is a backup copy of your production database. It is maintained on an identically configured but different machine. The names of the disk drives, directory paths, and files should ideally be the same.
As your production system runs, copies of the archive log files are saved to the secondary system and applied to the standby database at regular intervals. This means that the standby database is always a little behind the primary system because there is redo log information that isn't on the secondary system.
In the event of a failure, the secondary system can be activated and the standby database opened for use by your user community. The secondary system becomes your primary system and the standby database becomes your production database. Once the original primary system has been fixed, it can be used as the new secondary system maintaining your standby database.
While the standby database does not contain the most current data, it does maintain high availability with a minimal lose of data.
You can create a standby database by following these steps:
- Backup the data files
- Create the standby control file
- Archive the current redo log files
- Copy the standby control file, data files, and archived redo logs to the standby system
- Bring the standby database up in nomount mode
- Mount the database as a standby database
- Apply the archived log files
More information on standby databases is contained in the Oracle8 release documentation set.
The next lesson is the module wrap-up.