ORA-00018 - maximum number of sessions exceeded
Posted: Sun 13 Aug 2006 16:54
Hi,
We have an application that hits the Oracle database quite intensively. It hits the database about 5 times every second. After an hour, we get this message
CoreLab.Oracle.OracleException: ORA-00018: maximum number of sessions exceeded
at CoreLab.Oracle.OracleTransaction.Commit()
My best guess would be that Oracle has run out of sessions but this would mean that we aren't closing every Oracle transaction. We did check our code and we are pretty sure we close our connection after each transaction. I was wondering if CoreLabs is aware of any bugs that doesn't close the database connection.
Thank you
We have an application that hits the Oracle database quite intensively. It hits the database about 5 times every second. After an hour, we get this message
CoreLab.Oracle.OracleException: ORA-00018: maximum number of sessions exceeded
at CoreLab.Oracle.OracleTransaction.Commit()
My best guess would be that Oracle has run out of sessions but this would mean that we aren't closing every Oracle transaction. We did check our code and we are pretty sure we close our connection after each transaction. I was wondering if CoreLabs is aware of any bugs that doesn't close the database connection.
Thank you