max connections to the database

[thanigai]

I mean maximum Cumulative no of processes...
Thanks.
Thanigaivasan.

[Shestakov]

select * from v$sysstat where name like '%logon%';

from last instance start.

[thanigai]

Hi Gurus,see I am getting this value...

SQL> select * from v$sysstat where name like '%LOGON%';

no rows selected
but........for
SQL> select * from v$license;

SESSIONS_MAX SESSIONS_WARNING SESSIONS_CURRENT SESSIONS_HIGHWATER USERS_MAX
------------ ---------------- ---------------- ------------------ ----------
0 0 233 376 0

SQL>
Thanks.
Thanigaivasan

[Shestakov]

Originally posted by thanigai

SQL> select * from v$sysstat where name like '%LOGON%';
no rows selected

but : select * from v$sysstat where name like '%logon%';
STATISTIC# NAME CLASS VALUE
--- ------------------- ----- ------
0 logons cumulative 1 5127282
1 logons current 1 20

[thanigai]

Yes Sir...I got it...
SQL> select * from v$sysstat where name like '%logon%';

STATISTIC# NAME
---------- ----------------------------------------------------------------
CLASS VALUE
---------- ----------
0 logons cumulative
1 21266

1 logons current
1 88
Thanks.I was typing LOGON instead of logon.
Thanigaivasan.

[jmodic]

Note however that those logon values in V$SYSSTAT are totaly meaningless! They are not incremented by 1 with each logon to the database as you might have expected. Sometimes with each new connection they are incremented by 1, sometimes by 9, somertimes by XYZ, and sometimes they get incremented even without any new connection taken place on the database!

Simply don't use this values for any of your reports or statistical decisions about your system, because they simply do not report the implied by their names....

[thanigai]

No no..It is not for the reports ...
Thanks.
Thanigaivasan.

[Shestakov]

Originally posted by jmodic
Sometimes with each new connection they are incremented by 1, sometimes by 9, somertimes by XYZ, and sometimes they get incremented even without any new connection taken place on the database!

U can calculate how many connections will be in next time.
# on connections = old_#_of_logon + current_#_1 + #_new_commections - #of_disconnect.

where current_#_1 --> is current logons in point when listener UPDATE SERVICES

--------

TO_CHAR( STATISTIC# NAME CLASS VALUE
-------- ---------- ----------------------------- ---------- ----------
15:50:27 0 logons cumulative 1 5155442
15:50:27 1 logons current 1 20
------------------------------------------------
15:50:31 0 logons cumulative 1 5155462
15:50:31 1 logons current 1 20
------------------------------------------------
15:50:36 0 logons cumulative 1 5155462
15:50:36 1 logons current 1 20


=======================================================================
record from listener.log file:

17-APR-2002 15:50:30 * service_update * lab * 0

This is time when listener update services.

[jmodic]

Shestakov,

Unfortunately I'm affraid you are on the wrong track. I think this incrementing thing has nothing to do with listener at all. I have stopped my listener and observed the number of "logons cumulative" in V$SYSSTAT and it keeps rising. So it is not connected to listener at all.

But I'm suspecting one other thing that might be causing this - Oracle's job queue processes. The number of cumulative logons in V$SYSSTAT increases by twice the number of JOB_QUEUE_PROCESSES every JOB_QUEUE_INTERVAL seconds even when there is no new connections to the database. When I started my database with JOB_QUEUE_PROCESSES = 0 the number of cumulative logons remains steady.

[Shestakov]

Jury.
In first thanks for information.
Then: in my database, and i saw this problem not only now, every time when
listener updated services in v$sysstat "cummlulative connections" increased too.
I didn't check JOB_QUEUE parameters and i can't say about it nothing.
May be this is "next source" for cummlulative connections.
But in this case oracle has "new" knowlege about mathimatics.

[Edited by Shestakov on 04-17-2002 at 05:22 PM]