Tim and Dennis: Thanks for your responses:
SVRMGR> show parameter session NAME TYPE VALUE ----------------------------------- ------- ------------------------------ license_max_sessions integer 0 license_sessions_warning integer 0 session_cached_cursors integer 10 sessions integer 300 SVRMGR>
The SESSION parameter is hard-coded in our init.ora file to the value 300. The value for PROCESSES is set to 512. We have hard-coded our SESSION parameter because our number of licenses is set to 300 – however, my intuition tells me that the SESSION parameter should not be set based on our number of licenses. Can anybody confirm this for me?
I have also set up a TAR with Oracle Support, and they too say we need to increase the SESSION parameter (but we want to confirm it has no link to licenses).
Thanks again!
Sam Bootsma 416-415-5000 x4933
-----Original Message-----
I don't recall if the V$RESOURCE_LIMIT view existing in 7.3.4, but you might want to check. It is a better diagnostic point for that particular resource...
The "init.ora" parameter SESSIONS is related to the ORA-00018 error message, not any of the licensing parameters. Please use SHOW PARAMETER SESSIONS in SVRMGR to display its value. Generally, people let the value of the SESSIONS parameter default to 1.1 * PROCESSES, but you can increase it if you like.
Hope this helps...
|
- ORA-00018: maximum number of sessions exceeded Sam Bootsma
- Re: ORA-00018: maximum number of sessions exceeded Tim Gorman
- RE: ORA-00018: maximum number of sessions exceeded DENNIS WILLIAMS
- RE: ORA-00018: maximum number of sessions exceeded Sam Bootsma
- RE: ORA-00018: maximum number of sessions exceeded Hemant K Chitale