NOARCHIVELOG

Purpose

Two log archiving modes are supported: ARCHIVELOG and NOARCHIVELOG. You can use the ALTER SYSTEM NOARCHIVELOG statement to disable ARCHIVELOG for a user tenant.

Limitations and considerations

If ongoing or paused log archiving jobs exist in the current tenant before you execute the ALTER SYSTEM NOARCHIVELOG statement to disable ARCHIVELOG for the tenant, the system automatically stops the archiving jobs after you disable ARCHIVELOG.

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 root user in MySQL mode.
• The default administrator is the SYS user in Oracle mode.

Syntax

ALTER SYSTEM NOARCHIVELOG [TENANT = {all | tenant_name[, tenant_name...]}] [DESCRIPTION [=] 'description'];

Parameters

Examples

Assume that the current cluster contains three tenants which are respectively named sys, mysql_tenant, and oracle_tenant, and that ARCHIVELOG has been enabled for the mysql_tenant and oracle_tenant user tenants. You can execute the following statement to disable ARCHIVELOG for the tenants.

• Disable ARCHIVELOG for the mysql_tenant tenant from the sys tenant.

  obclient [oceanbase]> ALTER SYSTEM NOARCHIVELOG TENANT = mysql_tenant;
  

• Disable ARCHIVELOG for the mysql_tenant and oracle_tenant tenants from the sys tenant.

  obclient [oceanbase]> ALTER SYSTEM NOARCHIVELOG TENANT = mysql_tenant, oracle_tenant;
  

• Disable ARCHIVELOG for all user tenants from the sys tenant.

  obclient [oceanbase]> ALTER SYSTEM NOARCHIVELOG TENANT = all;
  

• Disable ARCHIVELOG for the mysql_tenant or oracle_tenant tenant from the current tenant.

  obclient [oceanbase]> ALTER SYSTEM NOARCHIVELOG;
  

References

• SET LOG_ARCHIVE_DEST

• ARCHIVELOG

• Disable ARCHIVELOG