6.4 Files that increase continuously over time when using the HADB server

This section describes files that increase continuously over time when using the HADB server.

Files that increase continuously over time when using the HADB server are created in the following directories:

Server directory
DB directory
Audit trail directory^#

#: This directory is required to use the audit trail facility.

Important: There is no upper limit to the number and file size of files that increase continuously over time. Therefore, with files of this nature, you need to take care to avoid a situation in which there is insufficient free space on the disk.

The following table shows the files in the server directory that increase continuously over time.

Table 6‒18: Files in server directory that increase continuously over time
No.	File name	File description	File deletion method
1	`$ADBDIR/spool/adbdumpYYYYMMDDhhmmss.server-process-process-id`^#1	HADB dump file	Deleted when the HADB server terminates normally. Deleted when the `adbinfosweep` command is executed.
2	`$ADBDIR/spool/adbdumperrorYYYYMMDDhhmmssSSSSSS_TTTTTTTTTTTTTTTTTTTT.server-process-process-id`^#1,#2	HADB dump file	Deleted when the `adbinfosweep` command is executed.

#1: YYYYMMDDhhmmss in the file name indicates the time when the file was generated.
#2: SSSSSS in the file name indicates the microsecond portion of the time when the HADB dump file was generated. TTTTTTTTTTTTTTTTTTTT indicates the thread ID of the real thread in which the HADB server's internal conflict error was detected.

The following table shows the files in the DB directory that increase continuously over time.

Table 6‒19: Files that DB directory that increase continuously over time
No.	File name	File description	File deletion method
1	`$DBDIR/SPOOL/core.server-process-process-id`^#1	Error information (core files)	Deleted when the `adbinfosweep` command is executed.
2	`$DBDIR/ADBWORK/xxxxx`^#2,#3	Temporary work files created during command execution^#4	Deleted when the command finished executing.

#1

If the adb_core_path operand in the server definition is specified, error information (core files) is output to the directory specified in the adb_core_path operand instead of to the $DBDIR/SPOOL directory.

#2

xxxxx in the file name is an arbitrary value.

#3

If the executed command omits the -w option, temporary work files are created in this directory. If the -w option is specified for the command, temporary work files are created in the directory specified in the -w option.

#4

Temporary work files are created when you execute the following commands:

adbimport command
adbidxrebuild command
adbmergechunk command
adbunarchivechunk command
adbreorgsystemdata command

The following table shows the files in the audit trail directory that increase continuously over time.

Table 6‒20: Files in audit trail directory that increase continuously over time
No.	File name	File description	File deletion method
1	`$AUDITDIR/adbaud-YYYYMMDD-hhmmss-nnn.aud`^#1,#2	Audit trail files^#3	Use the `cp` and `rm` OS commands to move the audit trail file to the audit trail storage directory. For details, see 12.3.1 Moving audit trail files (to audit trail storage directory).

#1

$AUDITDIR in the file name represents the audit trail directory. It is the path name specified in the adb_audit_log_path operand in the server definition.
YYYYMMDD and hhmmss in the file name are the date and time at which the audit trail file was renamed.
nnn in the file name is the millisecond component of the time at which the audit trail file was renamed.

#2

When using the multi-node function, the file name is $AUDITDIR/adbaud-YYYYMMDD-hhmmss-nnn-N.aud. N is the node number of the node that output the audit trail file.

#3

If 0 is specified for the adb_audit_log_max_num operand in the server definition or the adb_audit_log_max_num operand is omitted, there is no limit to the number of audit trail files that can be created.

To Page Top