Oracle Grid Infrastructure

ASM and Oracle Clusterware are installed into a single home directory called the Grid Infrastructure home.

With Oracle Database 11g Release 2, Automatic Storage Management (ASM) and Oracle Clusterware are installed into a single home directory, collectively called Oracle Grid Infrastructure. This directory is referred to as the Grid Infrastructure home. Configuration assistants start after the Oracle Universal Installer interview process and binary installation that configure ASM and Oracle Clusterware. Although the installation is called Oracle Grid Infrastructure, Oracle Clusterware and Automatic Storage Manager remain separate components.

A History of Innovation

About us

Oracle 11g: RAC and Grid Infrastructure Administration Accelerated Release 2 NEW                                  Contact US

This Oracle 11g: RAC and Grid Infrastructure Administration Accelerated training teaches you about the Oracle Grid Infrastructure products, including Oracle Automatic Storage Manager (ASM), ASM Cluster File System and Oracle Clusterware. You will also learn to administer the Oracle Clusterware and storage products using both command line utilities and graphical tools using both command line and graphical user interface clients.

Objective

• Understand Oracle Clusterware architecture
• Describe how Grid Plug and Play affects Clusterware
• Describe Automatic Storage Management (ASM) architecture
• Perform Grid Infrastructure installation and create RAC database
• Demonstrate Clusterware management proficiency
• Manage application resources
• Troubleshoot Oracle Clusterware
• Administer ASM Instances and disk groups
• Administer ASM Cluster File Systems
• Install Oracle Database 11gR2 software and create RAC database
• Manage RAC databases
• Manage backup and recovery for RAC
• Determine RAC-specific tuning components
• Configure and manage services in a RAC environment
• Describe high availability architectures

From Oracle Education

          Real Application Clusters Concepts
          Troubleshooting Oracle Clusterware
          Administration of ASM
          Administering ASM Cluster File Systems
          Cloning Grid Infrastructure
          DHCP and DNS Configuration for GNS
          Administering ASM Cluster File Systems
          Administering ASM Files and Directories
          Adding  a node
          Deleting a node


          Real Application Clusters Database Installation

• Oracle RAC Background Processes

          ASM Cluster File System

• Oracle ACFS Command-line Tools for Linux and UNIX Environments
• ASMCMD Volume Management Commands
• Oracle ACFS Command-Line Tools


Administering ASM Instances


• Administration - ASM
• Starting Up an Oracle ASM Instance
• Shutting Down an Oracle ASM Instance
• Setting or Changing Initialization Parameter Values
• Oracle Automatic Storage Management 11g Release 2 (11.2.0.2) New Features
• Configuring Initialization Parameters for Oracle ASM Instances
• Setting Oracle ASM Initialization Parameters

Administering ASM Disk Groups


• Views Containing Oracle ASM Disk Group Information
• Tuning Oracle disk I/O: ASM configuration
• Preferred Read Failure Groups
• Performance and Scalability Considerations for Disk Groups
• Miscellaneous Disk Group Maintenance Enhancements
• Dropping Disk Groups
• Disk Group Attributes
• Creating Disk Groups
• Oracle ASM Disk Groups

        Administering Oracle Clusterware

• To migrate OCR to Oracle ASM using OCRCONFIG
• Restoring Voting Disks
• Assignment of IP Addresses and SCAN
• Clusterware Networking
• Adding, Deleting, or Migrating Voting Disks

        ASM Files, Directories, and Templates

• Oracle file types and Oracle ASM file type tags
• Oracle ASM file components
• Managing Disk Group Templates
• Managing ASM ACL With Command Line Utilities
• Alias Oracle ASM Filename Forms

        Monitoring and Tuning the RAC Database

• RAC and Instance or Crash Recovery
• RAC Performance Tuning Goal
• Cache Coherency
• Cache Fusion Basics

       Oracle Clusterware High Availability

• The Generic Server Pool
• Creating an Application VIP Managed by Oracle Clusterware
• CLUSTER HA Components HA
• Managing Resources in 11g RAC
• Application placement policies
• 
  

      Managing Oracle Clusterware

• Download and Install Patch Updates
• Recommended Postinstallation Tasks
• Patching Oracle RAC in Online Mode
• Adding a new Node
• 
  

     RAC Tuning and Debugging

• Index Leaf Block contention Tuning
• HW enqueue contention
• Component Level Debugging

Contact US

Oracle RAC Background Processes

Oracle RAC Background Processes

The GCS and GES processes, and the GRD collaborate to enable Cache Fusion. The Oracle RAC processes and their identifiers are as follows:

• ACMS: Atomic Controlfile to Memory Service (ACMS)

In an Oracle RAC environment, the ACMS per-instance process is an agent that contributes to ensuring a distributed SGA memory update is either globally committed on success or globally aborted if a failure occurs.

• GTX0-j: Global Transaction Process

The GTX0-j process provides transparent support for XA global transactions in an Oracle RAC environment. The database autotunes the number of these processes based on the workload of XA global transactions.

• LMON: Global Enqueue Service Monitor

The LMON process monitors global enqueues and resources across the cluster and performs global enqueue recovery operations.

• LMD: Global Enqueue Service Daemon

The LMD process manages incoming remote resource requests within each instance.

• LMS: Global Cache Service Process

The LMS process maintains records of the data file statuses and each cached block by recording information in a Global Resource Directory (GRD). TheLMS process also controls the flow of messages to remote instances and manages global data block access and transmits block images between the buffer caches of different instances. This processing is part of the Cache Fusion feature.

• LCK0: Instance Enqueue Process

