on 08-23-2017 5:01 PM
HI Ramachandran
There is a one workaround solution is there. we can create one profile and assign the database user
setting profile limit timeout of 120 mins
If a user exceeds the CONNECT_TIME
or IDLE_TIME
session resource limit, then the database rolls back the current transaction and ends the session. When the user process next issues a call, the database returns an error.
for more information follow the link
https://docs.oracle.com/cd/B19306_01/server.102/b14200/statements_6010.htm
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
7 | |
7 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.