Hi,

That sounds to me like the Developer's don't have a clue what the problem is. You may very well find that the Developer's are not closing their connections in the application correctly, despite them saying they are. It may also depend on what sort of application it is (2-tier or 3-tier).

Paul

*********** ORIGINAL MESSAGE ***********

On 31/03/2006 at 3:43 PM Bouchard Michel \(Integic\) wrote:

DBA's
Other than the Idle Timeout setting in Profiles is there any
other setting that will set session status to SNIPED? We are having
problems with application Sessions not terminating - inactive sessions
over 28 hrs old and a few SNIPED sessions. To resolved the number of
Inactive sessions accumulating and exceeding the MAX Process number we
created a profile for this DB user with a IDLE Timeout of 2 hours - this
resulted in many SNIPED sessions that had to be manually cleared. So we
went back to the default profile (unlimited) this resolved most of the
SNIPED sessions but not all. In talking with the developers, they
mentioned that their application was tested on a Vanilla (default)
Oracle 9i (9.2.0.4) DB and that any session parameter setting other than
the default might be causing the connection release call to fail causing
these "Orphaned" sessions?

Thanks,

MB


--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these
terms:http://www.lazydba.com/legal.html




Oracle LazyDBA home page