Skip Navigation Links | |
Exit Print View | |
Oracle Solaris Cluster Data Service for Oracle Guide Oracle Solaris Cluster |
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 Veritas 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 Database Software
How to Install the Oracle Database Software
How to Set the Oracle Database Kernel Parameters
Verifying the Oracle Database Installation and Configuration
How to Verify the Oracle Database 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 Packages
How to Install the HA for Oracle Packages
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 Grid Infrastructure (CLI)
How to Register and Configure HA for Oracle With Oracle Grid Infrastructure for a Cluster (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
Upgrading HA for Oracle Resource Types
Upgrading the SUNW.oracle_listener Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
Upgrading the SUNW.oracle_server Resource Type
Information for Registering the New Resource Type Version
Information for Migrating Existing Instances of the Resource Type
Changing the Role of an Oracle Data Guard Instance
How to Change the Role of an Oracle Data Guard Instance
A. HA for Oracle Extension Properties
B. Preset Actions for DBMS Errors and Logged Alerts
The existing resource types for the HA for Oracle data service are as follows:
SUNW.oracle_listener, which represents an Oracle listener
SUNW.oracle_server, which represents an Oracle server
Note - For Oracle Database version 11g release 2 or 12c, if you are using an Oracle Grid Infrastructure for Clusters Single Client Access Name (SCAN) listener, the SUNW.oracle_listener resource type is not used.
In addition to the existing resource types, there are three additional resource types included in HA for Oracle data service for Oracle ASM. These resource types are as follows:
SUNW.asm_diskgroup (Oracle 10g and 11g release 1 only) or SUNW.scalable_asm_diskgroup_proxy (Oracle 11g release 2 or 12c only), which represents the single or clustered instance Oracle ASM disk group in an Oracle Solaris Cluster configuration. For more information about the resource type, see asm_diskgroup(5) or SUNW.scalable_asm_diskgroup_proxy(5).
SUNW.scalable_asm_instance, which represents the single instance Oracle ASM in an Oracle Solaris Cluster configuration. For more information about the resource type, see SUNW.scalable_asm_instance(5).
Note - Single instance Oracle ASM is not supported with Oracle 11g release 2 or 12c. For these releases, you must only use clustered Oracle ASM.
SUNW.scalable_asm_instance_proxy, which represents a proxy for the clustered Oracle ASM instance in an Oracle Solaris Cluster configuration. For more information about the resource type, see SUNW.scalable_asm_instance_proxy(5).
Upgrade the existing resource types if you are upgrading from an earlier version of HA for Oracle.
For general instructions that explain how to upgrade a resource type, see Upgrading a Resource Type in Oracle Solaris Cluster Data Services Planning and Administration Guide.
The information that you require to complete the upgrade of the SUNW.oracle_listener resource type is provided in the subsections that follow.
To determine the version of the resource type that is currently registered, use one command from the following list:
clresourcetype list
clresourcetype show
The resource type registration (RTR) file for this resource type is /SUNW.oracle_listener.
To determine the version of the latest installed version of the /opt/cluster/lib/rgm/rtreg/SUNW.oracle_listener resource type, whether it is registered or not, use the following command:
# grep -i RT_VERSION /opt/cluster/lib/rgm/rtreg/SUNW.oracle_listener
If the version of the latest installed resource type is later than the registered version, migrate to the newer version to ensure full functionality.
Note - In the global zone, Oracle Solaris Cluster Manager or the Resource Group option of clsetup locates for you the available resource type versions you can upgrade to.
The information that you require to edit each instance of the SUNW.oracle_listener resource type is as follows:
You can perform the migration at any time.
If you need to specify the timeout value in seconds that the fault monitor uses to probe an Oracle listener, set the Probe_timeout extension property. For more information, see SUNW.oracle_listener Extension Properties.
The following example shows a command for editing an instance of the SUNW.oracle_listener resource type.
Example 1-8 Editing an Instance of the SUNW.oracle_listener Resource Type
# clresource set -p Type_version=N \ -p probe_timeout=60 oracle-lrs
This command edits a SUNW.oracle_listener resource as follows:
The SUNW.oracle_listener resource is named oracle-lrs.
The Type_version property of this resource is set to N, which represents the version number of the resource type you migrated to.
The timeout value in seconds that the fault monitor uses to probe an Oracle listener is set to 60 seconds.
The information that you require to complete the upgrade of the SUNW.oracle_server resource type is provided in the subsections that follow.
To determine the version of the resource type that is registered, use one command from the following list:
clresourcetype list
clresourcetype show
The resource type registration (RTR) file for this resource type is /opt/SUNWscor/oracle_server/etc/SUNW.oracle_server.
To determine the version of the latest installed version of the SUNW.oracle_server resource type, whether it is registered or not, use the following command:
# grep -i RT_VERSION /opt/cluster/lib/rgm/rtreg/SUNW.oracle_server
If the version of the latest installed resource type is later than the registered version, migrate to the newer version to ensure full functionality.
Note - In the global zone, Oracle Solaris Cluster Manager or the Resource Group option of clsetup locates for you the available resource type versions you can upgrade to.
The information that you require to edit each instance of the SUNW.oracle_server resource type is as follows:
You can perform the migration at any time.
If you customized the behavior of the server fault monitor, set the Custom_action_file extension property. For more information, see Customizing the HA for Oracle Server Fault Monitor.
The following example shows a command for editing an instance of the SUNW.oracle_server resource type.
Example 1-9 Editing an Instance of the SUNW.oracle_server Resource Type
# clresource set -p Type_version=N \ -p custom_action_file=/opt/SUNWscor/oracle_server/etc/srv_mon_cust_actions \ oracle-srs
This command edits a SUNW.oracle_server resource as follows:
The SUNW.oracle_server resource is named oracle-srs.
The Type_version property of this resource is set to N, which represents the version number of the resource type you migrated to.
Custom behavior for the fault monitor of this resource is specified in the file /opt/SUNWscor/oracle_server/etc/srv_mon_cust_actions.