One more thought on this....
I would recommend, if it is possible in your environment, to let Oracle
handle the login restrictions and session killing.
Here is what you would do via Oracle:
- If you want Oracle to limit the sessions for you rather than via CF
code, a profile can be set up with concurrent sessions set to 1 (the
init.ora parameter resource_limit must be set to TRUE) which will prevent
an Oracle user from logging on more than once.
- If you want Oracle to automatically kill a session after so many minutes
of inactivity, you can set the idle_time parameter to the desired time in a
profile.
Profiles are defined by the Oracle DBA and assigned to Oracle accounts when
they are created. Profiles can contain information about resource usage
and password restrictions.
Hope this helps.
Janet.
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
