Re: sqlnet.log,mni.log and fsl<sid>.log

The nmi.log is being written to at 30 sec intervals, with stuff like this:

Fatal NI Connect Error 12640, connecting to

(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=ORACLE)
(ARGVO=ORACLECCMLIVE)(ARGS='DESCRIPTION=(LOCAL=YES)
(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(CID=
(PROGRAM=c:\oracle\ora81\bin\dbsnmp.exe)(HOST=EC2KCS1)
(USER=SYSTEM))))

Err .. what does it all mean? How do I stop it before the whole universe fills up with it?

Cheers

James

In article <WAk9a.440$pK2.756_at_news.indigo.ie>, Telemachus <telemachus_at_ul ysseswillreturn.net> writes
>There's a reason they're filling up......
>"Sybrand Bakker" <gooiditweg_at_nospam.demon.nl> wrote in message
>news:sq9a6v4ip2pdknetmh50r18gais8nn1cq6_at_4ax.com...
>> On Tue, 4 Mar 2003 18:34:04 +0000, James Chappell
>> <james_at_rees-chappell.demon.co.uk> wrote:
>>
>> >These three files (sqlnet.log,mni.log and fsl<sid>.log - this latter
>> >something to do with Oracle FailSafe) on my 8.1.6 w2k server are filling
>> >up at a rate of knots.
>> >
>> >What causes them to be written to?
>> >Can I turn it off? How? Will it be a problem?
>> >
>> >Thanks
>>
>>
>> In the default setup sqlnet.log and nmi.log list errors and warnings
>> only. The obvious solution would be to read those files and to address
>> the problems noted, rather than to 'turn it off'.
>> So yes: 'turning it off' (which can be done by lowering the
>> trace_level as documented in the net8 manuals) will be a problem
>>
>>
>> Sybrand Bakker, Senior Oracle DBA
>>
>> To reply remove -verwijderdit from my e-mail address
>
>

-- 
James Chappell