a copy of the primary database that is updated using archived logs created by the primary database
a copy of the primary database that you can update continually or periodically by using archived logs from the primary database
a database replica created from a backup of a primary database
a database that is constantly in recovery mode, recovering archive log files from the primary database
a transactionally consistent copy of an Oracle production database that is initially created from a backup copy of the primary database
A copy of a production database that you can use for disaster protection. stored script A sequence of RMAN commands stored in the recovery catalog.
A database that contains data replicated from another database (the primary database) through a replication system. The standby database is the database that receives replicated data in a replication system. Sometimes called the replicate database. Contrast with primary database. See also standby data.
Read-only database on the standby node. The standby database, also referred to as the replicated database, is physically identical to the master database. In the event of catastrophic failures, data modification activities "fail over" to the standby database such that it becomes the new master database.
A copy of a production database created using a backup of your primary database. Standby databases are kept synchronized with the primary database by applying archived redo logs over time from the primary database to each standby database. The standby database can take over processing from the primary database, providing nearly continuous database availability. A standby database has its own initialization parameter file, control file, and datafiles.
A copy of a production database that you can use for disaster protection. You can update the standby database with archived redo logs from the production database in order to keep it current. If a disaster destroys the production database, you can activate the standby database and make it the new production database.
An identical copy of a primary database that you can use for disaster protection. You can update your standby database with archived redo logs from the primary database to keep it current. Should a disaster destroy or compromise the primary database, you can fail over to the standby database and make it the new primary database. A standby database has its own initialization parameter file, control file, and datafiles. See also logical standby database, physical standby database, and primary database
Physical copy of a database standing by to take over in the event of a failure. The standby database in a permanent state of recovery and can be opened with minimal recovery required.