Oracle Cluster Ready Services waiting for SunCluster on x86 to start

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Oracle Cluster Ready Services waiting for SunCluster on x86 to start
# 1  
Old 05-19-2009
Oracle Cluster Ready Services waiting for SunCluster on x86 to start

Recently i faced problem starting oracle application on my galaxy cluster on one node.In the log i found that the CRS demon was not started after the booting of the node , so i manually tried to start it but faced some error.

So here are the work around that i had done and the CRS services got started .

The error i was getting while starting oracle is
======================
PRKC-1056 : Failed to get the hostname for node galclus157
PRKH-1010 : Unable to communicate with CRS services.
[Communications Error(Native: prsr_initCLSS:[3])]
======================

When i tried to start the crsd manually the service did not started .

Then after debugging this error i found that the crs service depends on the ucmmd service to start .

So please check if this is already running or not (If not start it)
===================================
root@syscl055 # ps -aef | grep ucmmd
root 2030 1 0 May 12 ? 13:12 ucmmd -r /usr/cluster/lib/ucmm/ucmm_reconf
===================================
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Script to Start services based on dependent services on other AIX machine

Hi, I just started working on a script. After my research, i found a command which can help me: AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2. So my script has to... (4 Replies)
Discussion started by: draghun9
4 Replies

2. AIX

Thoughts on HACMP: Automatic start of cluster services

Hi all, I remember way back in some old environment, having the HA cluster services not being started automatically at startup, ie. no entry in /etc/inittab. I remember reason was (taken a 2 node active/passive cluster), to avoid having a backup node being booted, so that it will not... (4 Replies)
Discussion started by: zaxxon
4 Replies

3. UNIX for Dummies Questions & Answers

DDD is waiting for GDB to get Ready

Hello, I'm attempting to use the DDD program. After launching it from the shell I try to set a breakpoint on a source code file and when I click run it hangs and says Waiting until GDB gets ready. I cannot do anything inside the program except quit (and even that takes a while). Can someone tell... (3 Replies)
Discussion started by: lamentofking
3 Replies

4. Solaris

Sun Cluster 3.2 x86: Node is rebooting itself

Hey Admins, I am running sun cluster 3.2 x86 on Vmware. I m facing an issue from 2 days.. One main node is continuously rebooting..... not sure... whats woring... I just had change heartbeat timeout values on 1 this node... Now both node are just rebooting itself..seems panic.. Any... (1 Reply)
Discussion started by: snchaudhari2
1 Replies

5. Solaris

suncluster co-existing with Veritas Cluster

have a pair of sun servers, wanting to test drive a 2-node cluster using both software.. would like disable one of these cluster software while the othe is running.. Is it feasible at all ?? (2 Replies)
Discussion started by: ppchu99
2 Replies

6. High Performance Computing

Veritas Cluster for Solaris x86?

Hi, Anybody know where I can download Veritas Cluster 5.0 for Solaris x86? Thanks (2 Replies)
Discussion started by: gwhelan
2 Replies
Login or Register to Ask a Question
VOTEQUORUM_LEAVING(3)				    Corosync Cluster Engine Programmer's Manual 			     VOTEQUORUM_LEAVING(3)

NAME
votequorum_leaving - Tell other nodes that we are leaving the cluster SYNOPSIS
#include <corosync/votequorum.h> int votequorum_leaving(votequorum_handle_t handle); DESCRIPTION
The votequorum_leaving function is used to tell the other nodes in the cluster that this node is leaving. They will (when the node actually leaves) reduce quorum to keep the cluster running without this node. This function should only be called if it is known that the node is being shut down for a known reason and could be out of the cluster for an extended period of time. Normal behaviour is for the cluster to reduce the total number of votes, but NOT expected_votes when a node leave the cluster, so the clus- ter could become inquorate. This is correct behaviour and is ther eto prevent split-brain. Do NOT call this function unless you know what you are doing. RETURN VALUE
This call returns the CS_OK value if successful, otherwise an error is returned. ERRORS
The errors are undocumented. SEE ALSO
votequorum_overview(8), votequorum_initialize(3), votequorum_finalize(3), votequorum_dispatch(3), votequorum_fd_get(3), corosync Man Page 2009-01-26 VOTEQUORUM_LEAVING(3)