1.2.2 Files that consistently increase in size

Files that consistently increase in size when HiRDB is used are listed in the table below by information type.

In the table below, note that an asterisk (*) can be any alphanumeric character. Standard path names are given for files or directory names. These might vary by system.

The earliest version that supports a given file is listed as the supporting version. For example, if the supporting version is the initial version, then all subsequent versions also support that file.

The legend for the table below is as follows:
Y: The maximum size can be limited using options.
N: The maximum size cannot be limited.
S: HiRDB/Single Server
P: HiRDB/Parallel Server
DK: HiRDB/Developer's Kit
RT: HiRDB/Run Time
Organization of this subsection
(1) Simple dump
(2) Error information
(3) Tuning information
(4) Troubleshooting information
(5) Temporary files for index creation
(6) Temporary work files for operation commands
(7) Utility results files
(8) Temporary work file for utilities
(9) Trace information
(10) Statistical information

(1) Simple dump

No.File or directory nameDescriptionApprox. file sizeFile countCan the max. size be limited?Outputting softwareSupporting 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
NPInitial
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
NPInitial
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
NPInitial
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
NSInitial
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.
  • 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
NS, PInitial

(2) Error information

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting 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 KBUnlimitedNS, PInitial
2%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 bytesOne file per serverNS, P07-00
3%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)NS, PInitial
4%PDCLTPATH%\pderr1.trc, pderr2.trcThis is a client error information file. It is generated when a UAP is executed. Use the OS's del 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.YS, P, DK, RTInitial
5%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 del 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.YS, P, DK, RT07-01

(3) Tuning information

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting 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) x SQL statement count within transactionFor each transactionNS, P04-03

(4) Troubleshooting information

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting 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
UnlimitedNS, PInitial
2%PDDIR%\spool\save\*This is server process abnormal termination information (core 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 MBThree generations of looped files named shutdown-server-name[1-3]NS, PInitial
3%PDDIR%\spool\save\*.debThis 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.
  • 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 MBThree generations of looped files named shutdown-server-name[1-3].debNS, PInitial
4%PDDIR%\spool\save\command-name*.txtThis 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 IDNS, P06-02
5%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.oldNS, PInitial

(5) Temporary files for index creation

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting version
1directory-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 del 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 x index-storage-RDAREA-count (number of updated RDAREAs)NS, P05-06

(6) Temporary work files for operation commands

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting 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 x global-buffer-count, 512 bytes x RDAREA-count)One file for each command process IDYS, PInitial
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 x RDAREA-countOne file for each command process IDYS, PInitial
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 del command (or some other method) to manually delete the file while the pdbufls command is not executing.
16 bytes + 124 bytes x global-buffer-countOne file for each command process IDYS, PInitial
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 HiRDB/Parallel Server when the dictionary server and system manager are different nodes.
MAX(1,024 bytes x global-buffer-count, 512 bytes x RDAREA-count)One file for each command process IDYPInitial
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 del command (or some other method) to manually delete the file.
number-of-resources-to-export x 70 bytesOne file for each command process IDNS, P04-01

(7) Utility results files

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting version
1%TMP%\pdcp1*This is a pdcopy results file. It is generated when pdcopy is executed.
Use the OS's del command (or some other method) to manually delete the file.
700 KB x RDAREA-countOne file with a different file name each time for pdcopy with no -p optionYS, PInitial
2%TMP%\pdrs1*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 del command (or some other method) to manually delete the file.
Depends on rollback log sizeNumber of servers associated with the pdrstr target RDAREANS, PInitial
3%TMP%\pdrs2*This is a pdrstr results file. It is generated when pdrstr is executed.
Use the OS's del command (or some other method) to manually delete the file.
700 KB x RDAREA-countOne file with a different file name each time for pdrstr with no -p optionYS, PInitial
4%TMP%\pdrs4*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 del command (or some other method) to manually delete the file.
256 bytesOne (command execution node only)YS, PInitial
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 del 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 specifiedNS, P06-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 del 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 IDNS, P07-03

