transaction_read_only

Description

transaction_read_only specifies whether to allow only read-only transactions.

Privileges requirements

• Query variables

  • Global level

    The sys tenant and all user tenants can execute the SHOW VARIABLES statement or query the SYS.TENANT_VIRTUAL_GLOBAL_VARIABLE view (in Oracle-compatible mode) or the information_schema.GLOBAL_VARIABLES view (in MySQL-compatible mode) to query the value of a global system variable.

  • Session level

    The sys tenant and all user tenants can execute the SHOW VARIABLES statement or query the SYS.TENANT_VIRTUAL_SESSION_VARIABLE view (in Oracle-compatible mode) or the information_schema.SESSION_VARIABLES view (in MySQL-compatible mode) to query the value of a session variable.

• Modify variables

  • Global level

    • The sys tenant can directly modify the value of a global system variable.

    • MySQL-compatible tenants must have the SUPER or ALTER SYSTEM privilege to modify the value of a global system variable.

    • Oracle-compatible tenants must have the ALTER SYSTEM privilege to modify the value of a global system variable.

  • Session variables

    The sys tenant and all user tenants can directly modify the value of a session system variable in their respective tenant.

Attributes

Considerations

When transaction_read_only is set to True, DML statements cannot be executed.

Examples

Configure the system variable to allow the opening of non-read-only transactions.

• Session level

  obclient> SET transaction_read_only = False;
  

• Global level

  obclient> SET GLOBAL transaction_read_only = False;