10.2.10 Operands related to troubleshooting information
- 35) PDCLTPATH SQL-trace-file-and-error-log-file-output-destination-directory
<path-name><<%PDDIR%\spool\hubspool\foreign-server-name\>>- Specifies the output destination directory for the SQL trace file and error log file. For details on the SQL trace file and error log file, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
- 36) PDSQLTRACE SQL-trace-file-size
<unsigned integer>((0, 4096-2000000000)) (Bytes)- Specifies the size of the SQL trace file (units: bytes). The SQL trace file is output to the directory specified by the PDCLTPATH operand. If the PDCLTPATH operand is omitted, the SQL trace file is output to %PDDIR%\spool\hubspool\foreign-serve-name\.
- Operand rules
- If 0 is specified, the maximum file size is used.
- If this operand is omitted, an SQL trace is not output.
- The function and specification method of this operand are the same as those of the PDSQLTRACE operand of the client environment definition. For details on the PDSQLTRACE operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
- 37) PDSQLTEXTSIZE size-of-SQL-statements-to-be-output-to-SQL-trace-file
((4096-2000000))<<4096>>(bytes)- Specifies in bytes the size of the SQL statements to be output to the SQL trace file.
- If this operand is omitted when an access path is acquired, 2000000 is assumed.
- 38) PDSQLEXECTIME YES | NO
- Specifies whether to output SQL execution time to the SQL trace.
- YES: SQL execution time is output to the SQL trace.
- NO: SQL execution time is not output to the SQL trace.
- Notes
- If YES is specified for this operand, SQL execution time is output to a UAP statistical report in microseconds.
- An execution time exceeding 24 hours cannot be correctly output to the SQL trace.
- 39) PDUAPERLOG error-log-file-size
<unsigned integer>((0, 4096-65536)) <<4096>> (Bytes)- Specifies the error log file size (units: bytes). The error log file is output to the directory specified by the PDCLTPATH operand. If the PDCLTPATH operand is omitted, the error log file is output to %PDDIR%\spool\hubspool\foreign-serve-name\.
- Operand rule
- If 0 is specified, the maximum file size is used.
- The function and specification method of this operand are the same as those of the PDUAPERLOG operand of the client environment definition. For details on the PDUAPERLOG operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
- 40) PDPRMTRC YES | NO
- Specifies whether to output the ? parameter in the SQL trace.
- YES: Outputs the ? parameter in the SQL trace.
- NO: Does not output the ? parameter in the SQL trace.
- 41) PDPRMTRCSIZE maximum-data-size-of-?-parameter-information-inside-SQL-trace
<unsigned integer>((4-4096)) <<256>> (Bytes)- Specifies the maximum data size for the ? parameter information to be output in the SQL trace.
- Condition
- The PDPRMTRC operand must be set to YES.
- 42) PDTRCMODE ERR | NONE
- Specifies whether to output troubleshooting information (information with the file name pderrXXXX.trc) other than the SQL trace.
- ERR: Outputs troubleshooting information.
- NONE: Does not output troubleshooting information.
- Troubleshooting information is output to the directory specified by the PDCLTPATH operand. If the PDCLTPATH operand is omitted, troubleshooting information is output to %PDDIR%\spool\hubspool\foreign-serve-name\.
- 43) PDTRCPATH dynamic-SQL-trace-file-output-destination-directory
<pathname>- Specifies the output destination directory for a dynamic SQL trace file. You must specify this operand if you use the trace collection command (pdtrcmgr) to collect a dynamic SQL trace file.
- If you specify in pdtrcmgr the directory specified in this operand, SQL trace files are output to the directory specified in this operand during subsequent connections.
- For details on the trace collection command (pdtrcmgr), see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
- 44) PDUAPREPLVL [s][u][p][r] | a
- Specifies the output information type for the UAP statistical report. For details on the UAP statistical report facility, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
- s: Outputs information for each SQL statement. Also outputs SQL trace.
- u: Outputs information for each UAP.
- p: Outputs access path information.
- r: Outputs intermediate information during SQL execution.
- a: Outputs all information.
- Condition
- The PDCLTPATH operand must be specified.
- Operand rules
- If this operand is omitted, only the SQL trace is output.
- You can specify s, u, p, and r as a combination of one or more letters. If you specify supr, it is the same as specifying a. If any letter other than s or a is specified, no SQL trace is output.
- If you specify only PDUAPREPLVL and not s, u, p, r, or a, an error occurs.
- The function and specification method of this operand are the same as those of the PDUAPREPLVL operand of the client environment definition. For details on the PDUAPREPLVL operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
- 45) PDREPPATH UAP-statistical-report-output-destination-directory
<pathname>- Normally, the UAP statistical report is output to the directory specified by the PDCLTPATH operand. To output the UAP statistical report to a different directory, specify this operand.
- A file is created for each connection or disconnection under a file name pdHHMMSSmmm_xxx_*(1 or 2).trc.
- HHMMSSmmm: Connection time
- xxx: Connection serial number
- The function and specification method of this operand are the same as those of the PDREPPATH operand of the client environment definition. For details on the PDREPPATH operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.
- 46) PDSQLTRCOPENMODE CNCT | SQL
- Specifies the opening mode for the SQL trace file when collecting an SQL trace.
- CNCT:
- Outputs an SQL trace by opening or closing the SQL trace file for each connection or disconnection. Because this option results in smaller overhead than when each SQL statement is specified, it reduces the SQL trace output time. However, because information is written while the SQL trace is kept open, the SQL trace may not be correctly output if normal disconnection does not occur.
- SQL:
- Outputs an SQL trace by opening or closing the SQL trace file for each SQL statement (operation).
- Condition
- The PDREPPATH operand must be specified.
- 47) PDVWOPTMODE access-path-information-acquisition-mode
<unsigned integer>((0-2)) <<0>>- Specifies whether to collect access path information. The access path information collected here is used when executing the access path display utility. The access path information is output to %PDDIR%\spool\pdsqldump of the foreign HiRDB (the unit containing a single server or front-end server).
- 0:
- Does not collect access path information.
- 1:
- Collects access path information. However, the information of an SQL statement for which the SQL object is inside a buffer is not output.
- 2:
- Collects access path information. Even for an SQL statement with an SQL object inside a buffer, the SQL object is re-created and SQL information is output.
- The function and specification method of this operand are the same as those of the PDVWOPTMODE operand of the client environment definition. For details on the PDVWOPTMODE operand, see the HiRDB Version 8 UAP Development Guide. If the HiRDB version number of the foreign server is different, see the manual for the correct version.