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
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
This section contains the information that you need to plan your HA for Oracleinstallation and configuration.
Note - Unless otherwise stated, instructions and information for Oracle Database 11g apply to both Oracle Database 11g release 1 and Oracle Database 11g release 2.
Caution - Your data service configuration might not be supported if you do not adhere to these requirements. |
Use the requirements in this section to plan the installation and configuration of HA for Oracle. These requirements apply to HA for Oracle only. You must meet these requirements before you proceed with your HA for Oracle installation and configuration.
You can configure HA for Oracle to run in non-global zones, with the following conditions:
You cannot configure Oracle Solaris Cluster HA for Oracle to be controlled by the HA for Solaris Containers data service.
You must use a highly available local file system.
You can also configure HA for Oracle in a zone cluster.
Caution - Raw devices from Oracle Solaris Cluster device groups are not supported in non-global zones. |
For requirements that apply to all data services, see Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide.
Oracle Database application files – These files include Oracle Database binaries, configuration files, and parameter files. You can install these files either on the local file system, the highly available local file system, or on the cluster file system.
See Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide for the advantages and disadvantages of placing the Oracle Database binaries on the local file system, highly available local file system, and the cluster file system.
Database related files– These files include the control file, redo logs, and data files. You must install these files on either raw devices or as regular files on the highly available local, ACFS 12c file system, or cluster file system. Raw devices from Oracle Solaris Cluster device groups are not supported in non-global zones.
Oracle ASM configuration – Oracle Automatic Storage Management (Oracle ASM) is a storage option that provides the services of a file system, logical volume manager, and software redundant array of independent disks (RAID) in a platform independent manner. If you are planning to install Oracle ASM, you should choose the appropriate Oracle ASM instance and disk group for your Oracle Database installation. There are two types of Oracle ASM instances, single Oracle ASM instance and clustered Oracle ASM instance. See Choosing the Appropriate Oracle ASM Instance for information on choosing the appropriate Oracle ASM instance. For more information on Oracle ASM, see the Oracle Database documentation corresponding to the Oracle Database version you are using.
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.
If the single instance Oracle Database software is installed on a node using an Oracle ASM disk group, then certain files are not included within the Oracle ASM disk group and they resided only locally. You should ensure that these files are copied to the other cluster nodes from the node where the Oracle Database single instance is created.
Starting with the Oracle Database 11g release 1 database version, you copy the following directories to other cluster nodes:
${ORACLE_BASE}/diag/rdbms/sid
${ORACLE_BASE}/admin
${ORACLE_HOME}/dbs/pfile.ora
If you are using an Oracle Database 10g database, you copy the following directories to other cluster nodes:
${ORACLE_HOME}/admin
${ORACLE_HOME}/dbs/initsid.ora
After you copy the necessary directories to the cluster nodes, ensure that the copied directories have the same user and group permissions as on the source system.
Oracle ASM with Solaris Volume Manager mirrored logical volumes – The following behavior might occur when you use Solaris Volume Manager mirrored logical volumes with Oracle ASM:
Performance degradation – Oracle ASM does not support Solaris Volume Manager Application Based Recovery (ABR). Instead, use external redundancy of Oracle ASM for Solaris Volume Manager devices. Avoid normal and high redundancy of Oracle ASM for Solaris Volume Manager devices. For additional information, see Article 603825.1 at https://support.oracle.com.
Failures of the SUNW.ScalDeviceGroup probe – Failures of this probe result in a loss of availability of any service that is dependent on the SUNW.ScalDeviceGroup resource.
You can mitigate such failures by increasing the IOTimeout property setting for the SUNW.ScalDeviceGroup resource type.
# clresource set -p IOTimeout=time-in-seconds resource-name
The default setting for the IOTimeout property is 30 seconds. Depending on your configuration, this value can be much higher and should be determined for each system individually. If you experience failures of this probe, start by setting the IOTimeout property to 240 seconds and adjust the setting further as needed.
Use the questions in this section to plan the installation and configuration of HA for Oracle. Write the answers to these questions in the space that is provided on the data service worksheets in Configuration Worksheets in Oracle Solaris Cluster Data Services Planning and Administration Guide.
What resource groups will you use for network addresses and application resources and the dependencies between them?
What is the logical hostname (for failover services) or shared address (for scalable services) for clients that will access the data service?
Where will the system configuration files reside?
See Configuration Guidelines for Oracle Solaris Cluster Data Services in Oracle Solaris Cluster Data Services Planning and Administration Guide for the advantages and disadvantages of placing the Oracle Database binaries on the local file system rather than the cluster file system.
Does your database setup require standby instances?
If you use the clsetup utility to register and configure HA for Oracle, some of these questions are answered automatically by the utility.
For information about standby databases, see your Oracle Database documentation.
Are you planning to use Oracle ASM storage?
If you are planning to use Oracle ASM storage, you should decide if you require single instance or clustered instance Oracle ASM. See Choosing the Appropriate Oracle ASM Instance for information on how to choose the appropriate Oracle ASM instance.
For information about standby databases, see your Oracle Database documentation.