I hope you are not using a 3-tier/n-tier architecture, in which case the OS user information available at database level will most probably be the user running the application in the midtier. You will have to make use of some Java classes to get the actual client information. This is true for Oracle Application server.
Thanks! amar Gints Plivna wrote:
One option would be to create on logon trigger, get current os user using sys_context('USERENV', 'OS_USER'), query v$session how many connections the same osuser has and raise exception if the connection number is too big. Gints Plivna http://www.gplivna.eu 2007/6/12, Krishnadas.Chathamath@xxxxxxxxxxxxxxxxxxHow can I restrict the no. of sessions connected based on osuser? Means I want to restrict the OS user connecting more than 3 concurrent sessions (3 sessions per OS users).-- //www.freelists.org/webpage/oracle-l
-- //www.freelists.org/webpage/oracle-l