standby database -- Compatibility and Operational Requirements

Compatibility and Operational Requirements

Note the following requirements for maintaining a standby database:

The primary database must run in ARCHIVELOG mode.

A standby database in manual recovery mode operates only on Oracle release 7.3 or higher.

A standby database in managed recovery mode operates only on Oracle release 8.1 or higher.

A standby database in read-only mode operates only on Oracle release 8.1.5 or higher.

The redo logs that you apply to the standby database must be either archived or noncurrent online redo logs. Note that you can salvage the transactions in the current redo log by archiving it manually.

You must use the same version and release of the operating system on the primary and standby hosts. The standby host can, however, use a different directory structure.

You should use the same version, release, and patch of the Oracle RDBMS for the primary and standby databases so that failover operations are not compromised.

The primary database and standby database cannot share the same control file.

If you place your primary and standby databases on the same host, some operating systems will not allow you to mount two instances with the same database name on the same machine simultaneously. Workarounds for this situation exist for every platform.

You cannot activate a standby database and then return it to managed recovery mode; an activated standby database becomes a normal primary database.

 

Oracle8.1 或以下版本：  日誌不能自動傳過來,可透過指令碼自動ftp 或 nfs 自動 apply 也不能.需要用指令碼定時 apply

 

Oracle 8.1 或以上版本：  可以透過managed revery database 方式自動恢復data .