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
Old 06-08-2015
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 Smilie

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

Connecting to a Oracle Db using SunOS

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

Capturing Oracle Shutdown error

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

Shell script to Shutdown Computers on Cluster

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

Shutdown the package in SUN cluster

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

Script to force Oracle database shutdown when shutdown immediate does not work

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

SunOS 8.5 random shutdown

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
OCI_SET_CLIENT_INFO(3)													    OCI_SET_CLIENT_INFO(3)

oci_set_client_info - Sets the client information

SYNOPSIS
bool oci_set_client_info (resource $connection, string $client_info) DESCRIPTION
Sets the client information for Oracle tracing. The client information is registered with the database when the next 'roundtrip' from PHP to the database occurs, typically when an SQL statement is executed. The client information can subsequently be queried from database administration views such as V$SESSION. The value may be retained across persistent connections. PARAMETERS
o $connection -An Oracle connection identifier, returned by oci_connect(3), oci_pconnect(3), or oci_new_connect(3). o $client_info - User chosen string up to 64 bytes long. RETURN VALUES
Returns TRUE on success or FALSE on failure. EXAMPLES
Example #1 Setting the client information <?php $c = oci_connect('hr', 'welcome', 'localhost/XE'); // Record the client information oci_set_client_info($c, 'My Application Version 2'); // Code that causes a roundtrip, for example a query: $s = oci_parse($c, 'select * from dual'); oci_execute($s); oci_fetch_all($s, $res); sleep(30); ?> // While the script is running, the administrator can see the client // information: sqlplus system/welcome SQL> select client_info from v$session; NOTES
Note Oracle version requirement This function is available when PHP is linked with Oracle Database libraries from version 10 g onwards. Tip Performance With older versions of OCI8 or the Oracle Database, the client information can be set using the Oracle DBMS_APPLICATION_INFO pack- age. This is less efficient than using oci_set_client_info(3). Caution Roundtrip Gotcha Some but not all OCI8 functions cause roundtrips. Roundtrips to the database may not occur with queries when result caching is enabled. SEE ALSO
oci_set_module_name(3), oci_set_action(3), oci_set_client_identifier(3). PHP Documentation Group OCI_SET_CLIENT_INFO(3)
All times are GMT -4. The time now is 07:40 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy