Data Guard NOT supported in Oracle Standard Edition (Doc ID 305360.1)

Data Guard and Oracle Standard Edition (Doc ID 305360.1) PURPOSE ------- This note outlines the usage of standby features with Standard Edition releases of the Oracle Database software from Oracle9i Release 1 and up. SCOPE & APPLICATION ------------------- This note is intended for DBAs and Support Engineers. Data Guard and Oracle Standared Edition ---------------------------------------- Oracle Data Guard is available only as a feature of Oracle Database Enterprise Edition. It is not available with Standard Edition. The following limitations exist using standby databases under Standard Edition: 1. Remote archival can not be configured. Setting the parameter LOG_ARCHIVE_DEST_n to any value will fail. SQL> alter system set log_archive_dest_1='SERVICE=stby'; * ERROR at line 1: ORA-00439: Feature not enabled: Managed standby Note: LOG_ARCHIVE_DEST can be used for local only archival. 2. While you can specify the MANAGED keyword when starting standby recovery: SQL> recover managed standby database disconnect; The managed recovery process (MRP) will not progress once started. It relies on the standby controlfile being updated with the latest available archive log during remote archival from the primary. The archives can be brought over manually and registered into the controlfile but the register attempt will fail instead with the following errors: SQL> alter database register logfile '/stby_arch/arc0055.dbf'; * ERROR at line 1: ORA-00439: Feature not enabled: Managed Standby Manual recovery with 'RECOVER STANDBY DATABASE' SQL will work. The archive log location will be determined based on the setting of the LOG_ARCHIVE_FORMAT and LOG_ARCHIVE_DEST parameters on the standby instance. 3. Switchover will not be possible. 4. Failover must be done with 'ALTER DATABASE ACTIVATE STANDBY DATABASE' 5. The only standby type possible is a physical standby, not logical. 6. The standby environment cannot be managed using the Data Guard Broker or it's interfaces, DGMGRL and the Data Guard GUI from Grid Control. 7. standby_file_management parameter will not work 8. RMAN 'DUPLICATE FOR STANDBY' cannot be used. Overall it is possible to create and maintain a physical standby with Standard Edition releases. However it is left up to the user to handle the archive log transfer to the standby site and the apply of the logs using basic 'RECOVER STANDBY DATABASE' SQL syntax. There is possible data loss in case of primary instance or node or site down. The behaviors such as rolling upgrades can not be used.