The
iv_packetlog isn't included as part of the Online DB Tuning. Most Manager functions depend on the
iv_alert table. The i
v_packetlog table is often large, and tuning this
iv_packetlog table takes time to complete.
A long tune results in longer wait times for other Manager functions such as report generation during this time.
Owing to this reason, it's not available with Manager-based tuning but available via the
dbadmin.bat tool.
To tune the
iv_packetlog table, use the
dbadmin.bat utility:
- Stop the Manager service.
NOTE: This action prevents data change on incoming alerts.
- Note the disk use on the drive or folder where the database is installed.
- Note the size of the table data in the <Manager Database Install Dir.>\MySQL\data\lf - iv_packetlog.ibd file.
- Run dbadmin.bat, which purges data for iv_alert and iv_packet log.
Specify the requested data range and purge the logs from here.
- Run manual 'DB Tuning,' and again measure the readings from Steps 2 and 3.
NOTE: The
optimize table command frees the space. When you run the command, you see the message below:
Table does not support optimize, doing re-create + analyze instead
This message is informational and states that the unused space is freed after the command finishes running.