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)
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
Perform the following verification tests to make sure that you have correctly installed HA for Oracle.
These sanity checks ensure that all the nodes or zones that run HA for Oracle can start the Oracle Database instance and that the other nodes or zones in the configuration can access the Oracle Database instance. Perform these sanity checks to isolate any problems in starting the Oracle Database software from HA for Oracle.
Use the sqlplus command with the user/password variable that is defined in the connect_string property.
# sqlplus user/passwd@tns_service
Specifies the network name service provided by the $ORACLE_HOME/network/admin/tnsnames.ora file or the value of the TNS_ADMIN environment variable.
The Oracle Solaris Cluster software restarts the Oracle instance because the Oracle instance is under Oracle Solaris Cluster control.
# clresourcegroup switch -n node-zone-list resource-group
Specifies a comma-separated, ordered list of zones that can master this resource group. The format of each entry in the list is node:zone. In this format, node specifies the name or ID of a node and zone specifies the name of a non-global Solaris zone. To specify the global zone, or to specify a node without non-global zones, specify only node.
The order in this list determines the order in which the nodes or zones are considered primary during failover. This list is optional. If you omit this list, the global zone of each cluster node can master the resource group.
Specifies the name of the resource group that you are switching.
Clients must always refer to the database by using the network resource, not the physical hostname. The network resource is an IP address that can move between physical nodes during failover. The physical hostname is a machine name.
For example, in the tnsnames.ora file, you must specify the network resource as the host on which the database instance is running. The network resource is a logical hostname or a shared address. See How to Set Up Oracle Database Permissions.
Note - Oracle client-server connections cannot survive a HA for Oracle switchover. The client application must be prepared to handle disconnection and reconnection or recovery as appropriate. A transaction monitor might simplify the application. Further, HA for Oracle node recovery time is application dependent.
Each instance of the HA for Oracle data service maintains log files in subdirectories of the /var/opt/SUNWscor directory.
The /var/opt/SUNWscor/oracle_server directory contains log files for the Oracle server.
The /var/opt/SUNWscor/oracle_listener directory contains log files for the Oracle listener.
These files contain information about actions that the HA for Oracle data service performs. Refer to these files to obtain diagnostic information for troubleshooting your configuration or to monitor the behavior of the HA for Oracle data service.