JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle Solaris Cluster Data Service for Oracle Guide
search filter icon
search icon

Document Information

Preface

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 Requirements

Configuration Planning Questions

Preparing the Nodes and Disks

How to Prepare the Nodes

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 Install the Oracle ASM Software

How to Verify 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

Creating an Oracle Database

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 by Using the clsetup Utility

How to Register and Configure HA for Oracle Without Oracle ASM Using Oracle Solaris Cluster Maintenance Commands

How to Register and Configure HA for Oracle with Single Instance Oracle ASM Using Oracle Solaris Cluster Maintenance Commands

How to Register and Configure HA for Oracle with Clustered Oracle ASM Instance Using Oracle Solaris Cluster Maintenance Commands

Where to Go From Here

Verifying the HA for Oracle Installation

How to Verify the HA for Oracle Installation

Oracle Clients

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

Custom Action File Format

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

C.  Sample Configurations for Oracle ASM with HA for Oracle

Index

How to Verify the Oracle ASM Software Installation

After installing Oracle ASM software, you can verify that Oracle ASM software is installed and Oracle ASM disk group is mounted on a cluster node by performing the following steps.

# sqlplus "/ as sysdba"
sql>    select * from v$sga;
sql>    select name,state from v$asm_diskgroup;
sql>    exit;
#

Note - If you are using Oracle database 11g, you should use sqlplus "/ as sysasm" instead of sqlplus "/ as sysdba".