Re: How to check with multiple login?
Date: Wed, 22 Sep 2010 09:13:47 +0200
Message-ID: <bd5fa$4c99acab$524ba3af$26951_at_cache6.tilbu1.nb.home.nl>
On 09/22/2010 03:42 AM, Mullin Yu wrote:
> 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
Sounds like security by obscurity. No more than two sessions...
>
> 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.
>
>
Don't top-post. People read from the top down.
Check SQLNET.EXPIRE_TIME:
"Setting a value greater than 0 ensures that connections are not left
open indefinitely, due to an abnormal client termination. If the probe
finds a terminated connection, or a connection that is no longer in use,
it returns an error, causing the server process to exit. This setting is
intended for the database server, which typically handles multiple
connections at any one time."
-- Regards, Frank van BortelReceived on Wed Sep 22 2010 - 02:13:47 CDT