DBAsupport.com Forums - Powered by vBulletin
Results 1 to 7 of 7

Thread: Max number of sessions exceeded

  1. #1
    Join Date
    Jan 2000
    Posts
    387

    Max number of sessions exceeded

    I have encountered the following errors and I could not even login to the database, I have to shutdown the database instead, anyway of solving this problem?

    SMON: following errors trapped and ignored:
    ORA-00604: error occurred at recursive SQL level 1
    ORA-00018: maximum number of sessions exceeded

    Could this have happened if my utl_file connections were not closed properly?

    Thanks!

  2. #2
    Join Date
    Apr 2003
    Location
    Hyderabad
    Posts
    40

    Max Sessions

    Increase the No Of Session Parameter.

  3. #3
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439

    Re: Max number of sessions exceeded

    Originally posted by mooks
    Could this have happened if my utl_file connections were not closed properly?
    No, defenitely not.
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  4. #4
    Join Date
    Jan 2000
    Posts
    387
    What can I do to prevent it from happening beside increasing the number of sessions? Or any alert or warnings?
    Last edited by mooks; 11-05-2003 at 04:09 AM.

  5. #5
    Join Date
    Jan 2000
    Posts
    387
    Any ways to track what could have caused it to happen? The recursive sql? There are no trace of the SQL in the alert log.

  6. #6
    Join Date
    Dec 2000
    Location
    Ljubljana, Slovenia
    Posts
    4,439
    Recursive (or any kind of) SQL statements have nothing to do with maximum number of sessions exceded! Oracle is not complaining about maximum naumber of cursors opened, it is complaining because there is too many sessions on your system!

    The reason could be that either
    - you have physical limit of max sessions in your init.ora too low
    or
    - something (firewall or something like that) is terminating the connections to the database in a "ungracefull"v maner and PMON is not able to clean those terminated sessions from the RDBMS
    or
    - something else ....????

    You should check regulary after your database has been up for some time if the number of database sessions is constantly increasing. If yes, you should check if there is many sessions with status KILLED that will not go away even after quite a long time since their last activity.

    Do you have MTS configuration?
    Jurij Modic
    ASCII a stupid question, get a stupid ANSI
    24 hours in a day .... 24 beer in a case .... coincidence?

  7. #7
    Join Date
    Jan 2000
    Posts
    387
    Hi

    There are no MTS configuration set. The sessions in the database is rather constant. It happened suddenly and after I shutdown the database, there are some processes which I cannot even kill (using kill -9), I have to reboot the whole server instead! Why is this so? Any ways to detect which process is causing it? Any logs?

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