Note
- For V4.3.x, this parameter was introduced in V4.3.3.
- For V4.2.x, this parameter was introduced in V4.2.4.
Description
audit_log_max_size specifies the maximum amount of audit logs to retain on a single OBServer.
Applicability
This content applies only to OceanBase Database Enterprise Edition. OceanBase Database Community Edition does not support the auditing feature.
Privilege requirements
Query the parameter
The
systenant and all user tenants can query this parameter by using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify the parameter
The
systenant and user tenants can modify this parameter by using theALTER SYSTEM SETstatement.
Attributes
| Attribute | Description |
|---|---|
| Type | Capacity |
| Default value | 0M, which indicates that audit logs are not retained. |
| Value range | [0M, +∞) |
| Modifiable | Yes. You can use the ALTER SYSTEM SET statement to modify the parameter. |
| Effective upon OBServer node restart | No. The setting takes effect immediately. |
Usage
When a new log file is created during log archiving, the system checks whether log cleanup is needed. The total log size is calculated separately for each OBServer directory. When the maximum size is exceeded, older files are cleaned up first.
Example
Set the maximum amount of audit logs to retain on a single OBServer to 4G.
obclient> ALTER SYSTEM SET audit_log_max_size='4G';