- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- IRac failover with HyperFabric
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
Discussions
Discussions
Forums
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
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
тАО03-23-2004 07:25 AM
тАО03-23-2004 07:25 AM
IRac failover with HyperFabric
Regards
Christian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-23-2004 02:00 PM
тАО03-23-2004 02:00 PM
Re: IRac failover with HyperFabric
This appears to be a standard response. Oracle appears to rely more on the cluster heartbeat than it's own. I would check out your cluster heartbeat setting inside of your cmcluster.ascii file, and see if it can be changed instead.
You should consider adding a secondary network backup for this, so that a failure of your Hyperfabric will not bring the RAC cluster down. Your normal network connections could probably be used for this so you don't have to buy another set of hyperfabric cards.
Thanks,
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2004 05:05 AM
тАО03-24-2004 05:05 AM
Re: IRac failover with HyperFabric
the two nodes of the cluster access in active mode to the same VG.
The PKG doesn't have Service Guard Failover, because this is a Oracle function.
I cut the link between the two Rac nodes, bacause I must test the behaivor of the installation. I know that this is an Oracle issue, but I don't find the items that I must change.
Regards.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-24-2004 08:04 AM
тАО03-24-2004 08:04 AM
Re: IRac failover with HyperFabric
Take a look at the following parameters:
HEARTBEAT_IP (one for each node)
HEARTBEAT_INTERVAL
NODE_TIMEOUT
If the cluster is not detecting the failure, then you will have to wait for the database to detect it. Looking through metalink, I don't see any way to change this.
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-25-2004 09:07 AM
тАО03-25-2004 09:07 AM
Re: IRac failover with HyperFabric
What did you think?
Regards
Christian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2004 09:20 AM
тАО03-29-2004 09:20 AM
Re: IRac failover with HyperFabric
Thanks,
Brian
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-29-2004 10:09 AM
тАО03-29-2004 10:09 AM
Re: IRac failover with HyperFabric
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-20-2004 10:05 AM
тАО04-20-2004 10:05 AM
Re: IRac failover with HyperFabric
there are in the init file 3 hidden parameters:
_cgs_send_timeout,
_lm_dlm_send_timeout,
_imr_splitbrain_res_wait
With this parameters you can control the time that the database wait for the Operative System, and the time that the database, after take the control migrate the sessions.
We are testing this issue right now
Regards
Christian Pisacane
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 12:05 AM
тАО04-21-2004 12:05 AM
Re: IRac failover with HyperFabric
_cgs_send_timeout = 5
Also, if you have HyperFabric/2, why not use HMP rather than UDP or TCP/IP. This has lower latency and lower CPU usage, but also is synchronous rather than using an asynchronous protocol like UDP. Win win. You have to relink Oracle to do this.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-21-2004 03:24 AM
тАО04-21-2004 03:24 AM
Re: IRac failover with HyperFabric
Regards
Christian