Skip Navigation Links | |
Exit Print View | |
![]() |
Oracle Solaris Cluster Data Service for Oracle Guide Oracle Solaris Cluster 4.0 |
1. Installing and Configuring HA for Oracle
Overview of the Installation and Configuration Process for HA for Oracle
Planning the HA for Oracle Installation and Configuration
Configuration Planning Questions
How to Configure the Oracle Database Access Using Solaris Volume Manager
How to Configure the Oracle Database Access Using Oracle ASM
How to Configure an Oracle Grid Infrastructure for Clusters SCAN Listener
Installing the Oracle ASM Software
Verifying the Oracle ASM Software Installation
Installing the Oracle Software
How to Install the Oracle Software
How to Set the Oracle Kernel Parameters
Verifying the Oracle Installation and Configuration
How to Verify the Oracle Installation
How to Create a Primary Oracle Database
Setting Up Oracle Database Permissions
How to Set Up Oracle Database Permissions
Installing the HA for Oracle Package
How to Install the HA for Oracle Package
Registering and Configuring HA for Oracle
Tools for Registering and Configuring HA for Oracle
Setting HA for Oracle Extension Properties
How to Register and Configure HA for Oracle (clsetup)
How to Register and Configure HA for Oracle Without Oracle ASM (CLI)
How to Register and Configure HA for Oracle With Clustered Oracle ASM Instance (CLI)
Verifying the HA for Oracle Installation
How to Verify the HA for Oracle Installation
Location of HA for Oracle Log Files
Tuning the HA for Oracle Fault Monitors
Operation of the Oracle Server Fault Monitor
Operation of the Main Fault Monitor
Operation of the Database Client Fault Probe
Operations to Monitor the Partition for Archived Redo Logs
Operations to Determine Whether the Database is Operational
Actions by the Server Fault Monitor in Response to a Database Transaction Failure
Scanning of Logged Alerts by the Server Fault Monitor
Operation of the Oracle Listener Fault Monitor
Obtaining Core Files for Troubleshooting DBMS Timeouts
Customizing the HA for Oracle Server Fault Monitor
Defining Custom Behavior for Errors
Changing the Response to a DBMS Error
Responding to an Error Whose Effects Are Major
Ignoring an Error Whose Effects Are Minor
Changing the Response to Logged Alerts
Changing the Maximum Number of Consecutive Timed-Out Probes
Propagating a Custom Action File to All Nodes in a Cluster
Specifying the Custom Action File That a Server Fault Monitor Should Use
How to Specify the Custom Action File That a Server Fault Monitor Should Use
A. HA for Oracle Extension Properties
B. Preset Actions for DBMS Errors and Logged Alerts
Database role failover or switchover is possible between an Oracle primary database and an Oracle standby database. When you use Oracle commands to change the role of Oracle Data Guard instances, the changes are not propagated to the Oracle Solaris Cluster resources that represent these instances. Therefore, you must also use Oracle Solaris Cluster commands to change extension properties of these resources to ensure that database instances are started in the correct role.
If a node fails while you are changing the role of an Oracle Data Guard instance, Oracle Solaris Cluster might restart the instance in an incorrect role. To prevent this possibility, change the Dataguard_role extension property of the Oracle server resource that represents the instance to IN_TRANSITION.
# clresource set -p Dataguard_role=IN_TRANSITION server-rs
Dataguard_role
Standby_mode
The required combination of Dataguard_role and Standby_mode depends on the change of role, as follows:
# clresource set -p Dataguard_role=STANDBY -p Standby_mode=PHYSICAL server-rs
# clresource set -p Dataguard_role=STANDBY \ -p Standby_mode=LOGICAL server-rs
# clresource set -p Dataguard_role=PRIMARY server-rs
# clresource set -p Standby_mode=SNAPSHOT server-rs