981185 wrote:Real Oracle errors have both Error Number & Message like below
Forgive me if this is a dumb question, or has been answered before but I can't find this info. I'm not a heavy Solaris user by any means, having been mostly a windows guy.
We're running a Sunfire x4240 with a large Oracle database on it. We began having issues with messages about "Concurrent Session Limit".
981185 wrote:[oracle@localhost ~]$ oerr ora 18
It usually states the following:
ORA-00604: error occured at recursive SQL level 1
ORA-00018: maximum number of sessions exceeded
If you really can't access the database, you'd have to poke around and figure out which pfile or spfile the database is set to start with and look up the settings there. Since it doesn't sound like you're either a Solaris expert or an Oracle expert and since it sounds like you're not the person that set up the server, it's probably easier to simply ask whoever is acting as your DBA what the SESSIONS initialization parameter is set to.
sqlplus / as sysoper show parameter sessions
And is there any reason that disk access speeds could be a problem that could limit this?Is it possible? Sure. If, for example, you're using a normal three-tier application with a connection pool, the longer each individual session takes to complete its work the more sessions the connection pool needs to have open at any given point in time. If your disk I/O suddenly gets much slower, that could increase the total number of simultaneous sessions.
981185 wrote:find / -name sqlplus -ls 2>/dev/null
We don't have direct access to the DB, but do have access to a local root account. Is there any way to find out what that setting is without SQL access? And is there any reason that disk access speeds could be a problem that could limit this?