Lock a tenant

Lock a tenant

=========================

This topic describes how to lock a tenant. If you lock a tenant, the tenant cannot be accessed by users. Proceed with caution.

Precautions

• Make sure that you have the following permissions:

• Resource Permissions: Cluster Maintenance or Tenant Maintenance permission

• Menu Permissions: Permission on the Overview menu of Tenants

• Do not lock the sys tenant.

• You can lock a tenant only from the primary tenant.

After a tenant is locked, there are certain effects on its management, including, but not limited to the following:

• If the current tenant's MetaDB is used to host the Binlog Service, locking the tenant will make the Binlog Service unavailable.
• Tenant backup is not supported.
• The tenant service name cannot be created.
• Tenant specification cannot be modified.
• Tenant cannot be renamed.
• Tenant cannot be cloned.
• Resource isolation is not supported for tenants.
• Cannot execute routine primary/standby tenant switching.
• Primary and standby tenant disaster recovery switch cannot be performed.
• Cannot manage tenant users.
• Cannot manage tenant databases.

1. Log on to the OceanBase Cloud Platform (OCP) console.

2. In the left-side navigation pane, click Tenants.

3. In the Tenants list, click Lock in the Actions column of the target tenant.

   A dialog box appears, asking you to confirm whether to lock the tenant.

4. In the dialog box, click Lock.