Solaris cluster critical issue


 
Thread Tools Search this Thread
Operating Systems Solaris Solaris cluster critical issue
# 8  
Old 03-31-2015
Problem solved

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.

After that, everything works fine.
Login or Register to Ask a Question

Previous Thread | Next Thread

8 More Discussions You Might Find Interesting

1. Solaris

Patching Procedure in Solaris 10 with sun cluster having Solaris zone

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)
Discussion started by: nick101
1 Replies

2. AIX

Cluster communication issue

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)
Discussion started by: sunnybee
2 Replies

3. Red Hat

Linux Cluster failover issue

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)
Discussion started by: munna529
2 Replies

4. Solaris

Sun Cluster 3.2 Issue

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)
Discussion started by: adilyos
1 Replies

5. Solaris

Sun Cluster switching issue

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)
Discussion started by: ahmadnauman
0 Replies

6. Solaris

Sun Cluster configuration issue

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)
Discussion started by: sanjee
0 Replies

7. Solaris

Issue while installing: Solaris 10 SPARC Recommended Patch Cluster (2009.10.23)

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)
Discussion started by: a.mauger
6 Replies

8. High Performance Computing

Building a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris

Provides a description of how to set up a Solaris Cluster Express cluster in a VirtualBox on OpenSolaris. More... (0 Replies)
Discussion started by: Linux Bot
0 Replies
Login or Register to Ask a Question
cmdeleteconf(1m)														  cmdeleteconf(1m)

NAME
cmdeleteconf - Delete either the cluster or the package configuration SYNOPSIS
cmdeleteconf [-f] [-v] [-c cluster_name] [[-p package_name]...] DESCRIPTION
cmdeleteconf deletes either the entire cluster configuration, including all its packages, or only the specified package configuration. If neither cluster_name nor package_name is specified, cmdeleteconf will delete the local cluster's configuration and all its packages. If the local node's cluster configuration is outdated, cmdeleteconf without any argument will only delete the local node's configuration. If only the package_name is specified, the configuration of package_name in the local cluster is deleted. If both cluster_name and pack- age_name are specified, the package must be configured in the cluster_name, and only the package package_name will be deleted. cmdelete- conf with only cluster_name specified will delete the entire cluster configuration on all the nodes in the cluster, regardless of the con- figuration version. The local cluster is the cluster that the node running the cmdeleteconf command belongs to. Only a superuser, whose effective user ID is zero (see id(1) and su(1)), can delete the configuration. To delete the cluster configuration, halt the cluster first. To delete a package configuration you must halt the package first, but you do not need to halt the cluster (it may remain up or be brought down). To delete the package VxVM-CVM-pkg (HP-UX only), you must first delete all packages with STORAGE_GROUP defined. While deleting the cluster, if any of the cluster nodes are powered down, the user can choose to continue deleting the configuration. In this case, the cluster configuration on the down node will remain in place and, therefore, be out of sync with the rest of the cluster. If the powered-down node ever comes up, the user should execute the cmdeleteconf command with no argument on that node to clean up the config- uration before doing any other Serviceguard command. Options cmdeleteconf supports the following options: -f Force the deletion of either the cluster configuration or the package configuration. -v Verbose output will be displayed. -c cluster_name Name of the cluster to delete. The cluster must be halted already, if intending to delete the cluster. -p package_name Name of an existing package to delete from the cluster. The package must be halted already. There should not be any packages in the cluster with STORAGE_GROUP defined before having a package_name of VxVM-CVM-pkg (HP-UX only). RETURN VALUE
Upon completion, cmdeleteconf returns one of the following values: 0 Successful completion. 1 Command failed. EXAMPLES
The high availability environment contains the cluster, clusterA , and a package, pkg1. To delete package pkg1 in clusterA, do the following: cmdeleteconf -f -c clusterA -p pkg1 To delete the cluster clusterA and all its packages, do the following: cmdeleteconf -f -c clusterA AUTHOR
cmdeleteconf was developed by HP. SEE ALSO
cmcheckconf(1m), cmapplyconf(1m), cmgetconf(1m), cmmakepkg(1m), cmquerycl(1m). Requires Optional Serviceguard Software cmdeleteconf(1m)