Re: Listener problem

Hi Sybrand, thanks for Your suggestion much appreciated. I'm still confused since i've resetted the listener.log for about three weeks ago and it has now grown to :

"-rw-r--r-- 1 oracle dba 3902829 Aug 27 16:21 listener.log ". The one before that was as You said big about 20MB or:

"40904436 Aug 10 13:48 listener.990810log", but there was no such problem to logon and get connected to the database that we are experiencing now. I try too not letting logfiles grow to much.

Is the size of the log still a problem or is it something else ?

About the trace level admin i put that in yesterday to see if i would get some kind of
error message or something too get me closer to a solution of the problem.
So it has almost not been running with admin trace level more then the last 2
days.

How can I query how many users are allowed to logon to the database ?

Is there a license dependency within Oracle DBMS how many user that can connect to the database based on the purchase ?

Lennart Holmgren

Thanks again for any information that could bring some enlightment to this problem..

Regards
Lennart Holmgren

Sybrand Bakker wrote:

> Hi Lennart, I have a strange feeling this might be caused by the size
> of your listener.log file. This file is always appended too, the
> listener never resets it.I wouldn't describe this if not your
> trace_level for that listener would have been admin, which means
> logging almost everything.You can safely delete it, it will be
> automatically created again.BTW do not forget to change it in your
> listener.ora to off.A week ago I addressed a similar issue, the log
> file was running since March 98 and it's size was 90 Mb. Couldn't even
> view it. Hth, Sybrand Bakker, Oracle DBA
>
> Lennart Holmgren <lenhol_at_swipnet.se> wrote in message
> news:37C5539D.FF0D298_at_swipnet.se...Hello, i've lately got
> some problem with the LISTENER that i can't figure out whats
> causing it.
> It starts up fine with "nohup lsnrctl start&" and will run
> without any problem, but
> then while there's some pressure on the server, i.e more
> users wan't to log on,
> the LISTENER simply refuses to log any new user.
> Thoose already connected can continue to work as nothing has
> happened..
> I kill the LISTENER and restart with above command "nohup
> lsnrctl start&"
> and it will run to next freeze moment occur.
>
> I suspect that i'm hitting a roof but how can i verify
> that's the case ?
> And second what remedy action should i take ?
>
> Configuration
> Hardware: Compaq Proliant 5000, 3CPU, 728MB,
> Harddrives: Diskdrives set up as 2*2,1GB mirrored for OS,
> 2*2,1GB mirrored for logs,
> 3*4,3GB on RAD5 for DB and 2*2,1GB mirrorerd for
> applications i.e Oracle executables
> OS: SCO Openserver 5.0.4
> Database Oracle Server 7.3.4
>
> Info from svrmgrl:
>
> Oracle Server Manager Release 2.3.4.0.0 - Production
> Copyright (c) Oracle Corporation 1994, 1995. Med ensamrätt.
> Oracle7 Server Release 7.3.4.2.0 - Production
> With the distributed and parallel query options
> PL/SQL Release 2.3.4.2.0 - Production
>
> From listener: ( it's translated from swedish to english so
> bear with me if i got it wrong.)
>
> Copyright (c) Oracle Corporation 1994. All rights reserved.
>
> Connect to
> (ADDRESS=(COMMUNITY=tcp.world)(PROTOCOL=TCP)(Host=painrich)(Port=1
>
> 521))
> STATUS for LISTENER
> ------------------------
> Alias LISTENER
> Version TNSLSNR for SCO System V/386: Version
> 2.3.4.0.0 - Production
> Startdate 26-AUG-99 15:36:05
> Uptime 0 dagar 0 tim. 59 min. 20 sek
> Trace level admin
> Security OFF
> SNMP OFF
> Listener parameterfile /etc/listener.ora
> Listeners logfile
> /u/home/dba/app/oracle/product/7.3.4/network/log/listener.log
>
> Listeners tracefile
> /u/home/dba/app/oracle/product/7.3.4/network/trace/listene
> r.trc
> Overview of service...
> PROD has 1 servicehandle
> TEST has 1 servicehandle
> Command proceeded without errors
>
> TIA for all input that could shed some light what's going
> on....
>
> Lennart Holmgren
>
>
Received on Fri Aug 27 1999 - 09:59:20 CDT