jkstill_at_gmail.com wrote:
> If you get this to work, it would be nice if you could post the
> solution here.
>
> The DBMS_SESSION.IS_SESSION_ALIVE function requires an input of the
> form returned by the UNIQUE_SESSION_ID function.
>
> UNIQUE_SESSION_ID does not take any arguments - it returns a value for
> the current session only. The value returned does not appear to be
> available from v$session.
>
> The IS_SESSION_ALIVE function appears to be somewhat useless, at least
> from the documentation I have been able to find.
Ok, point is this:
We use oracle spatial. That, in turn, uses objects.
Which the application cannot put into temporary tables because temporary
tables can't have spatial columns and indexes.
So, to make this application multi-user-able we use normal tables
and include one column with the session-id. That, as you have correctly
assumed is the one UNIQUE_SESSION_ID returned for each session.
Now, sometimes applications crash, leaving data in the spatial
tables. So, I'm going to do a little cronjob which cleans out
those tables once per day, probably midnight.
That job first gets all session id's and then deletes the data of
all non-active sessions.
Lots of Greetings!
Volker, hoping that one day temporary tables will be up to that job.
Received on Fri Sep 09 2005 - 16:47:00 CDT
