Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1200639

Summary: orainstance.sh pauses for 90 seconds to wait for exiting oracle processes.
Product: Red Hat Enterprise Linux 6 Reporter: Takayuki Nagata <tnagata>
Component: resource-agentsAssignee: Oyvind Albrigtsen <oalbrigt>
Status: CLOSED ERRATA QA Contact: cluster-qe <cluster-qe>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.6CC: agk, cluster-maint, mlisik, sbradley, tlavigne
Target Milestone: rcKeywords: EasyFix, Patch
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: resource-agents-3.9.5-26.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-10 19:13:49 UTC Type: Bug
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: 1172231    
Attachments:
Description Flags
proposal for the fix
none
Working patch none

Comment 2 Takayuki Nagata 2015-03-11 07:43:28 UTC 
I have sent the upstream a pull request.
https://github.com/ClusterLabs/resource-agents/pull/583

The customer has verified the fix.
Comment 9 Oyvind Albrigtsen 2015-10-20 15:21:06 UTC 
Created attachment 1084806 [details]
Working patch
Comment 10 Oyvind Albrigtsen 2015-10-20 15:24:08 UTC 
Tested and verified that if you had one database called e.g. "db" and another called e.g. "db2", you end up waiting 90 seconds and killing "db2" as well when trying to kill "db".

Tested with patch, and attached the working patch.
Comment 11 Oyvind Albrigtsen 2015-10-29 10:10:49 UTC 
Say you have 2 databases (cdb running from rgmanager and cdb2 running separately), this update will solve the issue where cdb2 which isnt controlled by rgmanager gets killed because it contains cdb in it's name. This also causes a 90 sec wait. 

Before:
Start e.g. cdb2 and stop the oracle service from rgmanager
# clusvcadm -d oracle

Expected: cdb2 is still running, and cdb is stopped.
Result: both cdb2 and cdb are stopped during 90 sec stop period.


After:
Start e.g. cdb2 and stop the oracle service from rgmanager
# clusvcadm -d oracle

Expected: cdb2 is still running, and cdb is stopped.
Result: cdb2 is still running, and cdb is stopped without any wait.
Comment 15 errata-xmlrpc 2016-05-10 19:13:49 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-0735.html