HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Halting the database service alone in a SG package
Operating System - HP-UX
1829102
Members
2509
Online
109986
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2004 01:09 AM
04-16-2004 01:09 AM
Hello there,
We have a SG package configured for our database HA in a metro cluster environment.
We want to shutdown the database (using shutdown immediate) and then take the backup and then start the database again, all using automated scripts.
We can't halt the package as it is doing a 'shutdown abort' and also it halts the package completely.
Is it OK to,
01) Kill the database monitoring process - ".sh monitor"
02) Shutdown the database using ".sh shutdown"
03. Take the backup
04. Start the database using ".sh start"
05. Start the monitoring process using ".sh monitor"
Please advice..
Thanks,
Sajith
We have a SG package configured for our database HA in a metro cluster environment.
We want to shutdown the database (using shutdown immediate) and then take the backup and then start the database again, all using automated scripts.
We can't halt the package as it is doing a 'shutdown abort' and also it halts the package completely.
Is it OK to,
01) Kill the database monitoring process - "
02) Shutdown the database using "
03. Take the backup
04. Start the database using "
05. Start the monitoring process using "
Please advice..
Thanks,
Sajith
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2004 02:55 AM
04-16-2004 02:55 AM
Re: Halting the database service alone in a SG package
Sajith
The answer is 'it depends'
It depends on the contents of your.sh file. I'm assuming this is a standard Enterprise Cluster Master Toolkit script. If it is the first few lines will read something similar to this:
#!/usr/bin/sh
# VERSION="@(#)B5139DA (11.x):"
# "@(#) B.01.08 $Revision: 2.00 $ $Date: 02/02/21 10:18:02 $"
# *****************************************************************************
# ******** Startup, Shutdown and Monitor Script for ORACLE (Template) *********
# *****************************************************************************
# ********** Note: This file MUST be edited before it can be used. ************
# *****************************************************************************
#
If the script has been setup in the 'vanila' way, then shutting down oracle or killing the monitor script will cause a failover.
However the script can be easily changed in the monitor section to look for a flag file to stop monitoring while you do something (like shut it down to back it up)
Have a look at the script attached to this thread by way of example:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=115488
HTH
Duncan
I am an HPE Employee
The answer is 'it depends'
It depends on the contents of your
#!/usr/bin/sh
# VERSION="@(#)B5139DA (11.x):"
# "@(#) B.01.08 $Revision: 2.00 $ $Date: 02/02/21 10:18:02 $"
# *****************************************************************************
# ******** Startup, Shutdown and Monitor Script for ORACLE (Template) *********
# *****************************************************************************
# ********** Note: This file MUST be edited before it can be used. ************
# *****************************************************************************
#
If the script has been setup in the 'vanila' way, then shutting down oracle or killing the monitor script will cause a failover.
However the script can be easily changed in the monitor section to look for a flag file to stop monitoring while you do something (like shut it down to back it up)
Have a look at the script attached to this thread by way of example:
http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=115488
HTH
Duncan
I am an HPE Employee

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-16-2004 05:45 AM
04-16-2004 05:45 AM
Solution
You need to setup a no monitor flag - if you kill the monitoring process - the package will fail over....
Here's something I did for lp spool...
Here's something I did for lp spool...
Proverbs 3:5,6 Trust in the Lord with all your heart and lean not on your own understanding; in all your ways acknowledge him, and he will make all your paths straight.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP