Login or Register to Ask a Question and Join Our Community


UNIX and Linux Applications

Oracle Cluster Ready Services waiting for SunCluster on x86 to start

Login to Discuss or Reply to this Discussion in Our Community

 
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

LEARN ABOUT DEBIAN

4s-backend-setup

4S-BACKEND_SETUP(1J)						      4store						      4S-BACKEND_SETUP(1J)

NAME

     4s-backend-setup -- Create a new 4store KB

SYNOPSIS

     4s-backend-setup kbname [--node node-number] [--cluster cluster-size] [--segments segment-count] kb-name

		      --node  Number of this node in the cluster, values range from 0 to cluster-size - 1.  The default is 0.

		      --cluster
			      The number of nodes in the cluster.  The default is 1.

		      --segments
			      The number of segments in the cluster. The default is 2. We recommend one for each CPU core in the cluster as a good
			      starting point. Higher numbers tend to consume more resources, but may result in increased performance.

NOTES

     Once crated with 4s-backend-setup KBs should be started with 4s-backend(1)

SEE ALSO

     4s-query(1), 4s-size(1), 4s-httpd(1), 4s-backend(1), 4s-delete-model(1)

EXAMPLES

     $ 4s-backend-setup --node 0 --cluster 1 --segments 4 demo

     Creates the indexes for a single-machine KB with four segments, named "demo".

4store								   May 31, 2019 							    4store