本站中文解释
MAX_IDLE_BLOCKER_TIME参数表示等待任务被阻塞的最长时间，以秒为单位。如果等待任务被阻塞的时间超过该参数值，则Oracle将其视为已超时，生成一条错误消息。
正确设置MAX_IDLE_BLOCKER_TIME参数，应该按照特定的场景和工作负载，根据预测可能发生的错误进行调整。一般而言，在繁忙的数据库环境下，应将此参数设置为低值，如60秒，以确保在忙碌时期，数据库的并发状态能够得到及时的改善。同时，也不要设置的太低，可根据实际性能测得最佳值。
官方英文解释
MAX_IDLE_BLOCKER_TIME specifies the maximum number of minutes that a blocking 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. |
A session is considered to be a blocking session when it is holding resources required by other sessions. For example:
- The session is holding a lock required by another session.
- The session is a parallel operation and its consumer group, PDB, or database has either reached its maximum parallel server limit or has queued parallel operations.
- The session’s PDB or database instance is about to reach its
SESSIONSorPROCESSESlimit.
This parameter differs from the MAX_IDLE_TIME parameter in that MAX_IDLE_TIME applies to all sessions (blocking and non-blocking), whereas MAX_IDLE_BLOCKING_TIME applies only to blocking sessions. Therefore, in order for MAX_IDLE_BLOCKING_TIME to be effective, its limit must be less than the MAX_IDLE_TIME limit.
Note:
This parameter does not have an effect on parallel query processes, nor on SYS user sessions.
See Also:
“MAX_IDLE_TIME”
