 | ||
| About deploying Storage Foundation for Databases (SFDB) tools with Oracle Data Guard | ||
|---|---|---|
| Prev | Using Storage Foundation for Databases (SFDB) tools in a replicated environment | Next |
| ||
| About deploying Storage Foundation for Databases (SFDB) tools with Oracle Data Guard | ||
|---|---|---|
| Prev | Using Storage Foundation for Databases (SFDB) tools in a replicated environment | Next |
The SFDB tools functionality is extended to support standby databases in an Oracle Data Guard environment.
Oracle Data Guard terminology:
Primary Database: Also referred to as 'Production Database', this database is accessed by most of the user applications.
Standby Database: A standby database is a transactionally consistent copy of the primary database.
Data Guard Configuration: A Data Guard configuration consists of one production database and one or more standby databases.
Physical Standby Database: A physically identical copy of the primary database, with on disk database structures that are identical to the primary database on a block-for-block basis.
The following point-in-time copy methods can be used on a Physical Standby database:
For cloning a standby read-write access database with Oracle Data Guard:
Physical standby databases are read-only databases. Under normal circumstances, they offer limited utility value since you can not update their contents.
Using the Data Guard support feature, DBI commands can clone a read-only standby database into a writable database.
In environments where the Oracle Active Data Guard feature is used, the redo log application must be stopped explicitly on standby database before taking a database snapshot.