9.2 and 10g on same machine, listener problem

Question

Hi,
i had a 10g db on a solaris server. then i installed a 9.2 database on this server. I know that i should use the 10g listener for 9.2 database.
But i cant manage to configure it correctly.
The 10g listener name is LISTENER and 9.2 listener name is TPRS.
what i did ? i opened netmgr and created a new listener named TPRS. added the database to it.(on the menu database services)
when i try to start TPRS i get the following error message
bash-2.05$ lsnrctl start TPRS
LSNRCTL for Solaris: Version 10.1.0.4.2 - Production on 08-JUN-2009 16:05:22
Copyright (c) 1991, 2004, Oracle. All rights reserved.
Starting /oracleAS/app/oracle/product/10.1.2.0.2/infra/bin/tnslsnr: please wait...
TNSLSNR for Solaris: Version 10.1.0.4.2 - Production
System parameter file is /oracleAS/app/oracle/product/10.1.2.0.2/infra/network/admin/listener.ora
Log messages written to /oracleAS/app/oracle/product/10.1.2.0.2/infra/network/log/tprs.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sun3.tuprasnet.local)(PORT=1522)))
TNS-01201: Listener cannot find executable /oracleAS/TPRS/app/oracle/product/9.2.0.1.0/bin/oracle for SID TPRS
Listener failed to start. See the error message(s) above...
The directory "/oracleAS/TPRS/app/oracle/product/9.2.0.1.0/bin/" exists , and oracle executable is under it. also /oracleAS/TPRS/app/oracle/product/9.2.0.1.0 is the oracle home for 9.2 database.
The listener.ora file of 10g is like that:
SID_LIST_TPRS =
(SID_LIST =
(SID_DESC =
(GLOBAL_DBNAME = TPRS)
(ORACLE_HOME = /oracleAS/TPRS/app/oracle/product/9.2.0.1.0)
(SID_NAME = TPRS)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /oracleAS/app/oracle/product/10.1.2.0.2/infra)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = iasdb.tuprasnet.local)
(ORACLE_HOME = /oracleAS/app/oracle/product/10.1.2.0.2/infra)
(SID_NAME = IASDB)
TPRS =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = sun3.tuprasnet.local)(PORT = 1522))
LISTENER =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = sun3.tuprasnet.local)(PORT = 1521))
what am i missing?
Thanks in advance,
mehmet

Answer 1

We (Gerwin and I) had a small discussion about the problem at hand.
The discussion is overlooking the obvious
TNSLSNR for Solaris: Version 10.1.0.4.2 - Production
System parameter file is /oracleAS/app/oracle/product/10.1.2.0.2/infra/network/admin/listener.ora
Log messages written to /oracleAS/app/oracle/product/10.1.2.0.2/infra/network/log/tprs.log
Listening on: (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=sun3.tuprasnet.local)(PORT=1522)))
TNS-01201: Listener cannot find executable /oracleAS/TPRS/app/oracle/product/9.2.0.1.0/bin/oracle for SID TPRSSo the Solaris user that starts the listener HAS NO ACCESS rights to the directory path and/or the executables (lsnrctl / tnslsnr).
[oracle@srv01-18-102 bin]$ ps -ef|grep tns
oracle   11967     1  0 Jun07 ?        00:00:53 /u01/app/oracle/product/11.1.0/dbhome_1/bin/tnslsnr LISTENER -inherit
oracle   28694 17439  0 17:49 pts/0    00:00:00 grep tnsYou can choose for a "more than one listener" solution or "only one listener". Whatever you do the unix user that starts the oracle, listener executables have to be the same OR sicky bits have to exist on the executables (so the user is allowed to start the executables and access the memory realms as if it was the actual owner).
The moment you don't use the defaults - aka "LISTENER" or a non default port (1521), you will have to define this via the database parameter
LOCAL_LISTENER
SQL> conn / as sysdba
SQL> show parameter local_listener
NAME                                 TYPE        VALUE
local_listener                       string
SQL> ALTER system SET LOCAL_LISTENER=
        "(ADDRESS=(PROTOCOL=TCP)(HOST=sun3.tuprasnet.local)(PORT=1522))"
        scope=BOTH;
System altered.
SQL> show parameter local_listener
NAME                                 TYPE        VALUE
local_listener                       string      (ADDRESS=(PROTOCOL=TCP)(HOST=sun3.tuprasnet.local)(PORT=1522))Now the database "knows" that it has to register itself against "sun3.tuprasnet.local" and will be serviced via port 1522.
After been set on database level, the "LOCAL_LISTENER" value can be resolved via the string itself or (*most common way of doing it is using a tnsalias*) is resolved via the tnsnames.ora file (the string given in LOCAL_LISTENER is an tns ALIAS).
If you use ONE listener, then databases can register themselves against SQL*Net compatible listeners. So you don't have to use a 9i listener for a 9i database. A 10g database is also allowed.
If I use a ONE listener solution, then I normally pick the listener from the highest database version and let all database versions use this listener.
The post given here (http://www.liberidu.com/blog/?p=116): "Registering non-default XMLDB HTTP/WebDAV and FTP ports on a non-default Oracle Listener port" describes a use case which is even more "extreem" regarding shared server functionality, based on TWO listeners and NON-DEFAULT PORT addressing, based on an Oracle 9 and Oracle 10 environment on the same machine.
HTH
M.
Edited by: Marco Gralike on Jun 8, 2009 6:01 PM