Solaris Cluster HA-Oracle with Oracle Database using DataGuard Starts the Database Incorrectly
Last updated on FEBRUARY 09, 2017
Applies to:Solaris Cluster - Version 4.3 and later
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on SPARC (64-bit)
In a Solaris Cluster HA-Oracle configuration one can set Standby_mode and Dataguard_role according to the desired Database and Dataguard operation mode. However after a resource group switchover or a failover the Database is started in a incorrect mode.
For example when Dataguard_role=STANDBY and there is a switch or fail over then the database maybe started "mounted".
Here we expect that the Database is READ ONLY.
Type string. Default is LOGICAL. This property specifies the mode of the standby database. This property is used by Oracle Solaris Cluster HA
for Oracle data service only when the Dataguard_role property is set to STANDBY to determine the type of standby database. The permitted values for
this property are as follows:
- LOGICAL -> Specifies a logical standby database.
- PHYSICAL -> Specifies a physical standby database.
- SNAPSHOT -> Beginning with Oracle 11g, specifies a snapshot standby database.
There were enhancements in Oracle Datguard in newer releases with Oracle Active Data Guard, it is now possible to perform redo log applies from a Primary to a Physical Standby database and open the database for READ ONLY.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms