14.3 Deleting troubleshooting information (adbinfosweep command)
By executing the adbinfosweep command while the HADB server is stopped, you can delete troubleshooting information that was output by the HADB server.
The troubleshooting information that was output by the HADB server is not automatically deleted in the following cases:
-
The troubleshooting information was output when a server process was forcibly terminated.
-
The troubleshooting information was output when an internal conflict was detected in a server process.
If troubleshooting information continues to accumulate, the disk might run out of space. Therefore, execute the adbinfosweep command regularly to make sure that sufficient free space remains on the disk.
For details about the adbinfosweep command, see adbinfosweep (delete troubleshooting information) in the manual HADB Command Reference.
Execute the adbinfosweep command at the following times.
- When to execute the adbinfosweep command
-
If the HADB server terminated abnormally, first collect troubleshooting information by executing the adbinfoget command, and then execute the adbinfosweep command.
By executing the adbinfosweep command, you can delete the following types of troubleshooting information.
Types of troubleshooting information that can be deleted
-
Error information (core files)
-
$DBDIR/SPOOL/core.server-process-process-ID
-
path-defined-by-adb_core_path-operand-in-the-server-definition/core.server-process-process-ID
-
-
Server definition storage file
-
$ADBDIR/spool/.defrslt
-
-
HADB dump file
-
$ADBDIR/spool/adbdumpYYYYMMDDhhmmss.server-process-process-ID
YYYYMMDDhhmmss indicates the time when the file was generated.
-
$ADBDIR/spool/adbdumperrorYYYYMMDDhhmmssSSSSSS_TTTTTTTTTTTTTTTTTTTT.server-process-process-ID
YYYYMMDDhhmmssSSSSSS indicates the time when the file was generated.
TTTTTTTTTTTTTTTTTTTT indicates the thread ID of the real thread in which the HADB server's internal conflict error was detected.
-
- Important
-
Executing the adbinfosweep command might not delete troubleshooting information that was output by OS users other than the HADB administrator. If such unnecessary troubleshooting information is not deleted, a superuser can delete it by executing a command such as the operating system's rm command.