Hooray, found the reason of cluster failure. It was oracle db user issue. Oracle DB server resource timed out due to Oracle DB locked user.
So we solved a problem via below order.
- Unlocked oracle db user which is used to connect Sun Cluster Oracle Resource to Ora DB.
- Took the resource group offline.
- Disabled oracle db resources and application resources.
- Brought resource group online on active node.
- Started oracle db manually.
- About 10 mins, enabled oracle db resources and application resources.
Hi Gurus
I am not able to find the patching procedure for solaris 10 ( sol10 u11) to latest patchset with sun cluster having failover zones so that same I should follow.
Take an instance, there are sol1 and sol2 nodes and having two failover zones like sozone1-rg and sozone2-rg and currently... (1 Reply)
Hi,
I am using Power HA7.1.1 SP5 AIx 7.1
My both cluster nodes are independently working. RG informations are not updating each other. Node A shows that node B is down and vice versa.
RG1 is running node A, RG2 running on node B.
=== clRGinfo From Node B ===
RG01 OFFLINE ... (2 Replies)
Hi Guys,
I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me.
How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Hello everyone,
I have two Solaris 10 servers that are on cluster. The cluster is a Sun Cluster 3.2
I have a script cronned that stop/start a ressource in a resource group everyday.
Today I have checked the status of the ressources and I found that my ressource group have a "Error--stop... (1 Reply)
I have installed sun cluster 3.2 on two sprac servers. Configured a failover resource group. Added a LogicalHostname resource to it. LogicalHostname is also added to /etc/hosts with ip address.
I am able to access cluster by share ip used for logical hostname but when i try to switch the resource... (0 Replies)
I am using VMware Workstation-7 on Windows-XP host .
I am trying to configure Solaris 10-X86 guest os based 2 nodes Sun Cluster .
I have added one extra Virtual Lan adapter on my VMware with another subnet (that I would like to put for SUN Cluster private communication).
I have... (0 Replies)
Hello,
As explained, I've encountered an issue while installing Solaris 10 SPARC Recommended Patch Cluster (2009.10.23).
Actually, patch no 120011-14 stops with the following error:
ERROR: attribute verification of </var/run/.patchSafeMode/root/usr/bin/passwd> failed
file type <f>... (6 Replies)
PACEMAKER(8) System Administration Utilities PACEMAKER(8)NAME
Pacemaker - Part of the Pacemaker cluster resource manager
SYNOPSIS
crm_node command [options]
DESCRIPTION
crm_node - Tool for displaying low-level node information
OPTIONS
-?, --help
This text
-$, --version
Version information
-V, --verbose
Increase debug output
-Q, --quiet
Essential output only
Stack:
-A, --openais
Only try connecting to an OpenAIS-based cluster
-H, --heartbeat
Only try connecting to a Heartbeat-based cluster
Commands:
-n, --name
Display the name used by the cluster for this node
-N, --name-for-id=value
Display the name used by the cluster for the node with the specified id
-e, --epoch
Display the epoch during which this node joined the cluster
-q, --quorum
Display a 1 if our partition has quorum, 0 if not
-l, --list
Display all known members (past and present) of this cluster (Not available for heartbeat clusters)
-p, --partition
Display the members of this partition
-i, --cluster-id
Display this node's cluster id
-R, --remove=value
(Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches
In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster
Additional Options:
-f, --force
AUTHOR
Written by Andrew Beekhof
REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org
Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)