RE: ORA-00018 issues

From: Bobak, Mark <>
Date: Thu, 26 Feb 2009 13:56:54 -0500
Message-ID: <>

Simple test:

Reboot box, get back to ground zero.
Now, login, do:
Show parameter sessions
Select count(*) from v$session;

Do not give up your established connection! Now, have the consultant login/attempt to login.

If he gets the error, repeat the two commands above: Show parameter sessions
Select count(*) from v$session;

Compare the results. I'd expect the value of sessions is not going to change. (I'm pretty sure it can't chance w/o a bounce.) However, I'd be interested to know what difference you see in the count(*) from v$session query results.


-----Original Message-----

From: [] On Behalf Of Maureen English Sent: Thursday, February 26, 2009 1:26 PM To: oracle-l
Subject: ORA-00018 issues

We're experiencing a very strange problem...ORA-00018 errors.

Yes, I know that the error means 'maximum number of sessions exceeded', but that is not the case.

We are running Oracle on Solaris 10. We have a consultant who is working in this database, using a connection string like:


where is the machine and MYDB is the database SID.

We're trying to figure out if his attempts to connect are messing things up, or if there is something else going on.

If we reboot the machine, the problem disappears -- we can connect via sqlnet. Then the consultant tries his connection, gets the error and we can no longer connect via sqlnet.

Any suggestions for further troubleshooting? We're looking into java issues, as well as system/database issues, but so far nothing is obvious.

  • Maureen


-- Received on Thu Feb 26 2009 - 12:56:54 CST

Original text of this message