In your database, you want to ensure that idle sessions that are blocking active are automatically terminated after a specified period of time. How would you accomplish this?

Metric thresholds in Oracle generate alerts or trigger advisory notifications when a threshold is exceeded but do not autonomously terminate sessions; they require external scripting or manual DBA action to act on the alert.

Database Resource Manager provides the MAX_IDLE_BLOCKER_TIME consumer group directive, which instructs Oracle to automatically kill any session that is idle and holding a lock that is blocking another active session for longer than the specified number of minutes. This is the only built-in Oracle feature that targets idle blocking sessions specifically, without affecting non-blocking idle sessions.

Resumable timeout defines how long a suspended resumable operation waits for a resource condition (such as out-of-space) to be resolved before raising an error; it has no mechanism to detect or terminate idle blocking sessions.

The IDLE_TIME resource limit in a user profile disconnects any session idle beyond the limit regardless of whether it is blocking another session, making it an indiscriminate control that does not specifically target blocking behavior.