Home » RDBMS Server » Networking and Gateways » Running SQL*Net V2 and Net8 together
Running SQL*Net V2 and Net8 together [message #367565] Wed, 09 September 1998 05:19 Go to next message
David Morin
Messages: 2
Registered: September 1998
Junior Member
I'm currently setting up an Oracle developement environment on a SUN Solaris
system. In this environment versions 7.3.4 and 8.0.5 of the RDBMS are running together.

Every RDBMS has its own Unix DBA user belonging to the dba Unix group, its own ORACLE_SID, ORACLE_HOME, TNS_ADMIN, ...

To keep each environment independant from the other, I have decided to setup two
listeners withe their own sets of ".ora" config files.
For Oracle 8.0.5, the Net8 listener is named LSNR_805. On TCP/IP level, it listens on port 1526.
For Oracle 7.3.4, the SQL*Net V2 listener is named LSNR_734. On TCP/IP level, it listens on port 1521.

I start the Net8 listener with the command :
lsnrctl start LSNR_805
Everything runs OK.

I start the SQL*Net V2 listener with the command :
lsnrctl start LSNR_734
I get the message
TNS-01106: Listener using listener name LSNR_805 has already been started
This is correct, but it doesn't make me happy.
TNS-00116 message details is :
01106, 00000, "Listener using listener name %s has already been started"
// *Cause: Another listener is already listening on one of the ADDRESSes specified.
// *Action: Shutdown the previous listener specified by the listener name
before starting this one.

I have two kinds of actions in the /etc/services file:
1. remove the entry
listener 1521/tcp
I added following the Oracle 8.0.5 installation guide. (I never did it
for Oracle 7.3.4, and it always worked)
2. add the entries :
lsnr_734 1521/tcp
lsnr_805 1526/tcp
Aniway, SQL*Net V2 keeps showing TNS-01106 message.

D. Morin
Re: Running SQL*Net V2 and Net8 together -> EVERYTHING OK [message #367566 is a reply to message #367565] Wed, 09 September 1998 07:08 Go to previous message
David Morin
Messages: 2
Registered: September 1998
Junior Member
Sorry,

I made a mistake in my listener configuration file
(listener.ora).

The files for each listener were containing a IPC
protocol address definition having the same key.

Now everything runs OK.
I start the listener with the commands :
lsnrctl start LSNR_734
lsnrctl start LSNR_805
Just notice that I comment the listener entry in the /etc/services file.

David Morin
Previous Topic: network load with large queries.
Next Topic: SQLNET/Listener Parameter Settings
Goto Forum:
  


Current Time: Sun Mar 03 16:27:01 CST 2024