Whenever you log in and issue a select statement, it would become a cursor. This is one of the tuning parameters should always be check. On the other hand, if there are going to be a number of people logging into your database and doing all kinds of query, the limit keeps going up. Here is one of the closely related thread on similar parameter setting. Check that out. The OPEN_CURSORS sets the max number of cursors that can be opened on your system at one point. When there are idle sessions, which had performed the querry operations and now have not been closed would contribute to that of holding the cursors count for no reason. So set some profile to the user sessions that would be closed if it were to be idle for a certain period of time. This would help in releasing the resources.

Relevent thread:
http://www.dbasupport.com/forums/sho...threadid=11524


Sam