Re: two listeners help

I would suggest that you configure the listener separately for the two instances. You can do this in the same listener.ora.

You can call the new listener anything you want (e.g. XYZ).

The sid list must then be suitably modified: SID_LIST_XYZ.

So now you'll have two sets of entries:

LISTENER .... SID_LIST_LISTENER ... XYZ ... SID_LIST_XYZ ... The XYZ entries will be a copy of the originals but with the SID changed, a new port number and any v8 specific entries.

In addition, any other parameters need to duplicated in the same way. E.g. LOG_FILE_XYZ, LOG_DIRECTORY_XYZ, etc. (I'm doing this from memory so I may get the names slightly wrong.)

You will also need to add parallel entries into each TNS_NAMES file on your clients (or the entry in your names server).

The downside of this is that you can't start all the listeners in one command this way. You will have to start the XYZ listener by:

   lsnrctl start XYZ

The advantage is that you can bring the listener of one down without any impact on the other database.

Len

>Hi,
>
>On Unix platform, I have installed an V8.0.6 db and would like to have it
>co-existing with production V7.3.2 before finally switched over. V7.3.2
>use port 1521 for listener. I would like to have two listeners co-exist
>in order not to have conflict. V8 db uses "oracle8" while V7 use "oracle"
>as owner. I would have 1526 as V8 listener.
>
>So how to implement it? Do anyone think I should change tnslsnr name in
>order not to confuse the system? By the way, multiple listeners is
>supported, then would that mean you need multiple ports launched by one
>listener only, or need multiple listeners, such as multiple tnslsnr files
>(both db do have its tnslsnr file with diff size)?
>
>I would like comment before I crash my system.
>
>All helps are very appreciated.
>
>Steve
>
>
Received on Sat Nov 18 2000 - 12:16:46 CST