Note
For V4.4.0, this parameter is available starting with V4.4.0.
Description
load_data_diagnosis_log_max_size specifies the size of a single diagnostic log file.
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.
Attributes
| Attribute | Description |
|---|---|
| Type | Capacity |
| Default value | 256M |
| 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. |
Considerations
Audit records are continuously appended to the diagnosis.log file. When the size of the diagnosis.log file reaches load_data_diagnosis_log_max_size, a new file is automatically generated and the records continue to be written to it.
Examples
Set the size of a single diagnostic log file to 128M.
obclient> ALTER SYSTEM SET load_data_diagnosis_log_max_size = '128M';
References
- For information about how to set the compression algorithm for diagnostic logs, see load_data_diagnosis_log_compression.
- For information about how to enable error diagnostics during the import of external tables, see LOAD DATA (MySQL-compatible mode) and LOAD DATA (Oracle-compatible mode).