Bug 581515
Summary: | oracledb.sh script assumes it needs to start Enterprise Manager and iSQL*Plus when oracle 10G | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Craig Kornmesser <tkornmes> | ||||||
Component: | rgmanager | Assignee: | Lon Hohberger <lhh> | ||||||
Status: | CLOSED NOTABUG | QA Contact: | Cluster QE <mspqa-list> | ||||||
Severity: | medium | Docs Contact: | |||||||
Priority: | low | ||||||||
Version: | 5.5 | CC: | cluster-maint, iannis | ||||||
Target Milestone: | rc | ||||||||
Target Release: | --- | ||||||||
Hardware: | All | ||||||||
OS: | Linux | ||||||||
Whiteboard: | |||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||
Doc Text: | Story Points: | --- | |||||||
Clone Of: | |||||||||
: | 587399 (view as bug list) | Environment: | |||||||
Last Closed: | 2010-04-29 19:33:00 UTC | Type: | --- | ||||||
Regression: | --- | Mount Type: | --- | ||||||
Documentation: | --- | CRM: | |||||||
Verified Versions: | Category: | --- | |||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||
Embargoed: | |||||||||
Bug Depends On: | |||||||||
Bug Blocks: | 587399 | ||||||||
Attachments: |
|
Description
Craig Kornmesser
2010-04-12 13:53:40 UTC
Please attach your cluster.conf Created attachment 405972 [details]
Cluster.conf file from cluster
Created attachment 405974 [details]
oracledb.sh file with the changes I've had to make to make sure it starts Oracle via the cluster
<longdesc lang="en"> This is the Oracle installation type: base - Database Instance and Listener only base-em (or 10g) - Database, Listener, Enterprise Manager, and iSQL*Plus ias (or 10g-ias) </longdesc> Sounds like setting it to "base" should work for your configuration without editing the script. I understand I could set it to base, but where would you set that such that you don't run the risk of it getting overwritten? Any changes to the oracledb.sh file will get overwritten when an update is applied to the rgmanager package. Which is exactly what happened here. The script incorrectly identifies any 10G install as base-em, which is incorrect. Changing this line in cluster.conf: <oracledb home="/wchillp/app/oracle/product/10.2.0" name="WCHILL1P" type="10g" user="oracle" vhost="vip-windchilldb.carrier.utc.com"/> to: <oracledb home="/wchillp/app/oracle/product/10.2.0" name="WCHILL1P" type="base" user="oracle" vhost="vip-windchilldb.carrier.utc.com"/> ... should do it. (Don't forget to change the config version and so forth; making a change to the agent will cause the Oracle instance to be restarted, so do it at your next maintenance window) Oops -- making a change to the resource line in cluster.conf, not the agent, will cause the resource instance to be restarted. Oh, Ok... I guess. I wish this was better documented and when you try to use the agent configuration via luci, it gives you a pull down menu for the type and let you choose from the three options: base, base-em or base-asi. I had contacted Redhat support when I was initially trying to get this to work, but they were not very helpful. All they did was have me create my own oracle agent, which was still not the right answer. I'm sorry that Red Hat Support did not answer your question as required. If you'd like, we can clone this bug against the luci interface and/or Documentation for clarification as to what the base/base-em/base-ias possibilities mean. However, as far as rgmanager is concerned, this isn't a bug. |