Re: fooling EM setup into using a different host name

On Fri, 25 Aug 2006 10:18:06 +0200, Sybrand Bakker <postbus_at_sybrandb.demon.nl> wrote:

>On Fri, 25 Aug 2006 03:15:33 -0400, NetComrade
><netcomradeNSPAM_at_bookexchange.net> wrote:
>
>>Our hostname is 'sun'
>>However, the database listens on 'orasun' (so that we could fail it
>>over to another host)
>>I've tried playing with configs, but I just don't really know what to
>>change.
>>Is there are a way to make the initial setup use a different host
>>name? I tried setting up HOST and HOSTNAME env variables, but that
>>didn't help
>>

>There is an article on Metalink discussing physical and virtual hosts.
>I really don't have the Doc ID handy, but I know exists.
>If there is anything that can be done, it needs to be done via
>aliasing the host name in /etc/hosts
>like
>192.168.0.10 sun orasun
>
>I have the feeling though your current set up is a home-grown
>workaround.
>Ordinary failover uses virtual IP and virtual hostnames.
>Home-grown workarounds like this are probably doomed to fail.

We use Veritas Cluster server for over 7 years now, first on Solaris, now on Linux, works like a charm (well.. we had some fun with it too)

Oracle listens on a Virtual IP, so sun != orasun. Problem with emca -config dbcontrol db -repos create is that it doesn't let me specify the host, and it tries to connect to 'sun'. I found where to change the connection string, so at least EM connects to the right port,but it looks like I need to change it in more than one place. Of course, I could try the workaround of creating another listener on host 'sun' for all the instances just for EM, but that just won't be 'right'
.......
We run Oracle 9iR2,10gR1/2 on RH4/RH3
remove NSPAM to email Received on Fri Aug 25 2006 - 09:29:52 CDT