Examine the parameters:
Users complain that their sessions for certain transactions hang. You investigate and discover that some users fail to complete their transactions, causing other transactions to wait on row-level locks.
Which two actions would you take to prevent this problem? (Choose two.)
To prevent users from blocking transactions and causing other transactions to wait on row-level locks, you can take the following actions: Use Database Resource Manager to automatically kill the sessions that are idle and are blocking other sessions. This helps in clearing idle sessions that are causing blocking issues. Additionally, decreasing the IDLE_TIME resource limit in the profiles assigned to blocking users can prevent users from being idle for too long, causing transactions to hang. By enforcing a shorter idle time, sessions that are not actively performing transactions are automatically terminated, thus reducing the chances of blocking other transactions. These measures together help ensure smoother transaction processing and avoid session hang issues.
think, DE 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. https://docs.oracle.com/database/121/SQLRF/statements_6012.htm#SQLRF01310
Agree with khan DE
i think DE
Agree DE
Agree.
I think DE