Re: sqlnet.log file growing with this error.

OK, the error actually is:
Fatal OSN connect error 12545, connecting to:

 (DESCRIPTION=(ADDRESS=(PROTOCOL=beq)(PROGRAM=oracle)(ARGV0=oracle)(ARGS='(DESCR

 IPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))')(DETACH=NO))(CONNECT_DATA=(CID=(PRO

 GRAM=)(HOST=i3107ps3)(USER=insight))))

I would say that there's a program (but which?), that tries to connect to the database, using the beq protocol.
I do not see this protocol defined anywhere, on my server/client laptop, I do have beq-local
defined in tnsnames, as well as extproc in the listener. Could this be anything, that was installed on this particular server (e.g. OEM), but the instance was
renamed, moved, or something similar? I ask, because of the LOCAL=YES. On the listener log I find similar entries, with programs like BOOT.EXE (WebServer), SVRMGR23
(Also WebServer, installing developer packages), but the address bit always states TCP, never local

Michael Rothwell wrote:

> Frank van Bortel wrote:
> >
> > I only see TCP addressing - the error is about the BEQ protocol.
> > Is this the tnsnames file from the client you get the error log on?
> >
>
> Nupe, it's from the server. I cant figure out what in the world is
> happening.
>
> --
> Michael A. Rothwell
> Oracle DBA/Oracle Web Applications Developer
>
> Views expressed here are not those of my company
> No - Actually - Since I am independent, They are the views of my company.

--
Met vriendelijke groet,
kind regards,

Frank van Bortel
Technical consultant Oracle
V&L Informatica BV

Work                           Home
Postbus 545                    Hunzestraat 4
7500 AM Enschede               7555 WB Hengelo
(31)53.434.1500                (31)74.242.5046