topic Re: Oracle RAC On SLES 10 in Operating System - Linux

Oracle RAC On SLES 10

Kapil Jha — Thu, 17 Dec 2009 12:01:15 GMT

Hi Gurus,

I am stuck in RAC installtion on SUSE 9.
it has 2 nodes and the node on which I am mounting ocfs2 filesystem it has
Checking heartbeat: Active
and other has

Checking heartbeat: Not active

when I am mounting the file system on second node it says

mount.ocfs2: Transport endpoint is not connected while mounting /dev/sdb1 on /oravl06_RAC

the only issue I could spot is port 7777 is closed on one server and open on other.

My question---
is this really related to port setting or something else.

How to open a port in SUSE?
whats should be the entry in services file for this port

7777/tcp open XXXX

BR,
Kapil+

Re: Oracle RAC On SLES 10

Ivan Ferreira — Thu, 17 Dec 2009 12:14:19 GMT

A TCP port is open when a service is started. For OCFS2 you need to ensure that the o2cb service starts correctly. Maybe you are having a problem with the cluster interconnect, that is, the private network interface between the hosts.

You could check with:

/etc/init.d/o2cb status

All information you need is in:

/usr/share/doc/ocfs2-tools-*/README.O2CB

Maybe the path is different for documentation in SUSE.

Re: Oracle RAC On SLES 10

Kapil Jha — Thu, 17 Dec 2009 12:20:58 GMT

Hey Ivan,

everything seems to be fine in status, except heartbeat

# /etc/init.d/o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking cluster ocfs2: Online
Checking heartbeat: Not active

on the server where ocfs2 is not mounted.

I am not sure if its like this is this should be Active on both nodes.
I also feel somep problem with interconnect but could not figure out whatexactly is the scene.

BR,
Kapil

Re: Oracle RAC On SLES 10

Ivan Ferreira — Thu, 17 Dec 2009 12:34:07 GMT

Yes. It has to be active on both nodes:

Example:

node1>
Checking O2CB cluster sfx: Online
Heartbeat dead threshold: 31
Network idle timeout: 30000
Network keepalive delay: 2000
Network reconnect delay: 2000
Checking O2CB heartbeat: Active

node2>
Checking O2CB cluster sfx: Online
Heartbeat dead threshold: 31
Network idle timeout: 30000
Network keepalive delay: 2000
Network reconnect delay: 2000
Checking O2CB heartbeat: Active

Check your ocfs2/cluster.conf and identify the ip_address configuration on both nodes.

Ensure that you can ping that ip address from each one.

Use the ethtool command to identify if your private adapters have link.

Re: Oracle RAC On SLES 10

Kapil Jha — Fri, 18 Dec 2009 04:46:23 GMT

All the links are UP I can ping from oe server to other.

The only issue I can feel is of port cause in one server port 7777 is open on other its closed.

What are the entries should be there in /etc/services file.

BR,
Kapil+

Re: Oracle RAC On SLES 10

Ivan Ferreira — Fri, 18 Dec 2009 12:00:35 GMT

I have no entries on /etc/services and everyhing is working correctly.

Any firewall running?

Re: Oracle RAC On SLES 10

Ivan Ferreira — Fri, 18 Dec 2009 12:35:00 GMT

And also post the output of:

grep -i o2cb /var/log/messages*

On both nodes.

Re: Oracle RAC On SLES 10

Viktor Balogh — Fri, 18 Dec 2009 13:42:30 GMT

# /etc/init.d/o2cb status
Module "configfs": Loaded
Filesystem "configfs": Mounted
Module "ocfs2_nodemanager": Loaded
Module "ocfs2_dlm": Loaded
Module "ocfs2_dlmfs": Loaded
Filesystem "ocfs2_dlmfs": Mounted
Checking cluster ocfs2: Online
Checking heartbeat: Not active

I would take a look into that init script and see what this "Checking heartbeat" does. My best bet is that it checks the port 7777, but I'm not sure as I don't know RAC environment in SuSE very well.

Re: Oracle RAC On SLES 10

Ivan Ferreira — Fri, 18 Dec 2009 14:34:46 GMT

I was digging a little more and the heartbeat is active when the OCFS2 filesystem is mounted.

That means that is inactive because you cannot mount the ocfs2 filesystem. We must find the reason of this.

Try with egrep "e2|ocfs2" /var/log/messages*

I have seen a problem similar searching and it was caused by different versions of ocfs2 installed on the nodes. Check the versions on both nodes with rpm -qa | grep ocfs