From: Mohan Sundaram (Mohan_Sundaram@emitac.ae)
Date: Sat Mar 20 2004 - 06:43:47 EST
Hi Folks,
This is a sort of second summary for this question.
In conclusion, I had referred the issue to HP and it seems HP is aware of such limitations existing for the Oracle9i (infrastructure) in serviceguard setup.
As per HP, it is not recommended to change the hostname, but it has documents of such a problem being reported. The solution is, the application vendor has to take care of any problems arising out of such a hostname modification.
When I conveyed this to the Oracle team, they agreed to use only the oracle Interpositioning libraries for the virtual hostname. They will not modify the hostname explicitly.
The inter-positioning library is the documented method in Oracle and the same was indicated by most of the respondents here.
I am also attaching the document sent by HP engineer to me. I hope I can share this info for the benefit of everyone here.
Thanks once again for all who responded.
Cheers,
Mohan.
-----Original Message-----
From: Mohan Sundaram
Sent: Monday, March 01, 2004 9:38 AM
To: 'hpux-admin@dutchworks.nl'
Subject: SUMMARY:Question on Serviceguard+oracle 9i
Hi Folks,
Thank you all for providing me your inputs on this. Everybody seems to reflect the same Idea that modifying the hostname may result in many problems. Interestingly, I had lodged a call with HP for this and they came up with the below document,
----------------------------------------------------------------------------------------------------------------------------------------
link <http://technet.oracle.com/products/ias/files/9iAS_Infra_HA_HPUX.zip> http://technet.oracle.com/products/ias/files/9iAS_Infra_HA_HPUX.zip
youŽll get a package where you find a document called
"Oracle9i Application Server Infrastructure:
Improved Availability with MC/ServiceGuard on HP-UX" (pdf attached) ,
which states:
Page 2:
Limitations:
...
2) Upon implementation of this solution, the active runtime of one of the
two nodes of the cluster will be with the node's hostname set to a
virtual hostname and not to the original hostname registered for the
cluster. This will result in some MC/ServiceGuard commands to fail on
that node. MC/ServiceGuard commands will work as expected on the other
node.
Page 7:
...
Note that the cmhaltpkg package1 command to stop the
package/infrastructure needs to be executed on the node that is not
running the package/infrastructure since running the
package/infrastructure will change the hostname of that node to the
virtual hostname and since MC/ServiceGuard commands will not execute
properly when the system is set to the virtual hostname (see the
LIMITATIONS section). Since a successfully executed cmhaltpkg package1
will restore the hostname back to the original hostname on the node where
the package/infrastructure was stopped, all MC/ServiceGuard commands will
function properly on that node until the package/infrastructure is
restarted.
----------------------------------------------------------------------------------------------------------------------------------------
I had further asked Oracle people to provide me the document which states that the host name needs to be modified. They have also opened a tar for the same.
Meanwhile I am checking with HP if the serviceguard A.11.15 too is having this limitation.
I will post the final conclusion to the forum once I get replies from HP and Oracle.
Thanks once again for all your time.
With regards,
Mohan.
-----Original Message-----
From: Mohan Sundaram
Sent: Wednesday, February 25, 2004 4:30 PM
To: 'hpux-admin@dutchworks.nl'
Subject: Question on Serviceguard+oracle 9i
Hi Folks,
I have an installation where 2 HP-UX 11i (rp7410) systems are configured in serviceguard 11.15. Oracle people are installing 9i Infrastructure on the setup. They have put a startup and halt script for the package, wherein they are explicitly modifying the hostname by
hostname <virtual IP hostname>
I have a concern if this is a correct practice. Whenever I move the package and test, it modifies the hostname. I cannot restart the cluster without rebooting or manually modifying the hostname back to its original name.
In case of a LAN heartbeat failure the package may switch to the adoptive node and both the primary and adoptive nodes may have the same Hostnames in that scenario.
Any of you have encountered this problem? if so, how was this tackled?
Thanks in Advance.
With regards,
Mohan.
--
---> Please post QUESTIONS and SUMMARIES only!! <---
To subscribe/unsubscribe to this list, contact majordomo@dutchworks.nl
Name: hpux-admin@dutchworks.nl Owner: owner-hpux-admin@dutchworks.nl
Archives: ftp.dutchworks.nl:/pub/digests/hpux-admin (FTP, browse only)
http://www.dutchworks.nl/htbin/hpsysadmin (Web, browse & search)
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 11:02:39 EDT