Skip to main content

Oracle RAC does not start

HACMP started


Before starting Oracle9i RAC instances, the HACMP cluster must be up and running. Check the cluster state with the /usr/sbin/cluster/clstat command.

Hagsuser group


These tests must be performed on all nodes:

Check that the Oracle user is part of the hagsuser group. The name of this group is mandatory, and cannot be changed.

Check, and change if necessary, the permissions on the cldomain executable. This program must be executable by everybody (user, group, other):

# chmod a+x /usr/es/sbin/cluster/utilities/cldomain

Check, and change the group to hagsuser if necessary, for the svcsdsocket.oracle9irac socket file: (assuming that oracle9irac is the name of your cluster, returned by the cldomain command):

{node2:root}/-> chgrp hagsuser /var/ha/soc/grpsvcsdsocket.oracle9irac

Check, and change if necessary, the group permissions for the grpsvcsdsocket.oracle9irac socket:

{node2:root}/-> chmod g+w /var/ha/soc/grpsvcsdsocket.oracle9irac

The HAGS socket file needs to be writable by the Oracle user and the cldomain executable needs to be executable by Oracle. By configuring the group and permissions for the grpsvcsdsocket.oracle9irac file, the instance will be able to communicate with HAGS and the instance will mount.

See Example 3-39 for the valid permissions and group membership for the socket files used by Oracle9i RAC.

Example 3-39 Permissions on the /var/ha/soc directory

{node2:root}/var/ha/soc-> ls -ltotal 0
srw-rw-rw- 1 root haemrm 0 Jun 10 18:18 em.clsrv.oracle9irac
srw-rw---- 1 root haemrm 0 Jun 10 18:18 em.rmsrv.oracle9irac
drwxrwxrwx 2 root system 256 Jun 11 19:20 grpsvcs.clients.oracle9i
racsrw-rw-rw- 1 root hagsuser 0 Jun 10 18:18 grpsvcsdsocket.oracle9i
racdrwxrwx--- 2 root haemrm 256 Jun 10 18:18 haem
drwxr-xr-x 2 root system 256 May 13 17:54 hats
drwxr-xr-x 2 root system 256 Jun 10 18:18 topsvcs

UDP tuning


The udp_sendspace value must always be greater than Oracle9i RAC's db_block_size. Otherwise Oracle9i RAC will not start.

GPFS issues


GPFS requires a quorum of nodes to run. It also requires that both nodes holding the GPFS configuration data be up and running for any configuration changes to be performed.

In case of a system restart, GPFS will be started automatically and the GPFS file systems will be mounted.


To shut down and unmount the GPFS file systems on all nodes, issue:

# mmshutdown -a



To start GPFS and mount the GPFS file systems on all nodes, issue:



# mmstartup -a

Comments

Post a Comment

Popular posts from this blog

Typical Oracle RAC configurations

All configurations are based on the following building blocks: Hardware Server nodes Storage Networking Software Operating system Cluster software Oracle RAC (application) Application architecture Oracle9i RAC on RAW devices is based on a shared disk architecture. Figure 2-1 shows a two-node cluster. The lower solid line is the primary Oracle interconnect, the middle dashed line is the secondary Oracle interconnect. For high availability, both these networks should be defined in the HACMP as "private". HACMP/ESCRM provides Oracle9i RAC with the infrastructure for concurrent access to disks. Although HACMP provides concurrent access and a disk locking mechanism, this mechanism is not used. Oracle, instead, provides its own locking mechanism for concurrent data access, integrity, and consistency. Volume groups are varied on all the nodes, thus ensuring short failover time. This type of concurrent access can only be provided for RAW ...
Post a Comment
Read more

How to configure multipath Debian CentOS for IBM Storage

This detailed how to guides to achieve high availability and performance on Debian and CentOS for accessing storage space at IBM DS8300 Data Storage Systems. Tested on Debian GNU/Linux 5.x Lenny 64 bits and CentOS 5.3 64 bits running on 8 cores blades, with Host Bus Adapters Qlogic and Emulex Light Pulse Fiber Channel in deployed systems at SERPRO . Observations showed that Debian Lenny has the best performance, for our app load profile and hardware. Also, there are listed a number of previously not clearly documented critical pitfalls to avoid. STUDY whole articles, hints, implications, and cited resources before planning your deployment. Every detail matters . Before start, you must have LUNs at IBM DS8300 storage configured for high availability and performance as explained at the article How to configure maximum performance storage space for Debian GNU/Linux on IBM DS 8300 Data Storage Systems . Multipath and storage basic concepts In order t...
Post a Comment
Read more

IBM SAN Multipath installation on Red Hat Enterprise Linux 5.X

This section describes the steps for installing Red Hat Enterprise Linux 5.2 on a multipath device. 1.Determine which multipath device your machine boots from. To do this, note down the LUN (Logical Unit) number of the bootable device that is made available by your Fibre Channel Adapter card during firmware boot. In the test environment, the firmware displays the boot disk, showing lun number 0.                           2.Start the installation by providing the keyword mpath in the kernel command line. In the test environment, linux mpath vnc was used. The Partitioning screen displays a list of multipath devices as mapper/mpath*. 3. Determine the multipath device that corresponds to the bootable device for the host being installed. Go back to the console window if using VNC, or start an alternate console. In the test environment, the System x® is hooked up to an RSA. In the remote control console,...
Post a Comment
Read more