Files that consistently increase in size

No.	File or directory name	Description	Approx. file size	File count	Can the max. size be limited?	Outputting software	Supporting version
1	$PDDIR/spool/pdfesdump/*	This is a simple dump file for a front-end server. It is generated when there is a pdfes process segmentation error or when an abort occurs. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several MB (undetermined)	Directory: The system loops through three generations of directories: $PDDIR/spool/pdfesdump, pdfesdump1, and pdfesdump2 File: Unlimited within directory	N	P	Initial
2	$PDDIR/spool/pddicdump/*	This is a simple dump file for a dictionary server. It is generated when there is a pddic process segmentation error, an abort occurs or the dictionary RDAREA is closed. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several MB (undetermined)	Directory: The system loops through three generations of directories: $PDDIR/spool/pddicdump, pddicdump1, pddicdump2 File: Unlimited within directory	N	P	Initial
3	$PDDIR/spool/pdbesdump/*	This is a simple dump file for a back-end server. It is generated when there is a pdbes process segmentation error, an abort occurs or the user RDAREA is closed. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several MB (undetermined)	Directory: The system loops through three generations of directories: $PDDIR/spool/pdbesdump, pdbesdump1, and pdbesdump2 File: Unlimited within directory	N	P	Initial
4	$PDDIR/spool/pdsdsdump/*	This is a simple dump file for a single server. It is generated when there is a pdsds process segmentation error, an abort occurs or the user RDAREA is closed. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several MB (undetermined)	Directory: The system loops through three generations of directories: $PDDIR/spool/pdsdsdump, pdsdsdump1, and pdsdsdump2 File: Unlimited within directory	N	S	Initial
5	$PDDIR/spool/pdsysdump/*	This is a simple dump file shared by the system. It is generated when a process that controls the HiRDB system terminates abnormally. When the server process is XDS, it is generated in the following cases: XDS is forcibly terminated by a pdxdsstop -f command. Group system switchover is performed by HA monitor's monswap command. HiRDB is forcibly terminated by a pdstop -f command. XDS terminates abnormally. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several MB to several dozen MB (undetermined)	Directory: The system loops through three generations of directories: $PDDIR/spool/pdsysdump, pdsysdump1, and pdsysdump2 File: Unlimited within directory	N	S, P	Initial

(2) Error information

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	$PDDIR/spool/pdlckinf/*	This is a deadlock timeout information file. It is generated when a lock error occurs. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several KB	Unlimited	N	S, P	Initial
2	$PDDIR/spool/pdtrninf/*	This is a transaction information file. It is generated using realtime SAN replication. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several KB	Unlimited	N	S, P	07-01
3	$PDDIR/spool/pdjnlinf/*	This is the status information file for the facility for monitoring the free space remaining for system log files. When the system log file free area falls to a value below the warning value, a file is generated. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Approx. 2,729 to 3,521 bytes	One file per server	N	S, P	07-00
4	$PDDIR/spool/pdjnlinf/errinf/*	This is a file for outputting system log error information. It is generated at reruns and when a system log read error occurs. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The file is also deleted when the pdstop command is executed (with no options, the -i option, or the dbdestroy option). The unit will shut down if there is insufficient space in $PDDIR.	The max. value is the value specified in the pd_log_max_data_size operand.	Number of log generations (finite number)	N	S, P	Initial
5	/tmp/pdskipsql_server-name_process-ID	This is the reflection SQL skip information file when the pdorend command is executed. It is generated when an SQL skip target error occurs in reflection processing when the pdorend command is executed. Use the OS's rm command (or some other method) to manually delete the file.	((400 + ((1,500 mapping-key-structure-column-count) 2)[+ 50 + ( (50 + (updated-member-count^#1 9) 80)]^#2) skipped-SQL-query-count) 1.2	Number of servers in RDAREA on which the pdorend command was run (for each process ID of the command and in server units)	N	S, P	07-01
6	$PDCLTPATH/pderr1.trc, pderr2.trc	This is a client error information file. It is generated when a UAP is executed. Use the OS's rm command (or some other method) to manually delete the file.	Value specified in client environment variable PDUAPERLOG (default is 4,096 bytes)	Two files, between which output is cycled.	Y	S, P, DK, RT	Initial
7	$PDCLTPATH/pderrxxxxx-1.trc, pderrxxxxx-2.trc (xxxxx: Process ID when UAP executes)	This is a client error information file (when an API (TX_ function) that conforms to X/Open is used). It is generated when a UAP is executed. Use the OS's rm command (or some other method) to manually delete the file.	Value specified in client environment variable PDUAPERLOG (default is 4,096 bytes)	Two files created for each UAP process ID, between which output is cycled.	Y	S, P, DK, RT	07-01

#1: Details about the number of updated members are as follows.; UPDATE SET (specifies members): Number of members to be updated; UPDATE ADD: 1; UPDATE DELETE: Number of members to be deleted

#2: When mvcelmwarn=ignore is specified in the control statement and a repetition column exists, the values in square brackets are added.; : Adds amounts for the number of repetition columns.

(3) Tuning information

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	$PDDIR/spool/pdsqldump/*	This is an access path information file. When 1 or greater is specified in the client environment variable PDVWOPTMODE, this file is generated when a SQL statement is executed (for each preprocessing). To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	(Several KB to several hundred KB) SQL statement count within transaction	For each transaction	N	S, P	04-03

(4) Troubleshooting information

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	$PDDIR/spool/save/abcode.*	This is server process abnormal termination information (primarily abort codes). It is generated when a server process terminates abnormally. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	In 32-bit mode: 40 bytes In 64-bit mode: 72 bytes	Unlimited	N	S, P	Initial
2	$PDDIR/spool/save/*	This is server process abnormal termination information (code file). It is generated when a server process terminates abnormally. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several MB to several dozen MB Note: In the following cases, the attached shared memory dump is also included in the core, so it can grow to several GB. In AIX, the EXTSHM environment variable is not specified. The Linux version is earlier than 5.2 and the HiRDB version is earlier than 08-04.	Three generations of looped files named shutdown-server-name[1-3] (If the name of the server is unknown, this might be a number rather than a name.)	N	S, P	Initial
3	$PDDIR/spool/save/*.deb	This is server process abnormal termination information. It is generated when a server process terminates abnormally. When the server process is XDS, it is generated in the following cases: XDS is forcibly terminated by a pdxdsstop -f command. Group system switchover is performed by HA monitor's monswap command. HiRDB is forcibly terminated by a pdstop -f command. XDS terminates abnormally. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several MB to several dozen MB	Three generations of looped files named shutdown-server-name[1-3].deb (If the name of the server is unknown, this might be a number rather than a name.)	N	S, P	Initial
4	$PDDIR/spool/save/*.ext.deb	This is server process abnormal termination information. It is generated when a server process terminates abnormally, and a backtrace is output. When the server process is XDS, it is generated in the following cases: XDS is forcibly terminated by a pdxdsstop -f command. Group system switchover is performed by HA monitor's monswap command. HiRDB is forcibly terminated by a pdstop -f command. XDS terminates abnormally. To delete automatically: Specify the following operands. pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several dozen KB	Three generations of looped files named shutdown-server-name[1-3].deb^# (If the name of the server is unknown, this might be a number rather than a name.)	N	S, P	09-03
5	$PDDIR/spool/save/command-name*.txt	This is troubleshooting information for the pdload, pdrorg, pdreclaim, and pdpgbfon commands. It is generated when a command times out. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several KB to several dozen KB (Varies with total number of HiRDB processes executed at that time and number of resources waiting for lock release)	One file for each command process ID	N	S, P	06-02
6	$PDDIR/spool/pdshmdump/*	This is a shared memory dump file. It is generated when a server process or unit terminates abnormally. To delete automatically: Specify the following operands: pd_spool_cleanup_interval pd_spool_cleanup_interval_level pd_spool_cleanup pd_spool_cleanup_level To delete manually: Execute the pdcspool command. The unit will shut down if there is insufficient space in $PDDIR.	Several hundred MB to several GB (about the same size as the shared memory segment whose attribute of the process that uses shared memory displayed with the pdls -d mem command is MANAGER)	The system loops through two generations of files: shmdump and shmdump.old	N	S, P	Initial

#: When the pdcancel -d command is used to forcibly terminate a server process, an instance of the following file is generated for each process that is canceled.; $PDDIR/spool/save/server-name.process-ID.cancel.ext.deb

(5) Special files for communication

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	/dev/HiRDB/pth/*	This is a special file for communication. It is generated at HiRDB startup, HiRDB server startup, command execution, and UAP connection. It is automatically deleted when the HiRDB server process terminates normally. Use the OS's rm command (or some other method) to manually delete the file (it can be deleted with all the HiRDB servers of the server machine stopped). The unit cannot start if there is insufficient space in $PDDIR.	0	Maximum of 196,605	N	S, P	Initial

(6) Temporary files for index creation

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	directory-specified-by-pd_plugin_ixmk_dir/index-name.RDAREA-name (if directory specified in pd_plugin_ixmk_dir)	This is a plug-in index information file. It is generated when an SQL statement is executed. It is automatically deleted when batch creation of the plug-in index terminates normally or when re-creation of the plug-in index is executed. Use the OS's rm command (or some other method) to manually delete the file.	See the Notes section in Delayed batch creation of a plug-in index in the HiRDB Version 9 System Operation Guide.	plugin count index storage RDAREA-count (number of updated RDAREAs)	N	S, P	05-06

(7) Temporary work files for operation commands

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	$PDDIR/tmp/CMr*	This is a temporary operation command file. It is generated when an operation command is executed. It is automatically deleted when operation command execution terminates.	MAX(1,024 bytes global-buffer-count, 512 bytes RDAREA-count)	One file for each command process ID	Y	S, P	Initial
2	$PDDIR/tmp/CMs*	This is a temporary operation command file. It is generated when an operation command is executed. It is automatically deleted when operation command execution terminates.	128 bytes RDAREA-count	One file for each command process ID	Y	S, P	Initial
3	$PDDIR/tmp/CMb*	This is a differential information file for the pdbufls command. It is generated when the pdbufls command (specifying -k sts or no option) is executed. It is automatically deleted when HiRDB starts. Use the OS's rm command (or some other method) to manually delete the file while the pdbufls command is not executing.	16 bytes + 124 bytes global-buffer-count	One file for each command process ID	Y	S, P	Initial
4	$PDDIR/tmp/pdcmd*	This is the operation command results file. It is generated when an operation command is executed. It is automatically deleted when command execution terminates. This file is only used by a HiRDB parallel server configuration when the dictionary server and system manager are different nodes.	MAX(1,024 bytes global buffer count, 512 bytes RDAREA count)	One file for each command process ID	Y	P	Initial
5	/tmp/pddefrev.exp.*(the pd_tmp_directory operand is ignored)	This is a temporary pddefrev command work file. It is generated when the pddefrev command is executed. It is automatically deleted when pddefrev command execution terminates. Use the OS's rm command (or some other method) to manually delete the file.	number of resources to export 70 bytes	One file for each command process ID	N	S, P	04-01
6	$PDDIR/spool/tmp/*	This is a temporary file for an operation command. It is generated when an operation command is executed. It is deleted automatically when the operation command execution terminates.	A maximum of 1,024 bytes	One file for each command process ID	N	S, P	09-04

(8) Utility results files

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	$TMPDIR/pdcp1, /tmp/pdcp1, directory-specified-by-the-p-option/pdcp1* (In 08-02 or later, this file is stored in the pd_tmp_directory directory if the pd_tmp_directory operand is specified.)	This is a pdcopy results file. It is generated when pdcopy is executed. Use the OS's rm command (or some other method) to manually delete the file.	3,500 (bytes) RDAREA count	One file with a different file name each time for pdcopy with no -p option	Y	S, P	Initial
2	$TMPDIR/pdrs1, directory-specified-by-the-w-option/pdrs1 (In 08-02 or later, this file is stored in the pd_tmp_directory directory if the pd_tmp_directory operand is specified.)	This is a temporary pdrstr results file (temporary file for storing rollback logs when recovering log specifications). It is generated when pdrstr is executed. It is deleted automatically when rollback terminates. Use the OS's rm command (or some other method) to manually delete the file.	Depends on rollback log size	Number of servers associated with the pdrstr target RDAREA	N	S, P	Initial
3	$TMPDIR/pdrs2, /tmp/pdrs2, directory-specified-by-the-p-option/pdrs2* (In 08-02 or later, this file is stored in the pd_tmp_directory directory if the pd_tmp_directory operand is specified.)	This is a pdrstr results file. It is generated when pdrstr is executed. Use the OS's rm command (or some other method) to manually delete the file.	3,500 (bytes) RDAREA count	One file with a different file name each time for pdrstr with no -p option	Y	S, P	Initial
4	$TMPDIR/pdrs4, /tmp/pdrs4 (In 08-02 or later, this file is stored in the pd_tmp_directory directory if the pd_tmp_directory operand is specified.)	This is a temporary pdrstr results file (temporary file for outputting messages to console). It is generated when pdrstr is executed. It is deleted automatically when pdrstr execution terminates. Use the OS's rm command (or some other method) to manually delete the file.	256 bytes	One (command execution node only)	Y	S, P	Initial
5	/tmp/REPORT* (in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a pdrbal results file. It is generated when pdrbal is executed. Use the OS's rm command (or some other method) to manually delete the file.	See 19.1.9 File sizes required for execution of the rebalancing utility (pdrbal).	One file with a different file name each time no report control statement is specified	N	S, P	06-00
6	/tmp/CONSTCK-REPORT-*(in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a pdconstck results file. It is generated when pdconstck starts executing. Use the OS's rm command (or some other method) to manually delete the file.	See 19.1.10 File sizes required for execution of the integrity check utility (pdconstck).	One file for each command process ID	N	S, P	07-03

(9) Temporary work file for utilities

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	$TMPDIR/pdcp3, /tmp/pdcp3 (In 08-02 or later, this file is stored in the pd_tmp_directory directory if the pd_tmp_directory operand is specified.)	This is a temporary pdcopy results file (for outputting messages to the console). It is generated when pdcopy is executed. It is automatically deleted when pdcopy execution terminates. Use the OS's rm command (or some other method) to manually delete the file.	256 bytes	One (command execution node only)	Y	S, P	Initial
2	$TMPDIR/pdcp4, /tmp/pdcp4 (In 08-02 or later, this file is stored in the pd_tmp_directory directory if the pd_tmp_directory operand is specified.)	This is a temporary pdcopy results file (for storing messages). It is generated when pdcopy execution starts. It is automatically deleted when pdcopy execution terminates. Use the OS's rm command (or some other method) to manually delete the file.	256 bytes pdcopy target RDAREA count	Number of servers associated with the target RDAREA of pdcopy + 2	Y	S, P	Initial
3	$TMPDIR/pdrs5, /tmp/pdrs5 (In 08-02 or later, this file is stored in the pd_tmp_directory directory if the pd_tmp_directory operand is specified.)	This is a temporary pdrstr results file (for storing messages). It is generated when pdrstr execution starts. It is automatically deleted when pdrstr execution terminates. Use the OS's rm command (or some other method) to manually delete the file.	256 bytes pdrstr target RDAREA count	Number of servers associated with the target RDAREA + 2. However, add an additional 1 when the number of target servers is two or more, or when you are inputting a log that exists somewhere other than the recovery target unit.	Y	S, P	Initial
4	/tmp/ERROR* (in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a results file for pdload input data storage information (error information file). It is generated when pdload is executed. Use the OS's rm command (or some other method) to manually delete the file.	See 19.1.1 File sizes required for the execution of the database load utility (pdload).	If no error operand is specified in the source statement, one file, with a different file name each time	N	S, P	Initial
5	/usr/tmp/, /var/tmp/, /tmp/*(in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a temporary file for creating the pdload error information file. It is generated when pdload is executed. Use the OS's rm command (or some other method) to manually delete the file. This file is only used with a HiRDB parallel server configuration.	See 19.1.1 File sizes required for the execution of the database load utility (pdload).	Number of servers that store the table to be loaded with data	N	S, P	Initial
6	/tmp/LOBMID* (in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a work file for pdload BLOB column loads. It is generated when pdload execution starts. Use the OS's rm command (or some other method) to manually delete the file.	See 19.1.1 File sizes required for the execution of the database load utility (pdload).	When something other than d is specified for the -k option, the lobmid statement is omitted, and a table that has a BLOB column is loaded with data, one file with a different file name each time	N	S, P	03-00
7	/tmp/INDEX, idxwork-control-statement-specification-directory/INDEX (in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is an index information file for pdload, pdrorg, and pdrbal. It is generated when pdload, pdrorg, or pdrbal executes. It is deleted automatically when index loading finishes. Use the OS's rm command (or some other method) to manually delete the file.	See the following: 19.1.1 File sizes required for the execution of the database load utility (pdload), 19.1.2 File sizes required for the execution of the database reorganization utility (pdrorg), 19.1.9 File sizes required for execution of the rebalancing utility (pdrbal)	When index batch creation mode is selected, the number of files is index count index storage RDAREA count, with a different file name each time.	N	S, P	Initial
8	/tmp/rs, sort-control-statement-specification-directory/rs (in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a sorting work file for pdload, pdrorg, and pdrbal. It is generated when pdload, pdrorg, or pdrbal executes. It is automatically deleted when index loading finishes or when the process terminates. Use the OS's rm command (or some other method) to manually delete the file.	See the following: 19.1.1 File sizes required for the execution of the database load utility (pdload), 19.1.2 File sizes required for the execution of the database reorganization utility (pdrorg), 19.1.9 File sizes required for execution of the rebalancing utility (pdrbal).	When index batch creation mode is selected, the number of files equals the index storage server count, with a different file name each time.	N	S, P	Initial
9	/tmp/.dbst.data, /tmp/.dbst.msg (in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a pddbst command temporary file. It is generated when pddbst execution starts. It is deleted automatically when pddbst execution terminates. Use the OS's rm command (or some other method) to manually delete the file.	See 19.1.4 File sizes required for the execution of the database condition analysis utility (pddbst).	One file for each process ID of the command.	N	S, P	Initial
10	/tmp/.syi, .syo, .uai, .uao, .sqi, .sqo, .pci, .pco, .soi, .soo, .doi, .doo, .bui, .buo, .fii, .fio, .dfi, .dfo, .ixi, .ixo, .isi, .iso, .cni, .cno, .qhi, .qho, .shi, .sho, .obi, .obo, .fsi, .fso, .hbi, .hbo, directory-specified-by--w-option/*** (in 08-02 or later, this file is stored under the pd_tmp_directory directory if the pd_tmp_directory operand is specified)	This is a temporary pdstedit command work file. It is generated when pdstedit execution starts. It is deleted automatically when pdstedit execution terminates. Use the OS's rm command (or some other method) to manually delete the file.	See 19.1.3 File sizes required for the execution of the statistics analysis utility(pdstedit).	One file for each process ID of the command and for each information item subject to analysis.	N	S, P	Initial

(10) Trace information

No.	File or directory name	Description	Approx. file size	File count	Can max. size be limited?	Outputting software	Supporting version
1	$PDCLTPATH/pdsql1.trc, pdsql2.trc	This is SQL trace information. It is generated at SQL statement execution. Use the OS's rm command (or some other method) to manually delete the file.	Specified by client environment variable PDSQLTRACE	Two files, between which output is cycled.	Y	S, P, DK, RT	Initial
2	$PDCLTPATH/pdsqlxxxxx-1.trc, pdsqlxxxxx-2.trc xxxxx: Process ID when UAP executes	This is SQL trace information (when using X/Open-compliant API (TX_ function)). It is generated at SQL statement execution. Use the OS's rm command (or some other method) to manually delete the file.	Specified by client environment variable PDSQLTRACE	Two files created for each UAP process ID, between which output is cycled.	Y	S, P, DK, RT	07-01
3	$PDCLTPATH/pdjsqlxxxxxxxx_ppppp_1.trc, pdjsqlxxxxxxxx_ppppp_2.trc xxxxxxxx: Connected server name ppppp: Client reception port number	This is SQL trace information (when using Type 4 JDBC driver). It is generated at SQL statement execution. Use the OS's rm command (or some other method) to manually delete the file.	Specified by client environment variable PDSQLTRACE	Two files each created for connected server name and client reception port number, between which output is cycled.	Y	S, P, DK, RT	08-00
4	$PDCLTPATH/pdjsqlxxxxxxxx_ppppp_1.trc, pdjsqlxxxxxxxx_ppppp_2.trc xxxxxxxx: Connected server name ppppp: Client reception port number	This is a dynamic SQL trace (when Type 4 JDBC driver is used). It is generated at SQL statement execution. Use the OS's rm command (or some other method) to manually delete the file.	Specified by the pdtrcmgr -s command	Two files each created for connected server name and client reception port number, between which output is cycled.	Y	S, P, DK, RT	08-00
5	$PDJDBFILEDIR/pdexc1.trc, pdexc2.trc	This is an exception trace log. It is generated when an exception occurs within a Type 4 JDBC driver. Use the OS's rm command (or some other method) to manually delete the file.	See Exception Trace Log in the HiRDB Version 9 UAP Development Guide.	Two files, between which output is cycled.	Y	S, P, DK, RT	08-00
6	Specified by user (in setLogWriter method of DriverManager class or setLogWriter method of DataSource interface)	This is a JDBC interface method trace. It is generated when an exception occurs within a Type 4 JDBC driver or when a Connection.close method is called. Use the OS's rm command (or some other method) to manually delete the file.	Specified in system property HiRDB_for_Java__FileSize or client environment variable PDJDBFILESIZE. If not specified, 180 n m 1,024 kilobytes n: Specification in user property TRC_NO, which is specified at connection (default is 500) m: Number of exceptions from connection to disconnection + 1	One file	Y	S, P, DK, RT	08-00
7	$PDTRCPATH/pdcHHMMSSmmm_XXX_1.trc, pdcHHMMSSmmm_XXX_2.trc HHMMSSmmm: CONNECT time XXX: CONNECT number	This is a dynamic SQL trace. It is generated at SQL statement execution. Use the OS's rm command (or some other method) to manually delete the file.	Specified by pdtrcmgr -s command	Two files created for each connection, between which output is cycled.	Y	S, P, DK, RT	06-00
8	$PDCLTPATH/pdrcnct1.trc, pdrcnct2.trc	This is a reconnection trace. It is generated when a connection is made automatically using the automatic connection function. Use the OS's rm command (or some other method) to manually delete the file.	Specified by client environment variable PDRCTRACE	Two files, between which output is cycled.	Y	S, P, DK, RT	07-01

1.3.2 Files that consistently increase in size

(1) Simple dump