HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Oracle Monitorint Scripts
Operating System - HP-UX
1836992
Members
2057
Online
110111
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
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
07-29-2002 04:43 AM
07-29-2002 04:43 AM
Oracle Monitorint Scripts
How do I configure MC/Serviceguard NOT to fail over to a secondary node if the Oracle monitoring script fails or goes down?
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2002 05:08 AM
07-29-2002 05:08 AM
Re: Oracle Monitorint Scripts
Hi Brent,
This may sound like a foolish answer, but if you do NOT want Oracle to failover, you shouldn't put it in a package in the first place. Run it locally ...
Or am I missing your point here ? Please explain what it is exactly that you want to achieve ...
Regards,
Tom
This may sound like a foolish answer, but if you do NOT want Oracle to failover, you shouldn't put it in a package in the first place. Run it locally ...
Or am I missing your point here ? Please explain what it is exactly that you want to achieve ...
Regards,
Tom
A life ? Cool ! Where can I download one of those from ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-29-2002 05:20 AM
07-29-2002 05:20 AM
Re: Oracle Monitorint Scripts
I assume that you want a way to do Oracle maintenance without SG interference.
In your.cntl file you should have your Oracle monitoring script defined in this section ...
# SERVICE NAMES AND COMMANDS.
# Specify the service name, command, and restart parameters which are
# used by this package. Uncomment SERVICE_NAME[0]="", SERVICE_CMD[0]="",
# SERVICE_RESTART[0]="" and fill in the name of the first service, command,
# and restart parameters. You must begin with SERVICE_NAME[0], SERVICE_CMD[0],
# and SERVICE_RESTART[0] and increment the list in sequence.
#
# For example:
# SERVICE_NAME[0]=pkg1a
# SERVICE_CMD[0]="/usr/bin/X11/xclock -display 192.10.25.54:0"
# SERVICE_RESTART[0]="" # Will not restart the service.
#
# SERVICE_NAME[1]=pkg1b
# SERVICE_CMD[1]="/usr/bin/X11/xload -display 192.10.25.54:0"
# SERVICE_RESTART[1]="-r 2" # Will restart the service twice.
#
# SERVICE_NAME[2]=pkg1c
# SERVICE_CMD[2]="/usr/sbin/ping"
# SERVICE_RESTART[2]="-R" # Will restart the service an infinite
# number of times.
#
# Note: No environmental variables will be passed to the command, this
# includes the PATH variable. Absolute path names are required for the
# service command definition. Default shell is /usr/bin/sh.
#
...
so you might have ...
SERVICE_NAME[0]="Oracle_Monitor"
SERVICE_CMD[0]="/etc/cmcluster/oraclepkg/oraclepkg.sh monitor"
SERVICE_RESTART[0]=""
...
Then in oraclepkg.sh
there should be a loop that checks the DB status every few seconds.
In this monitor loop, you probably runs an Oracle control script that checks the status.
This Oracle control script can now check a control file to see if you want failover to occur or not.
Then when you want to do maintenance, you change the monitor option in the control file. Do your maintenance. Then change the control file option back when you are finished.
I'm sure there are many ways to do what you want.
I hope this makes sense, I tried not to make it too complicated.
This solution has worked good for us.
Rich
In your
# SERVICE NAMES AND COMMANDS.
# Specify the service name, command, and restart parameters which are
# used by this package. Uncomment SERVICE_NAME[0]="", SERVICE_CMD[0]="",
# SERVICE_RESTART[0]="" and fill in the name of the first service, command,
# and restart parameters. You must begin with SERVICE_NAME[0], SERVICE_CMD[0],
# and SERVICE_RESTART[0] and increment the list in sequence.
#
# For example:
# SERVICE_NAME[0]=pkg1a
# SERVICE_CMD[0]="/usr/bin/X11/xclock -display 192.10.25.54:0"
# SERVICE_RESTART[0]="" # Will not restart the service.
#
# SERVICE_NAME[1]=pkg1b
# SERVICE_CMD[1]="/usr/bin/X11/xload -display 192.10.25.54:0"
# SERVICE_RESTART[1]="-r 2" # Will restart the service twice.
#
# SERVICE_NAME[2]=pkg1c
# SERVICE_CMD[2]="/usr/sbin/ping"
# SERVICE_RESTART[2]="-R" # Will restart the service an infinite
# number of times.
#
# Note: No environmental variables will be passed to the command, this
# includes the PATH variable. Absolute path names are required for the
# service command definition. Default shell is /usr/bin/sh.
#
...
so you might have ...
SERVICE_NAME[0]="Oracle_Monitor"
SERVICE_CMD[0]="/etc/cmcluster/oraclepkg/oraclepkg.sh monitor"
SERVICE_RESTART[0]=""
...
Then in oraclepkg.sh
there should be a loop that checks the DB status every few seconds.
In this monitor loop, you probably runs an Oracle control script that checks the status.
This Oracle control script can now check a control file to see if you want failover to occur or not.
Then when you want to do maintenance, you change the monitor option in the control file. Do your maintenance. Then change the control file option back when you are finished.
I'm sure there are many ways to do what you want.
I hope this makes sense, I tried not to make it too complicated.
This solution has worked good for us.
Rich
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