On May 6, 10:34 am, yossarian <yossaria...@[EMAIL PROTECTED]
> wrote:
> Jason D. wrote:
> > I used Oracle 10g XE a lot last summer and will likely be using it
> > again this summer. My database is essentially for experiment purposes
> > and most connections to it are VIA ODBC. I noticed last year after so
> > many (like 20 perhaps? I'm not sure an exact number) sequential ODBC
> > connections (that is connect and disconnect, the connections were
> > *not* concurrent) XE would suddenly refuse more anymore connections
> > until I restarted the service (running Windows XP). I thought this
> > might be a limitation of XE but I can't find any do***entation on it
> > as a limitation, so that's making me think it might have been a
> > problem with my setup. Are there any suggestions on what might be
> > causing this?
>
> Keep the V$SESSION dictionary table monitored and you will find out that
> the ODBC app doesn't really close the database session.
>
> Y.
Thanks for the reply!
Interesting...is V$SESSION the same as V_$SESSION ? I found the latter
when logging on as "sys" under Views in the Object Browser but
couldn't find one without the underscore.
In any case, it shows 15 tuples all marked as "Active" under Status. I
log on with my ODBC app, and a new tuple pops up showing me with a new
SID, and application info it launched from, etc, but then when I log
off, the tuple (and SID) does indeed disappear. My application calls
SQLDisconnect() and SQLFreeHandle()
when quitting, is there something else I need to do to "close" the
session?
Thanks!
|
