Overview
audit_log_max_size specifies the maximum size of audit logs that can be stored on a single OBServer node.
Privilege requirements
Query parameters
The
systenant and all user tenants can query this parameter using theSHOW PARAMETERSstatement or theGV$OB_PARAMETERSview.Modify parameters
Both the
systenant and user tenants can use theALTER SYSTEM SETstatement to modify this parameter.
Attributes
Attribute |
Description |
|---|---|
| Parameter type | Capacity |
| Default Value | 0M: Do not save audit logs. |
| Value range | [0M, +∞) |
| Modifiable | Yes, you can use the following methods:ALTER SYSTEM SETStatement modification. |
| Whether to restart the OBServer node for the change to take effect | No, the setting takes effect immediately. |
Usage instructions
Each time a new log file is generated during log archiving, the system checks whether log cleanup is required. The total log size is calculated separately for each OBServer directory. When the maximum total size is exceeded, files with the oldest retention period are cleaned up first.
Configuration example
Set the maximum size for audit logs saved on a single OBServer node to 4 GB.
obclient> ALTER SYSTEM SET audit_log_max_size='4G';