ob_org_cluster_id

Description

ob_org_cluster_id specifies the cluster_id of the current session in OceanBase Database. The value is persisted to the transaction log.

Privilege requirements

• Query variables

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

• Modify variables

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

Attributes

Usage

Usually, you do not need to set the ob_org_cluster_id variable. When OceanBase Database generates logs (clog), it uses the default value. OMS can use the ob_org_cluster_id variable to implement data filtering. For more information about the data filtering feature of OMS, see Create a data migration project from a MySQL tenant of OceanBase Database to a MySQL tenant of OceanBase Database in the OceanBase Migration Service documentation.

For example, if the OMS obcdc component sets the cluster_id_black_list parameter to 2147473648 and the OBServer node sets the session variable to SET ob_org_cluster_id=2147473648;, then obcdc will filter out all data with a cluster_id of 2147473648.

Examples

Set the cluster_id of the current session in OceanBase Database to 2147473648.

obclient> SET ob_org_cluster_id = 2147473648;