Nikhil,

Looks to me that the connect string for the SQL*NET Ver 1.x does not contain
a valid SID name.
Is it by mistake getting set to '*' as the error seems to indicate?

Have you tried to connect to the database using the proper connect string
from a SQL*Plus session? (something like sqlplus
system/[Email Address Removed] What happens when you try that?

Regards,

- Kirti Deshpande
Verizon Information Services
http://www.superpages.com

> -----Original Message-----
> From: Nikhil Seth [SMTP:[Email Address Removed] Sent: Thursday, August 30, 2001 10:51 PM
> To: LazyDBA.com Discussion
> Subject: Listener Error - HELP NEEDED URGENT
>
> Hi Guys,
>
> There's this specific problem related to our application published in
> CITRX/working locally as well and having a database of Oracle 7.1.5.2.0 on
> SCO Openserver 5.0.5. The ORASRV.LOG file goes like this :
>
> 28-AUG-101 11:23:20 orasrv[ 603]: CONNECT request from 172.28.65.115
> 28-AUG-101 11:23:20 orasrv[ 603]: ERROR while processing request from
> host 172.28.65.115:
> 28-AUG-101 11:23:20 orasrv[ 603]: ERROR: SID lookup failure for '*'
> 28-AUG-101 11:23:37 orasrv[ 603]: CONNECT request from 172.28.65.115
> 28-AUG-101 11:23:37 orasrv[ 603]: ERROR while processing request from
> host 172.28.65.115:
> 28-AUG-101 11:23:37 orasrv[ 603]: ERROR: SID lookup failure for '*'
> 28-AUG-101 11:23:37 orasrv[ 603]: ERROR: unable to send return code to
> client (err=108)
>
> This error is continuous in the ORASRV.LOG file and is not allowing the
> users to LOGON to the database and work on the application.
>
> Has someone encountered this error in ORASRV.LOG..??? Any suggestions,
> views
> sharable are highly appreciated.
>
> TIA,
> Nikhil.
>
>
Oracle LazyDBA home page