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

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

Squid Access Lists

Access Lists There are a number of different access lists: http_access : Allows HTTP clients (browsers) to access the HTTP port. This is the primary access control list. http_reply_access : Allows HTTP clients (browsers) to receive the reply to their request. This further restricts permissions given by http_access , and is primarily intended to be used together with rep_mime_type acl for blocking different content types. icp_access : Allows neighbor caches to query your cache with ICP. miss_access : Allows certain clients to forward cache misses through your cache. This further restricts permissions given by http_access , and is primarily intended to be used for enforcing sibling relations by denying siblings from forwarding cache misses through your cache. cache : Defines responses that should not be cached. url_rewrite_access : Controls which requests are sent through the redirector pool. ident_lookup_access : Controls which requests need an Ident lookup. always_dire...
Post a Comment
Read more

ipsec tunnel pfSense and Centos

pfSense 1.2.3 -------- external ip: 1.1.1.1 internal ip: 172.20.1.20 internal network: 172.20.1.0/24 Centos 5.5 -------- external ip: 2.2.2.2 internal ip: 172.20.2.1 internal network: 172.20.2.0/24 pfSense config from a reset. Firewall rule to allow all ipsec communication (all protocols). pfSense ipsec config -------------------- Mode: Tunnel Interface: WAN (I'm not sure this should be WAN, but changing it to LAN makes no difference) Local subnet: 172.20.1.0/24 Remote subnet: 172.20.2.0/24 Remote gateway: 2.2.2.2 Phase 1 Negotiation mode: agressive My identifier: My IP adress Encryption algorithm: 3DES Hash algorithm: SHA1 DH key group: 2 Authentication method: Pre-shared key Pre-Shared Key: secret Phase 2 Protocol: ESP Encryption algorithms: Rijndael (AES) Hash algorithms: SHA1 PFS key group: 2   Centos ipsec config ------------------- /etc/sysconfig/network-scripts/ifcfg-ipsec0 TYPE=IPSEC ...
1 comment
Read more