https://docs.oracle.com/en/database/oracle/oracle-database/12.2/refrn/MAX_IDLE_TIME.html#GUID-9E26A81D-D99E-4EA8-88DE-77AF68482A20
1.179 MAX_IDLE_TIME
MAX_IDLE_TIME specifies the maximum number of minutes that a session can be idle. After that point, the session is automatically terminated.
| Property | Description |
|---|---|
|
Parameter type |
Integer |
|
Default value |
0 |
|
Modifiable |
|
|
Modifiable in a PDB |
Yes |
|
Range of values |
0 to the maximum integer. The value of 0 indicates that there is no limit. |
|
Basic |
No |
|
Oracle RAC |
Different instances can use different values. |
https://docs.oracle.com/en/database/oracle/oracle-database/18/sqlrf/CREATE-PROFILE.html#GUID-ABC7AE4D-64A8-4EA9-857D-BEF7300B64C3
IDLE_TIME
ALTER PROFILE app_user LIMIT IDLE_TIME DEFAULT;
Oracle Database enforces resource limits in the following ways:
-
If a user exceeds the
CONNECT_TIMEorIDLE_TIMEsession 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. -
If a user attempts to perform an operation that exceeds the limit for other session resources, then the database aborts the operation, rolls back the current statement, and immediately returns an error. The user can then commit or roll back the current transaction, and must then end the session.
-
If a user attempts to perform an operation that exceeds the limit for a single call, then the database aborts the operation, rolls back the current statement, and returns an error, leaving the current transaction intact.