ob_trx_idle_timeout

Description

ob_trx_idle_timeout specifies the idle timeout period of a transaction. A timeout error occurs if the execution interval between two consecutive statements in the transaction exceeds the value of this variable.

Limitations

• Query the variable

  • Global-level operation

    In the sys tenant or a user tenant, you can execute the SHOW VARIABLES statement to query the variable at the global level or query the SYS.TENANT_VIRTUAL_GLOBAL_VARIABLE view (in Oracle mode) or information_schema.GLOBAL_VARIABLES view (in MySQL mode) for the variable at the global level.

  • Session-level operation

    In the sys tenant or a user tenant, you can execute the SHOW VARIABLES statement to query the variable at the session level or query the SYS.TENANT_VIRTUAL_SESSION_VARIABLE view (in Oracle mode) or information_schema.SESSION_VARIABLES view (in MySQL mode) for the variable at the session level.

• Modify the variable

  • Global-level operation

    • In the sys tenant, you can directly change the value of the variable at the global level.

    • In a MySQL user tenant, you must have the SUPER or ALTER SYSTEM privilege to change the value of the variable at the global level.

    • In OceanBase Database V4.2.0 and later V4.x versions, you must have the ALTER SYSTEM privilege to change the value of the variable at the global level in an Oracle user tenant.

  • Session-level operation

    In the sys tenant or a user tenant, you can directly change the value of the variable at the session level for the current tenant.

Attributes

Examples

Set the idle timeout period of a transaction to 86,400,000,000 μs.

• Session-level operation

  obclient> SET ob_trx_idle_timeout =86400000000;
  

• Global-level operation

  obclient> SET GLOBAL ob_trx_idle_timeout =86400000000;