|
|
Sponsored Content
Operating Systems
Solaris
Shutdown Oracle DB on SunOS Cluster
Post 302946341 by Peasant on Monday 8th of June 2015 11:30:40 AM
06-08-2015
Moderator
You should not issue shutdown commands from instance on Solaris Cluster.
The clusterware will see this as failed resource group and will failover on another node.
What you need to do is :
Identify the cluster group resource which is responsible for resources.
clrg show and clrs show will tell you that.
After you have identifed the cluster group(s) responsible for database you will just need to do a clrg offline group-name
This will stop everything related to database (every resource in resource group[s]), umount filesystems if used, stop ASM etc. -> depending on the resources configuration and database resources setup).
If you want to tinkle around the database while resource group is online you will need to put its resources in unmonitor state clrg unmonitor group-name .
Be sure to return them to monitor after you are done, or risk failover not happening.
Test this on virtualbox cluster or test enviroment, setup a small cluster and get into resource groups and resources
I haven't done this with oracle databases, but i have with NFS and HA filesystem on sun cluster.
Hope that helps.
Regards
Peasant.
The clusterware will see this as failed resource group and will failover on another node.
What you need to do is :
Identify the cluster group resource which is responsible for resources.
clrg show and clrs show will tell you that.
After you have identifed the cluster group(s) responsible for database you will just need to do a clrg offline group-name
This will stop everything related to database (every resource in resource group[s]), umount filesystems if used, stop ASM etc. -> depending on the resources configuration and database resources setup).
If you want to tinkle around the database while resource group is online you will need to put its resources in unmonitor state clrg unmonitor group-name .
Be sure to return them to monitor after you are done, or risk failover not happening.
Test this on virtualbox cluster or test enviroment, setup a small cluster and get into resource groups and resources
I haven't done this with oracle databases, but i have with NFS and HA filesystem on sun cluster.
Hope that helps.
Regards
Peasant.
|
|
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Guys, how do I connect to a Oracle Database from my machines running on Solaris 5 and 9. Do I need a Oracle client installed or is there any other way to connect to the Oracle Db without using the oracle client?
Any inputs will be highly appreciated. (2 Replies)
Discussion started by: darmat0712
2 Replies
2. UNIX for Advanced & Expert Users
Hi,
Iam calling 3 sql scripts through one shell script 'rmia.sh'.
Till now this was working fine, but last time while calling the SQL scripts,
Oracle was down. But amazingly the exit status was '0' (success)!!!
Below is the shell code:
#!/usr/bin/ksh -x
assign_file asql a.sql 1... (15 Replies)
Discussion started by: ganapati
15 Replies
3. Shell Programming and Scripting
Hello all.
I have built a cluster of 9 Macs for computational chemistry and I need a shell script that I can use from one computer to all the rest to shutdown.
I have modified all of the Macs so that there is pass-wordless ssh. As well, I have modified each "visudo" file on each machine by... (1 Reply)
Discussion started by: marcozd
1 Replies
4. Solaris
Hi,
I have a SUN cluster system.
I want to know what script do when the SUN cluster shutdown the package as I may need to modify it ?? Where can I find out this information in the system??
In which directory and log file ???
Any suggestion ??? (5 Replies)
Discussion started by: chuikingman
5 Replies
5. UNIX for Dummies Questions & Answers
I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS).
Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies
6. Solaris
hope this is the correct spot.
we have 4 unit running SunOS 8.5 2 in offices and 2 running equipment in the lab.
the communicate over our network to run/monitor jobs on the equipment.
they randomly shut off recently. twice last thursday and once this friday.
the vendor of the equipment... (4 Replies)
Discussion started by: fah_kinright
4 Replies
LEARN ABOUT CENTOS
ocf_heartbeat_lvm
OCF_HEARTBEAT_LVM(7) OCF resource agents OCF_HEARTBEAT_LVM(7) NAME
ocf_heartbeat_LVM - Controls the availability of an LVM Volume Group SYNOPSIS
LVM [start | stop | status | monitor | meta-data | validate-all] DESCRIPTION
Resource script for LVM. It manages an Linux Volume Manager volume (LVM) as an HA resource. SUPPORTED PARAMETERS
volgrpname The name of volume group. (required, string, no default) exclusive If set, the volume group will be activated exclusively. This option works one of two ways. If the volume group has the cluster attribute set, then the volume group will be activated exclusively using clvmd across the cluster. If the cluster attribute is not set, the volume group will be activated exclusively through the use of the volume_list filter in lvm.conf. In the filter scenario, the LVM agent verifies that pacemaker's configuration will result in the volume group only being active on a single node in the cluster and that the local node's volume_list filter will prevent the volume group from activating outside of the resource agent. On activation this agent claims the volume group through the use of a unique tag, and then overrides the volume_list field in a way that allows the volume group to be activated only by the agent. To use exclusive activation without clvmd, the volume_list in lvm.conf must be initialized. If volume groups exist locally that are not controlled by the cluster, such as the root volume group, make sure those volume groups are listed in the volume_list so they will be allowed to activate on bootup. (optional, boolean, default false) tag If "exclusive" is set on a non clustered volume group, this overrides the tag to be used. (optional, string, default "pacemaker") partial_activation If set, the volume group will be activated even only partial of the physical volumes available. It helps to set to true, when you are using mirroring logical volumes. (optional, string, default "false") SUPPORTED ACTIONS
This resource agent supports the following actions (operations): start Starts the resource. Suggested minimum timeout: 30. stop Stops the resource. Suggested minimum timeout: 30. status Performs a status check. Suggested minimum timeout: 30. monitor Performs a detailed status check. Suggested minimum timeout: 30. Suggested interval: 10. methods Suggested minimum timeout: 5. meta-data Retrieves resource agent metadata (internal use only). Suggested minimum timeout: 5. validate-all Performs a validation of the resource configuration. Suggested minimum timeout: 5. EXAMPLE
The following is an example configuration for a LVM resource using the crm(8) shell: primitive p_LVM ocf:heartbeat:LVM params volgrpname=string op monitor depth="0" timeout="30" interval="10" SEE ALSO
http://www.linux-ha.org/wiki/LVM_(resource_agent) AUTHOR
Linux-HA contributors (see the resource agent source for information about individual authors) resource-agents UNKNOWN 06/09/2014 OCF_HEARTBEAT_LVM(7)