Sponsored Content
Top Forums UNIX for Advanced & Expert Users Oracle RAC Cluster on RedHat Linux, Node eviction Post 302449272 by mardaff on Monday 30th of August 2010 02:21:16 AM
Old 08-30-2010
Quote:
Originally Posted by ygemici
this seem network problem on host2 through other nodes..check host2 network settings , network cables and private cluster network or host2 rac settings..
If this one doesn't fix your problem... then please reply with the info I asked. I've faced the same problem a few months ago and now is .....gone.


Quote:
Originally Posted by mardaff
Hi,

Can you please mention the version of the Oracle RAC, the patchset,the number of nodes and the number of instances running on each node.

Marius
 

We Also Found This Discussion For You

1. UNIX and Linux Applications

Slow sftp on one node of RAC cluster

I have a three node Oracle RAC cluster on RHEL4u7. User is using sftp to move files and the process works well on 2 of the three nodes. The other remaining node takes forever. I have gone through the /etc/sysconfig/network-scripts/ifcfg files and everything seems to be configured correctly. ... (0 Replies)
Discussion started by: blkav07
0 Replies
ICECREAM 
DAEMON(1) Icecream User's Manual ICECREAM DAEMON(1) NAME
iceccd - Icecream daemon SYNOPSIS
iceccd [-n netname] [-m max_processes] [--no-remote] [-w] [-d | --daemonize] [-l logfile] [-s schedulerhost] [-v [v [v]]] [-r | --run-as-user] [-b env-basedir] [-u | --nobody-uid nobodyuid] [--cache-limit MB] [-N hostname] DESCRIPTION
The Icecream daemon has to run on all nodes being part of the Icecream compile cluster. It receives compile jobs and executes them in a ch- root environment. The compile clients send their compile environment the first time they send a job to a particular daemon, so that the en- vironment of the daemon doesn't have to match the one of the client. The daemon also has to run on clients sending compile jobs to the Icecream network. If a node should be able to send compile jobs, but nev- er receive any, start the daemon with the option -m 0. All Icecream daemons need to have contact to the Icecream scheduler which controls the distribution of data between compile nodes. Normally the daemon will automatically find the right scheduler. If this is not the case you can explicitly specify the name of the Icecream network and the host running the scheduler. OPTIONS
-n netname The name of the icecream network the daemon should connect to. There has to be a scheduler running for the network under the same network name. -m max_processes Maximum number of compile jobs started in parallel on machine running the daemon. --no-remote Prevents jobs from other nodes being scheduled on this one. -w -d, --daemonize Detach daemon from shell. -l logfile Name of file where log output is written to. -s scheduler_host Name of host running the scheduler for the network the daemon should connect to. This option might help if the scheduler can't broadcast its presence to the clients due to firewall settings or similar reasons. -v, -vv, -vvv Control verbosity of daemon. The more v the more verbose. -r, --run-as-user Force running the daemon with user rights. Usually you will need to run the daemon with root rights. -b env_basedir Base directory for storing compile environments sent to the daemon by the compile clients. -u, --nobody-uid nobodyuid Id of user nobody. This user id is used when the daemon is dropping privileges. --cache-limit MB Maximum size in Mega Bytes of cache used to store compile environments of compile clients. -N hostname The name of the icecream host on the network. SEE ALSO
icecream, scheduler, iceccd, icemon AUTHOR
Cornelius Schumacher Icecream April 21th, 2005 ICECREAM DAEMON(1)
All times are GMT -4. The time now is 01:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy