Idle time is not the problem.

From: Henk Hultink <hhu_at_stopspam.stoas.nl>
Date: Mon, 8 Jul 2002 13:43:03 +0200
Message-ID: <3d297ad1@news.wau.nl>

Hi,

The idle time is not the problem; it is set to unlimited. The alertlogs do not show any errors either. I am not surprised, because both databases are working fine, and they can be accessed on the server as well as remote.

However in the map \oracle\ora81\network\log is a file that grows at high speed, like 200 kb in 1 hour: NMI.LOG
The same error is logged every 30 seconds:

---

Fatal NI connect error 12560, connecting to:

(DESCRIPTION=(ADDRESS=(PROTOCOL=BEQ)(PROGRAM=ORACLE)(ARGV0=ORACLEimsvd)(ARGS ='(DESCRIPTION=(LOCAL=YES)(ADDRESS=(PROTOCOL=beq)))'))(CONNECT_DATA=(CID=(PR OGRAM=D:\oracle\ora81\bin\dbsnmp.exe)(HOST=BEHEERSERVER)(USER=SYSTEM))))

  VERSION INFORMATION:
 TNS for 32-bit Windows: Version 8.1.7.0.0 - Production  Oracle Bequeath NT Protocol Adapter for 32-bit Windows: Version 8.1.7.0.0 - Production
 Windows NT TCP/IP NT Protocol Adapter for 32-bit Windows: Version 8.1.7.0.0 - Production
  Time: 08-JUL-2002 13:29:37
  Tracing not turned on.
  Tns error struct:
    nr err code: 0
    ns main err code: 12560
    TNS-12560: TNS:protocol adapter error     ns secondary err code: 0
    nt main err code: 530
    TNS-00530: Protocol adapter error
    nt secondary err code: 0
    nt OS err code: 0

And in the same folder the LISTENER.LOG logs an error every 5 minutes:

08-JUL-2002 13:30:51 * 12502
TNS-12502: TNS:listener received no CONNECT_DATA from client

I don't know which service uses the BEQUEATH protocol; I even tried to change the local connection to use IP as well, and it is still working fine, but it's still loggin as well.

"Rauf Sarwar" <rsarwar_at_ifsna.com> wrote in message news:c2d690f2.0207040844.64ea70e4_at_posting.google.com...
> For second part...
> There is a parameter called IDLE_TIME defined under your user defined
> profile or DEFAULT profile. If the profile IDLE_TIME value is set to
> e.g. 60 (Minutes) and user has been assigned that profile, then user
> will get automatically disconnected from the database after 60 minutes
> of inactivity...Resolution: increase the IDLE_TIME value. To
> do..Connect as SYS@<YourDB>
>
> SQL> select p.profile, p.resource_name, p.limit
> from dba_profiles p, dba_users u
> where p.profile = u.profile
> and p.resource_name = 'IDLE_TIME'
> and u.username = '&UserName';
> SQL> ALTER PROFILE <profile name> LIMIT IDLE_TIME <New limit in
> minutes>;
>
> HTH
> //Rauf Sarwar
Received on Mon Jul 08 2002 - 06:43:03 CDT