Re: How to check with multiple login?

1. can't use sessions_per_user as those users are application users, not database users. that FAT client uses the same common database account to make connection to database.
2. it's for security concern to have that requirement
3. expect to use "dbms_application_info" to set CLIENT_INFO with real application user id.

just wonder if the FAT client quits gracefully or accidentally, will the session/record in V$Session be cleaned up at once as it's what i assume for this mechanism. if not, this approach may not be working.

On Sep 22, 12:22 am, joel garry <joel-ga..._at_home.com> wrote:
> On Sep 21, 1:50 am, Mullin Yu <mullin..._at_gmail.com> wrote:
>
> > I have an application and those user accounts are application users,
> > not database users, i.e. userid and password stored on the user table
> > (e..g usr_user).
>
> > Now, I would like to check with any multiple login of users (same
> > machine or another user) and in case having, the application will warn
> > the user and not allow further login.
>
> > Currently, I think of checking with V$session. But then, may need to
> > set the value of user id when user logins to the application.
>
> > Is it possbile and any information can be shared?
>
> Why do you want to do this?  For most apps I've seen, people love
> being able to have multiple windows on their display.  Sometimes it
> can be a PITA if you have special serialization requirements, I have a
> job barcoding time-series app like that which is very touchy about
> commits, but even so, there are other session variables available to
> limit what really needs to be limited.
>
> Normally when I hear a request like this there is either some serious
> misapprehension of multiuser capabilities, or people are worried about
> the wrong security issues.
>
> jg
> --
> _at_home.com is bogus.
> "45 minutes 'til I go onstage at Moscone West L2 2014: Messed-Up Apps
> (3pm). Plz join me. " - Cary Millsap
Received on Tue Sep 21 2010 - 20:42:10 CDT