From: tom.kempster@aero.bombardier.com
Date: Tue Jan 17 2006 - 10:21:44 EST
I would really like to thank the people who have taken the time to answer
this, it has been really useful and has indeed led to a solution. I was
aware that many people would have come across this but people have devoted
their time and given many offers of support.
I found that there were 2 possible routes to take, 1) Using a cluster alias
and 2) Using an IP address.
Because 2) satisfied my requirements perfectly I am currently going along
that route. These were found in the Best Practices link
http://h30097.www3.hp.com/docs/best_practices/BP_TCR_ORA_SS/TITLE.HTM
So far I have had success with testing, I can start and stop SAP and Oracle
on either server. The only problem so far is that we run our own start and
stop files. I was told by SAP last week that we should use the provided SAP
files (sapstart in the run dir). This gives me other errors and will not
connect to to the database (ERROR => CONNECT failed with sql error '1034')
so I am ignoring that for now. This SAP man who was here last week on
another project said he thought it was not possible to use a cluster alias
because the latest SAP looked for a hostname using "hostname -n" and this
was hardcoded. I have tried to reset the hostname to the alias name but
this gives other errors.
I will not look in to this now because of time constraints.
Regards,
Tom Kempster
I am installing SAP and Oracle (not RAC) on a 2 node cluster. We hope to
have SAP running on one server and to failover and start SAP/Oracle on the
other server when required.
I am unsure of how to cater for the files that use a hostname, such as
DEFAULT.PFL, tnsnames.ora and listener.ora for example. On failover these
files will point to the first server and naming the cluster alias in these
files will not work.
Can anyone advise how this is normally handled, please.
Regards,
Tom Kempster
tomkempster@aero.bombardier.com
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:50:27 EDT