Purpose
You can use the CANCEL DELETE BACKUP statement to cancel ongoing cleanup jobs.
If you only want to cancel ongoing jobs, you can execute the CANCEL DELETE BACKUP statement. If you do not want canceled cleanup jobs to be scheduled again, you must first execute the DROP DELETE BACKUP POLICY statement to drop the corresponding automatic cleanup strategy and then execute the CANCEL DELETE BACKUP statement to cancel the cleanup jobs. For more information about the DROP DELETE BACKUP POLICY statement, see DELETE BACKUP.
Required privileges
You must execute this statement as the root user of the sys tenant (namely root@sys) or as the administrator of a user tenant.
- The default administrator is the
rootuser in MySQL mode. - The default administrator is the
SYSuser in Oracle mode.
Syntax
ALTER SYSTEM CANCEL DELETE BACKUP [TENANT [=] {tenant_name[, tenant_name]...} ];
Parameters
| Parameter | Description |
|---|---|
| tenant_name | The name of the tenant for which ongoing cleanup jobs are to be canceled when you execute this statement in the sys tenant. You can specify multiple tenant names separated with commas (,). If you do not specify the TENANT = tenant_name clause when you execute the statement in the sys tenant, the ongoing cleanup jobs of all user tenants are canceled.
NoticeYou must use the |
Examples
Drop the automatic cleanup strategy named
defaultfor themysql_tenanttenant from the sys tenant.obclient [oceanbase]> ALTER SYSTEM DROP DELETE BACKUP POLICY 'default' TENANT = mysql_tenant;Cancel the ongoing cleanup jobs of the
mysql_tenantandoracle_tenanttenants from the sys tenant.obclient [oceanbase]> ALTER SYSTEM CANCEL DELETE BACKUP TENANT mysql_tenant, oracle_tenant;Cancel the ongoing cleanups job of the
oracle_tenanttenant from the current tenant.obclient [SYS]> ALTER SYSTEM CANCEL DELETE BACKUP;