Re: Oracle 10g kills 8i listener

More specifically, the local_listener parameter needs to be set to a tnsname alias (defined in tnsnames.ora) that resolves to the listener that listens to that different port - read my original post :-).

Ron (support_at_dbainfopower.com) wrote:

: Hello Xu,

: I believe you can to disable automatic 10g service registration.

: To do this, you must set the init.ora parameter local_listener to use a
: TCP port other than the one defined in your listener.ora file.

: Regards,

: Ron
: DBA Infopower
: http://www.dbainfopower.com
: Standard disclaimer:
: http://www.dbainfopower.com/dbaip_advice_disclaimer.html

: "Xuequn Xu" <xux_at_informa.bio.caltech.edu> wrote in message
: news:c0jff3$3sv$1_at_naig.caltech.edu...
: > Just want to share some intersting experience and observations:
: >
: > I installed Oracle 10g on Solaris 5.8, and on the same box there is
: > another Oracle 8i instance installed and running, with a separate
: > ORACLE_HOME (8.1.7.4). I found that the moment I startup the 10g instance
: > the 8i listener stopped responding. Further testing showed that this
: > only happens when the 10g database is about to open (i.e. startup nomount
: > and startup mount does NOT make this happen). The 8i listener is running
: > at port 1521. This must be that the 10g instance cannot do service
: > registration with an 8i listener. Had to resolve this by running 10g's
: > own listener at another port (in my case 1526), and specify the
: > LOCAL_LISTENER parameter in 10g, pointing to a tnsnames.ora entry
: > that resolves the new listener.
: >
Received on Fri Feb 13 2004 - 23:03:12 CST