- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Service Guard and OEM
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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
05-04-2006 07:54 PM
05-04-2006 07:54 PM
Service Guard and OEM
I have three Oracle databases running in my 2 node cluster. Each database has its own package. I want to add an OEM agent to each package.
I have added a new service to the .conf file. I have added a new file system and a start/stop/monitor section to the .cntl file.
I can start & stop it fine but the monitoring fails.
Does anyone use OEM to monitor their Oracle databases in a cluster,
thanks in advance
Shane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2006 08:04 PM
05-04-2006 08:04 PM
Re: Service Guard and OEM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2006 08:27 PM
05-04-2006 08:27 PM
Re: Service Guard and OEM
May 4 14:27:44 - Node "waldorf": Starting service WLRCONP using
"/etc/cmcluster/wlrconp/toolkit.sh monitor"
May 4 14:27:44 - Node "waldorf": Starting service WLR_OEM using
"/etc/cmcluster/wlrconp/toolkit_oem.sh monitor"
cmrunserv : Service name WLR_OEM does not exist.
ERROR: Function start_services
ERROR: Failed to start service WLR_OEM
May 4 14:27:44 - Node "waldorf": Halting service WLRCONP
May 4 14:27:45 - Node "waldorf": Halting service WLR_OEM
cmhaltserv : Service name WLR_OEM is not running.
May 4 14:27:45 - Node "waldorf"
*** /etc/cmcluster/wlrconp/wlr_oem.sh called with stop argument. ***
May 4 14:27:45 - Node "waldorf"
: Aborting OEM Agent at Thu May 4 14:27:45 BST 2006
In the OEM stop function ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-04-2006 08:33 PM
05-04-2006 08:33 PM
Re: Service Guard and OEM
Additionally you can also put set -vx in /etc/cmcluster/wlrconp/toolkit.sh and check.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2006 12:17 AM
05-05-2006 12:17 AM
Re: Service Guard and OEM
SERVICE_NAME
SERVICE_FAIL_FAST_ENABLED
SERVICE_HALT_TIMEOUT
If you added them to the configuration file, you have to halt the package and then cmapplyconf the configuration file so that the cluster binary file has a reference for the service name. Use cmviewconf to see what is in the cluster binary.
If the cluster binary has a reference for the new service, then make certain that you add a set of these parameters customized in the package control script:
SERVICE_NAME[0]=""
SERVICE_CMD[0]=""
SERVICE_RESTART[0]=""
If you previously defined a service in the script, don't forget to increment the index number in brackets on this new service definition.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2006 03:03 AM
05-05-2006 03:03 AM
Re: Service Guard and OEM
cmrunserv : Service name WLR_OEM does not exist.
You have put the service commands in the control script file, but not configured this service into your package in the package configuration file.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-05-2006 07:59 AM
05-05-2006 07:59 AM
Re: Service Guard and OEM
This was 9i, not sure if the same issues exist with 10g.
Good luck,
Greg.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-07-2006 11:52 PM
05-07-2006 11:52 PM
Re: Service Guard and OEM
I even played around with editing several config-Files to get this thing running with the Package-IP, but no success.
Christian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2006 07:43 AM
05-08-2006 07:43 AM
Re: Service Guard and OEM
Good to know that Oracle has not corrected this issue ;^{
Did you get it to work? As I mentioned, we got this to work on 9i by keeping the "real" hostnames in the OEM config files on each of the cluster nodes.
--Greg
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-08-2006 07:22 PM
05-08-2006 07:22 PM
Re: Service Guard and OEM
I played around with creating symlinks in ORACLE_HOME for each physical nodename linked to my package_name. I also greped through most of the files in the config dir of OEM and changed the names, but that did not work perfectly either. (And is not supported by Oracle!)
The thing is, that OEM always reports the DB and the listener to be down, even if it is not.
But most other things are working.
We already have a EM-Grid-Control (10GR1) running on a Windowsbox. Unfortunately this Version of Gridcontrol does not support 10GR2; the Windows-Version for 10GR2 should be available after summer 2006.
Christian