lsnrctl on Win2003 Not Picking Up listener.ora file

  • Follow


Hi,

On 10g Win2003, listener.ora, sqlnet.ora (Which is blank), and
tnsnames.ora in $ORACLE_HOME/network/admin are fine, as they worked for
a couple of weeks, and the Oracle clients were able to access the
databases.

Now, some Win 2003 config work was done on the server, and the Oracle
clients cannot access the databases, although the DBs are up.
(ORA-12514: Listener cannot resolve SERVICE_NAME in description).

I executed 'lsrnctl' on the Win 2003 server, and, indeed, the
2 services for the databases were not available. I stopped and started
the listener, the service, etc.., but to no avail.

I set ORACLE_HOME, ORACLE_SID, and ORACLE_BASE correctly before
executing 'lsnrctl', but the latest 'listener.log' file was in
C:\WINDOWS\SYSTEM. Thus, no wonder the correct 'listener.ora' file was
not accessed.

However, given that ORACLE_HOME, etc.. were set correctly, should
Oracle not have used that listener.ora be resident in
$ORACLE_HOME/network/admin? Am I missing an environment variable or
something else. (The registry has ORACLE_HOM etc..crrectly also so
perhaps I did not need to set it on Win2003, but I did so to be sure).
Thanks,
SAP BASIS Consultant

0
Reply basis_consultant (53) 12/6/2004 11:22:14 PM

basis_consultant@hotmail.com wrote:
> Hi,
> 
> On 10g Win2003, listener.ora, sqlnet.ora (Which is blank), and
> tnsnames.ora in $ORACLE_HOME/network/admin are fine, as they worked for
> a couple of weeks, and the Oracle clients were able to access the
> databases.
> 
> Now, some Win 2003 config work was done on the server, and the Oracle
> clients cannot access the databases, although the DBs are up.
> (ORA-12514: Listener cannot resolve SERVICE_NAME in description).


To resolve that error, we need to know what service name the clients 
were actually requesting a connection to (ie, the contents of their 
tnsnames.ora) and the services the Listener is actually aware of (ie, a 
cut and paste of a lsnrctl services command) as well as the listener.ora 
you think should be being used.

Everything else is just speculation.

That your sqlnet.ora on the server is blank is a little bit of a worry. 
It should at the least have the names resolution method mentioned.

HJR



0
Reply hjr (2065) 12/7/2004 12:16:13 AM


Couple of things to check for,

1) Make sure $ORACLE_HOME/bin directory is listed first in your system
path. Open command prompt and type PATH.
2)  Make sure Oracle database/listener services logon user is part of
the ORA_DBA group. Local administrator is preffered. Also logon to the
machine as the same user while starting up Oracle services/processes.
3) As Howard pointed out.... sqlnet.ora being empty may be an issue.
Regards
/Rauf

0
Reply rs_arwar (312) 12/7/2004 10:12:34 AM

Hello,

Thanks to all those who responded. The Oracle DB/listener user is part
of the ORA_DBA group. $ORACLE_HOME/bin is first in the path.

I "solved" this problem by copying the listener.ora, sqlnet.ora and
tnsnames to C:\Windows\System32 from %ORACLE_HOME%\network\admin. I can
now access the databases from the remote clients. Thus, I do not see a
need to change any of the *.ora files, though I do not intend to have
Oracle access them from that directory indefinately.

I am still not sure why the listener is expecting these files in
C:\Windows\System32, and why it writes listener.log to that directory.

I set ORACLE_HOME and ORACLE_BASE correctly. Hence, I thought that the
listener would expect the *.ora files in %ORACLE_HOME%\network\admin.

I also set TNS_ADMIN to %ORACLE_HOME%\network\admin (I hardcoded the
path instead of putting %ORACLE_HOME%). Also, the variables are set
correctly in the registry.

Any information as to why Oracle keeps on expecting the *.ora files in
C:\Windows\System32 would be greatly appreciated.


Thanks,
SAP BASIS Consultant


Rauf Sarwar wrote:
> Couple of things to check for,
>
> 1) Make sure $ORACLE_HOME/bin directory is listed first in your
system
> path. Open command prompt and type PATH.
> 2)  Make sure Oracle database/listener services logon user is part of
> the ORA_DBA group. Local administrator is preffered. Also logon to
the
> machine as the same user while starting up Oracle services/processes.
> 3) As Howard pointed out.... sqlnet.ora being empty may be an issue.
> Regards
> /Rauf

0
Reply basis_consultant (53) 12/7/2004 9:51:21 PM

3 Replies
48 Views

(page loaded in 0.083 seconds)


Reply: