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

Popular posts from this blog

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...

Six Linux softphone's list

VoIP has improved a lot since its first days, today a lot of multinational business are using it as a reliable way to keep stay in touch. With more and more telecommuters, and business man working, and with cell phone roaming costs still high, VoIP is a real option for both big and small corporations. And when you talk to a CFO about investing to save costs, you usually will see the checkered flag for your project. Most of these projects will involve IP phones or ATAs, but you may use softphones too, which are very convenient for the traveler guy, here we will review some of the soft phones available for Linux. Linphone Linphone is a mature piece of software, it uses SIP, for voice and video over IP, it can work as a stand alone application, and you can call other sip enabled devices just entering its ips on the dial window of Linphone, or you can configure it to use an Asterisk PBX. There are binary packages for the most common distros, so try to install it using you pa...

Configuring the virtual path devices

We recommend that you start with a "fresh" disk configuration, so it is a good idea to delete all previously configured FC adapters and their child (disk) devices. On node1, we checked which disks are still defined: {node1:root}/-> lspvhdisk0 0022be2ab1cd11ac rootvg activehdisk1 0022be2a3d02ead0 Nonehdisk2 0022be2a4cbbafd8 Nonehdisk3 none NoneThese are the internal SCSI disk drives {node1:root}/-> lscfg grep disk+ hdisk3 U1.9-P2/Z2-A8 16 Bit LVD SCSI Disk Drive (36400 MB)+ hdisk2 U1.9-P2/Z1-A8 16 Bit LVD SCSI Disk Drive (36400 MB)+ hdisk1 U1.9-P1/Z2-A8 16 Bit LVD SCSI Disk Drive (36400 MB)+ hdisk0 U1.9-P1/Z1-A8 16 Bit LVD SCSI Disk Drive (36400 MB)In order to include the ESS disks, run the configuration manager on each node: {node1:root}/-> cfgmgr -vSince ESS was configured with two host paths for each node (node1a and node1b), this results in two hdisks on the nodes. Actually, those two logical hdisks represent the same physical disk, accessed via the two ...