Using both SID and Serial # from v$session worked for me when doing the
exact same thing you're saying.
"Epicentre Team A ANNECY" <djeanneret_at_epicentre.fr> wrote in message
news:aa5svg$qgp$1_at_wanadoo.fr...
> in fact, my problem is:
> User A insert many records in table A (Commit is necessary, it's a
> particular execution) !! when user stop application all data are deleted.
> (ok)
> User A insert many records in table A but session abort data are not
deleted
> (its a problem because we can't normally delete this records)
> => I want to scan in table A all records and look for the value of the
> stored session. if session doesn't exists i can delete record ect ...
>
> regards
> Denis
>
> "Knut Talman" <knut.talman_at_mytoys.de> wrote in message
> news:3CC6731B.6020209_at_mytoys.de...
> > Epicentre Team A ANNECY wrote:
> >
> > > Do you think this that the column "VALUE" of v$mystat is ok for use it
> on a
> > > primary key ?
> > > Why not use "SADDR" of v$session ?
> >
> >
> > Of course it is NOT ok. Neither VALUE nor SADDR should be used. You want
a
> > _primary_ key, not just a key. Primary means also unique but the data
you
> want
> > to use is not unique when you insert more than one record per session.
> > Why don't you use a sequence?
> >
> > Regards,
> >
> > Knut
> >
> >
> >
> >
>
>
>
Received on Wed Apr 24 2002 - 04:33:11 CDT