The LCK0 process manages non-Cache Fusion resource requests such as library and row cache requests.

• RMSn: Oracle RAC Management Processes (RMSn)

The RMSn processes perform manageability tasks for Oracle RAC. Tasks accomplished by an RMSn process include creation of resources related to Oracle RAC when new instances are added to the clusters.

• RSMN: Remote Slave Monitor manages background slave process creation and communication on remote instances. These background slave processes perform tasks on behalf of a coordinating process running in another instance.

Oracle ACFS Command-line Tools for Linux and UNIX Environments

Oracle ACFS Command-line Tools for Linux and UNIX Environments

Summary of Oracle ACFS commands for Linux and UNIX

Command	Description
fsck	Checks and repairs an Oracle ACFS file system.
mkfs	Creates an Oracle ACFS file system.
mount	Mounts an Oracle ACFS file system.
umount	Dismounts an Oracle ACFS file system.

fsck

Purpose

Checks and repairs an Oracle ACFS file system.

Syntax and Description

fsck -t acfs -h /dev/null
fsck [-a|-f] [-v] [-vv] -t acfs [-n|-y] volume_device

fsck -t acfs -h dev/null displays usage text and exits.

Table contains the options available with the fsck command.

Options for the Linux fsck command

Option	Description
-a	Specifies to automatically repair the file system.
-f	Forces the file system into mountable state without completing a file system check or repair.
-v	Specifies verbose mode. The progress is displayed as the operation occurs.
-vv	Specifies very verbose mode. The progress is displayed as the operation occurs.
-h	Displays the usage help text and exits.
-n	Answers no to any prompts.
-y	Answers yes to any prompts.
volume_device	Specifies the primary Oracle ADVM volume device.

Examples

The following example shows how to check and repair an Oracle ACFS file system.

# /sbin/fsck -a -v -y -t acfs /dev/asm/volume1-123

mkfs

Purpose

Creates an Oracle ACFS file system.

Syntax and Description

mkfs -t acfs -h
mkfs [-v] [-f]-t acfs [-b blocksize] [-n name ] volume_device [size]

mkfs -t acfs -h displays usage text and exits.

Table below contains the options available with the mkfs command.

Options for the Linux mkfs command

Option	Description
-t acfs	Specifies the type of file system on Linux. acfs designates the Oracle ACFS type.
-v	Specifies verbose mode. The progress is displayed as the operation occurs.
-n name	Specifies the name for the file system. A name can be a maximum of 64 characters. acfsutil info fsreturns the name if one was specified.
-f	Specifies the force option. This action creates the file system even if there is an existing Oracle ACFS on the volume device, although only if the file system is dismounted. This option overwrites structures on the original file system. Use this option with caution.
-h	Displays the usage help text and exits.
-b blocksize	The default block size is 4K and this is the only size supported in 11g Release 2 (11.2).
size	Specifies the size that the file system should consume on the named device. The quantity specified can be in units of K (kilobytes), M (megabytes), G (gigabytes), T (terabytes), or P (petabytes). If a unit is not specified, the default is bytes. If the size specified is not a multiple of the block size, then the value is rounded up to the closest multiple. If this option is not specified, the entire device is consumed.
volume_device	Specifies an Oracle ADVM device file that is to be formatted.

Examples

Before creating an Oracle ACFS file system, first determine which Oracle ADVM volume devices are available. You can use the ASMCMD volinfo command to display information about the volumes and volume devices.

ASMCMD [+] > volinfo -a

...

         Volume Name: VOLUME1

         Volume Device: /dev/asm/volume1-123

         State: ENABLED

... 

Next create an Oracle ACFS file system on the volume device file.

$ /sbin/mkfs -t acfs /dev/asm/volume1-123

mount

Purpose

Mounts an Oracle ACFS file system.

Syntax and Description

mount -h
mount [-v] -t acfs [-o options] volume_device mount_point
mount

mount -h displays usage text and exits.

Options for the Linux mount command

Option	Description
-h	Displays the usage help text and exits.
-t acfs	Specifies the type of file system on Linux. acfs designates the Oracle ACFS type.
-v	Specifies verbose mode. The progress is displayed as the operation occurs.
-o	Options are specified with the -o flag followed by a comma-delimited string of options. The following options are available: all Reads the Oracle ACFS mount registry created with the acfsutil registry command and mounts the file systems in it. A mount -t acfs -o all command is automatically run at Oracle ACFS startup. When the -o all option is specified, other -o options are ignored. To specify mount options for a registry entry, include those options with the acfsutil registry command when you add the entry to the registry. ro Mounts the file system in read-only mode. norootsuid Fails the execution of binaries by non-root users whose permissions allow set user Id execution, and are owned by root. An attempt to run these executables as a non-root user fails with a permission denied error. rootsuid Allows the execution of binaries by non-root users of set user Id files owned by root. This is the default action.
volume_device	Specifies an Oracle ADVM volume device file that has been formatted by mkfs. device is required but can be a dummy value.
mount_point	Specifies the directory where the file system is mounted. This directory must exist before you run the mountcommand.

Examples

The first example shows how to mount volume1-123 on the mount point /u01/app/acfsmounts/myacfs. The second example shows how to mount all the registered Oracle ACFS file systems. The dummy names (none) have been entered for the device and directory as they are required, but not used, when theall option is specified.

# /bin/mount -t acfs /dev/asm/volume1-123 /u01/app/acfsmounts/myacfs

# /bin/mount -t acfs -o all none none

umount

Purpose

Dismounts an Oracle ACFS file system.

# /bin/umount /dev/asm/volume1-123

# /bin/umount /u01/app/acfsmounts/myacfs