Sponsored Content
Operating Systems Solaris Solaris cluster critical issue Post 302939925 by sembii on Tuesday 31st of March 2015 02:11:24 AM
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.
 

8 More Discussions You Might Find Interesting

1. 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

2. 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

3. 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

4. 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

5. 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

6. 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

7. 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

8. 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
sctelemetry(1M) 					  System Administration Commands					   sctelemetry(1M)

NAME
sctelemetry - initialize system resource monitoring SYNOPSIS
sctelemetry -d sctelemetry -e sctelemetry -i -o hasp_rg=rg,hasp_rs=rs [,hasp_mnt_pt=mnt_pt] [,db_rg=rg] [,db_rs=rs] [,telemetry_rg=rg] [,telemetry_rs=rs] sctelemetry -i -o hasp_mnt_pt=mnt_pt,hasp_nodelist=node[:...] [,hasp_rs=rs] [,db_rg=rg] [,db_rs=rs] [,telemetry_rg=rg,telemetry_rs=rs] sctelemetry -u DESCRIPTION
Note - Beginning with the Sun Cluster 3.2 release, Sun Cluster software includes an object-oriented command set. Although Sun Cluster software still supports the original command set, Sun Cluster procedural documentation uses only the object-oriented command set. For more infor- mation about the object-oriented command set, see the Intro(1CL) man page. The sctelemetry command initializes system resource monitoring, brings monitoring online, and takes it offline. When initializing, use the -o option with the hasp_rg=rg,hasp_rs=rs parameters to rely on an existing resource of type SUNW.HAStoragePlus. Use the -o option with the hasp_mnt_pt=mnt_pt,hasp_nodelist=node[:,...]parameters to have the sctelemetry command create a resource of type SUNW.HAStoragePlus. For more information about the resource types, see the SUNW.derby(5), SUNW.HAStoragePlus(5), and SUNW.SCTelemetry(5) man pages. SUNW.SCTelemetry is instantiated in a multi-master resource group, that is the resource group is configured on all cluster nodes and does not use network load balancing. You can use this command only in the global zone. OPTIONS
The options for sctelemetry are as follows: -d Disables the collection of system resource usage data and the database in which telemetry data is stored. You can use this option only in the global zone. Users other than superuser require solaris.cluster.system.modify RBAC authorization to use the -d option of sctelemetry. For more information, see the rbac(5) man page. -e Brings collection of system resource usage data online. By default, system resource monitoring is online when you use the -i option of the sctelemetry command. You can use this option only in the global zone. Users other than superuser require solaris.cluster.system.modify RBAC authorization to use the -e option of sctelemetry. For more information, see the rbac(5) man page. -i Creates resource groups containing resources of type SUNW.SCTelemetry and SUNW.derby. By default, when you create these resources and resource groups by using the -i option, system resource monitoring is online. You can use this option only in the global zone. Users other than superuser require solaris.cluster.system.modify RBAC authorization to use the -i option of sctelemetry. For more information, see the rbac(5) man page. -o hasp_rg=rg,hasp_rs=rs[,hasp_mnt_pt=mnt_pt][,db_rg=rg][,db_rs=rs][,telemetry_rg=rg][ ,telemetry_rs=rs] When used with the -i option, identifies the resource of type SUNW.HAStoragePlus to be used by the database and the resource group that contains this resource. The data collection facility must have access to a file system for SUNW.HAStoragePlus. The parameters are as follows: hasp_rg=rg The resource group that contains the resource of type SUNW.HAStoragePlus that is used for system resource monitoring. You must specify rg, the name of this resource group. hasp_rs=rs The resource of type SUNW.HAStoragePlus that is used for system resource monitoring. You must specify rs, the name of this resource. hasp_mnt_pt=mnt_pt The mount point on which sctelemetry stores database files for system resource monitoring. This mount point must be a property of the resource, hasp_rs. Specifying this mount point is obligatory if there is more than one mount point in hasp_rs. db_rg=rg The resource group in which sctelemetry configures the resource of type SUNW.derby. You can specify rg, the name of this resource group. db_rs=rs The resource of type SUNW.derby that sctelemetry configures. You can specify rs, the name of this resource. telemetry_rg=rg The resource group in which sctelemetry configures a resource of type SUNW.SCTelemetry. You can specify rg, the name of this resource group. telemetry_rs=rs The resource of type SUNW.SCTelemetry that sctelemetry configures. You can specify rs, the name of this resource. -o hasp_mnt_pt=mnt_pt,hasp_nodelist=node[:...][,hasp_rs=rs][,db_rg=rg][,db_rs=rs][,telemetry_rs=rs] When used with the -i option, specifies the nodes on which the SUNW.HAStoragePlus file system for data collection is accessible and specifies the mount point for the file system in which Sun Cluster stores system resource data. The parameters are as follows: hasp_mnt_pt=mnt_pt The mount point that sctelemetry uses to configure a resource of type SUNW.HAStoragePlus. You must specify mnt_pt, the name of the mount point. The shared storage must be configured before the HAStoragePlus resource to be created. This mount point refers to the shared storage and must appear in /etc/vfstab as follows: /dev/md/ddg/dsk/d20 /dev/md/ddg/rdsk/d20 /mntpt ufs 2 no logging hasp_nodelist=node[:...] The nodes with which sctelemetry configures a resource of type SUNW.HAStoragePlus. You must specify node:[...], the name of the nodes. hasp_rs=rs The resource of type SUNW.HAStoragePlus that sctelemetry configures. You can specify rs, the name of this resource. db_rg=rg The resource group in which sctelemetry configures a resource of type SUNW.derby. You can specify rg, the name of this resource group. db_rs=rs The resource of type SUNW.derby that sctelemetry configures. You can specify rs, the name of this resource. telemetry_rg=rg The resource group in which sctelemetry configures a resource of type SUNW.SCTelemetry. You can specify rg, the name of this resource group. telemetry_rs=rs The resource of type SUNW.SCTelemetry that sctelemetry configures. You can specify rs, the name of this resource. -u Removes the resources and resource groups that were previously created by using the -i option. You can use this option only in the global zone. Users other than superuser require solaris.cluster.system.modify RBAC authorization to use the -u option of the sctelemetry command. For more information, see the rbac(5) man page. EXAMPLES
Initializing System-Resource Monitoring, When a HAStoragePlus Resource Exists This example initializes system-resource monitoring and verifies that monitoring has been initialized. This example assumes that you have a SUNW.HAStoragePlus resource available for system-resource monitoring. This example does not specify the names of the resources db_rs and telemetry_rs or the resource groups db_rg and telemetry_rg. The sctelemetry command gives these resources and resource groups default names. The output of the scstat -g command shows the relationship between resources and resource groups involved in system resource monitoring. The output also shows that the db_rs and hasp_rs resources and the db_rg resource group are each online on one node, the telemetry_rg and telemetry_rs are online on all cluster nodes. # sctelemetry -i -o hasp_mnt_pt=DBDATA,hasp_nodelist=l6-lx-1:l6-lx-4,hasp_rs=anto # scstat -g Disabling System-Resource Monitoring This example disables system-resource monitoring then verifies that the monitoring has been disabled. When monitoring is disabled, the out- put of the scstat -g command shows that the db_rs, hasp_rs, and telemetry_rs resources and the db_rg and telemetry_rg resource groups are offline. # sctelemetry -d # scstat -g EXIT STATUS
The following exit values are returned: 0 The command completed successfully. nonzero An error has occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWsczu | +-----------------------------+-----------------------------+ |Interface Stability |Evolving | +-----------------------------+-----------------------------+ SEE ALSO
Intro(1CL), cltelemetryattribute(1CL), cluster(1CL), scstat(1M), sctelemetry(1M), SUNW.derby(5), SUNW.HAStoragePlus(5), SUNW.SCTelemetry(5) Sun Cluster 3.2 18 Jul 2006 sctelemetry(1M)
All times are GMT -4. The time now is 10:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy