Tenant Management

OceanBase Tenant Management

Resolve the installed OBD build, Community Edition deployment, and tenant before selecting a command. Confirm the requested operation against the installed command and component plugin.

This Skill version retains tenant workflows only for OceanBase Community Edition. Commercial OceanBase tenant operations and OBD-managed SeekDB HA are not supported by the current Skill version; do not translate either into the Community Edition tenant commands below.

Default Tenant Configuration

Creating a tenant still requires an explicit user request; cluster deployment alone never implies a business tenant. After creation is requested, do not ask for tenant settings the user omitted. Confirm the installed OBD defaults and omit those options so OBD owns the defaults for tenant name, mode, placement, replicas, Units, resources, IOPS, time zone, charset/collation, optimization, variables, network allowlist, and initial password. Explicit user values override only the corresponding defaults.

In the reviewed OBD baseline, the minimal create path produces tenant test, MySQL mode, all active zones, RANDOM primary zone, maximum currently allocatable tenant resources bounded by the selected servers, allowlist %, and an empty tenant password. Preserve that empty-password default when no password was supplied: do not ask for one, generate one, or set one after creation. Read the full tenant default and verification workflow before creating a tenant.

Apply the same no-prompt identity and password policy when building a physical primary/standby tenant pair. If the primary tenant must be created, apply each omitted value independently: the ordinary OBD defaults are tenant test and an empty root password. When creating its standby, omit --tenant-name unless the user supplied a standby name, so OBD uses the primary tenant name; omit --tenant-root-password unless the user supplied the primary tenant's root password, so the reviewed workflow tries the empty-password default. The required positional primary-tenant identity must still be resolved from actual primary-cluster state rather than guessed. These tenant-root defaults do not apply to the separate standbyro replication account, whose password must follow the installed OBD workflow. Read physical primary/standby tenants before creating or operating that relationship.

Shared Gates

Read the shared references required by the current stage:

• Before selecting syntax or packages, read product and capability resolution.
• Before any live controller/host/deployment query, SSH/SQL/API/network access, external action, or mutation, read the operation contract.
• Before declaring success, read the completion criteria.
• After a failure, timeout, interruption, or mixed result, read failure recovery and evidence before retrying or cleaning anything.
• Before dropping or removing a tenant, database resource object, backup/archive object, or generated artifact, read cleanup and ownership boundaries.

Route by Intent

Hard Boundaries

• Treat tenant drop, tenant restore, backup-task cancellation, restore-task cancellation, failover, and decouple as separate high-impact operations. Authorization for inspection, ordinary tenant creation, backup, restore, or switchover does not authorize cancellation. The V4.6.0/current reviewed restore path creates a new target tenant and refuses an existing target; do not invent overwrite semantics or turn restore authorization into permission to drop an existing tenant.
• Do not place tenant, standbyro, storage, decryption, KMS, or other credentials in reusable commands or reports.
• A tenant row or successful OBD exit is not completion. Apply the domain checks in the selected reference and verify an authenticated data-plane outcome when applicable.
• Do not infer a physical standby relationship from deployment names alone.

For cluster deployment, component lifecycle, or upgrades, use cluster-management. For benchmarks and functional tests, use testing-and-benchmark.