(8) Temporary work file for utilities

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting version
1%TMP%\pdcp3*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 del command (or some other method) to manually delete the file.
256 bytesOne (command execution node only)YS, PInitial
2%TMP%\pdcp4*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 del command (or some other method) to manually delete the file.
256 bytes x pdcopy-target-RDAREA-countNumber of servers associated with the target RDAREA of pdcopy + 2YS, PInitial
3%TMP%\pdrs5*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 del command (or some other method) to manually delete the file.
256 bytes x pdrstr-target-RDAREA-countNumber 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.
YS, PInitial
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 del 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 timeNS, PInitial
5%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 del command (or some other method) to manually delete the file.
This file is only used with HiRDB/Parallel Server.
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 dataNS, PInitial
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 del 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 timeNS, P03-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 del 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 x index-storage-RDAREA-count, with a different file name each time.NS, PInitial
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. Use the OS's del 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.NS, PInitial
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 del 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.NS, PInitial
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 del 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.NS, PInitial

(9) Trace information

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting version
1%PDCLTPATH%\pdsql1.trc, pdsql2.trcThis is SQL trace information. It is generated at SQL statement execution.
Use the OS's del command (or some other method) to manually delete the file.
Specified by client environment variable PDSQLTRACETwo files, between which output is cycled.YS, P, DK, RTInitial
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 del command (or some other method) to manually delete the file.
Specified by client environment variable PDSQLTRACETwo files created for each UAP process ID, between which output is cycled.YS, P, DK, RT07-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 del command (or some other method) to manually delete the file.
Specified by client environment variable PDSQLTRACETwo files each created for connected server name and client reception port number, between which output is cycled.YS, P, DK, RT08-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 del command (or some other method) to manually delete the file.
Specified by the pdtrcmgr -s commandTwo files each created for connected server name and client reception port number, between which output is cycled.YS, P, DK, RT08-00
5pdoletrc.txtThis is an OLEDB method trace. It is generated when an OLE DB provider is accessed.
Use the OS's del command (or some other method) to manually delete the file.
No size specificationOne fileNS, P, DK, RT05-06
6%PDJDBFILEDIR%\pdexc1.trc, pdexc2.trcThis is an exception trace log. It is generated when an exception occurs within a Type 4 JDBC driver.
Use the OS's del command (or some other method) to manually delete the file.
[Figure]180 x n x m [Figure]1,024[Figure] + 1 kilobytes
n: Specification in client environment variable PDJDBONMEMNUM (default is 1000)
m: Specification in client environment variable PDJDBFILEOUTNUM (default is 5)
Two files, between which output is cycled.YS, P, DK, RT08-00
7Specified 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 del command (or some other method) to manually delete the file.
[Figure]180 x n x m [Figure]1,024[Figure] 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 fileYS, P, DK, RT08-00
8%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 del command (or some other method) to manually delete the file.
Specified by pdtrcmgr -s commandTwo files created for each connection, between which output is cycled.YS, P, DK, RT06-00
9%PDCLTPATH%\pdrcnct1.trc, pdrcnct2.trcThis is a reconnection trace. It is generated when a connection is made automatically using the automatic connection function.
Use the OS's del command (or some other method) to manually delete the file.
Specified by client environment variable PDRCTRACETwo files, between which output is cycled.YS, P, DK, RT07-01
10%PDCLTPATH%\pddndpxxxx_yyy_1.trc, pddndpxxxx_yyy_2.trc
xxxx: Process ID
yyy: CONNECT number
This is a method trace for HiRDB.NET data providers. It is generated when a HiRDB.NET data provider method or property is called while connected to a server.
Use the OS's del command (or some other method) to manually delete the file.
Specified by client environment variable PDDNDPTRACETwo files created for each connection, between which output is cycled.YDK, RT08-05

(10) Statistical information

No.File or directory nameDescriptionApprox. file sizeFile countCan max. size be limited?Outputting softwareSupporting version
1%PDREPPATH%\pdHHMMSSmmm_XXX_1.trc,pdHHMMSSmmm_XXX_2.trc
HHMMSSmmm: CONNECT time
XXX: CONNECT number
This is a UAP statistical report. It is generated at SQL statement execution.
Use the OS's del command (or some other method) to manually delete the file.
Specified by client environment variable PDSQLTRACETwo files created for each connection, between which output is cycled.YS, P, DK, RT06-00
2%PDCLTPATH%\pdjsqlxxxxxxxx_ppppp_1.trc, pdjsqlxxxxxxxx_ppppp_2.trc
xxxxxxxx: Connected server name
ppppp: Client reception port number
This is a UAP statistical report (when a Type 4 JDBC driver is used). It is generated at SQL statement execution.
Use the OS's del command (or some other method) to manually delete the file.
Specified by client environment variable PDSQLTRACETwo files each created for the connected server name and client reception port number, between which output is cycled.YS, P, DK, RT08-00