DBAsupport.com Forums - Powered by vBulletin
Page 2 of 2 FirstFirst 12
Results 11 to 20 of 20

Thread: max connections to the database

  1. #11
    Join Date
    Oct 2000
    Location
    Charlotte, USA
    Posts
    330
    I mean maximum Cumulative no of processes...
    Thanks.
    Thanigaivasan.

  2. #12
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    select * from v$sysstat where name like '%logon%';

    from last instance start.

  3. #13
    Join Date
    Oct 2000
    Location
    Charlotte, USA
    Posts
    330
    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

  4. #14
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    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

  5. #15
    Join Date
    Oct 2000
    Location
    Charlotte, USA
    Posts
    330
    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.


  6. #16
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    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....
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  7. #17
    Join Date
    Oct 2000
    Location
    Charlotte, USA
    Posts
    330
    No no..It is not for the reports ...
    Thanks.
    Thanigaivasan.

  8. #18
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    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.



  9. #19
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    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.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  10. #20
    Join Date
    Sep 2001
    Location
    NJ, USA
    Posts
    1,287
    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]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  


Click Here to Expand Forum to Full Width