2.2.13 Operands related to the facility for output of extended SQL error information
- 66) pd_uap_exerror_log_use = AUTO | YES | NO
- Select AUTO, YES, or NO to specify whether to apply the facility for output of extended SQL error information. For details about this facility, see the HiRDB Version 9 UAP Development Guide.
- AUTO:
- Applies the facility for output of extended SQL error information. SQL error information is output in a client error log file and an SQL error report file.
- The date and time when error information was output to the SQL error report file and the start, end, and execution times of SQL are displayed in seconds.
- YES:
- Applies the facility for output of extended SQL error information. SQL error information is output in a client error log file and an SQL error report file.
- The date and time when error information was output to the SQL error report file, and the start, end, and execution times of SQL are displayed in microseconds.
- NO:
- The facility for output of extended SQL error information is not applied.
- Specification guideline
- If you manage SQL error information centrally, or if you output the SQL statements causing an error along with the parameter information, we recommend that you specify YES.
- Relationship to client environment definition
- The value of this operand can be changed for each client. To change the operand for a client, specify the PDUAPEXERLOGUSE operand in the client environment definition. If both this operand and the PDUAPEXERLOGUSE operand in the client environment definition are specified, the PDUAPEXERLOGUSE operand takes precedence.
- For details about the PDUAPEXERLOGUSE operand, see the HiRDB Version 9 UAP Development Guide.
- Effects on individual estimation formulas
- If the value of the pd_uap_exerror_log_use operand is changed, the following estimation formulas are affected:
- HiRDB Version 9 Installation and Design Guide:
- Determining the size of the memory required to use the facility for output of extended SQL error information under Estimating the memory size required for a HiRDB single server configuration
- Determining the size of the memory required to use the facility for output of extended SQL error information under Estimating the memory size required for a HiRDB parallel server configuration
- 67) pd_uap_exerror_log_dir = SQL-error-report-file-storage-directory
- ~<path name of up to 255 characters> <<$PDDIR/spool/pduaperr>>
- Specifies an absolute path name for the directory in which to store SQL error report files.
- Two SQL error report files are created in the specified directory. Their file names are pduaperrlog1 and pduaperrlog2.
- For details about the facility to output extended SQL error information, see the HiRDB Version 9 UAP Development Guide.
- 68) pd_uap_exerror_log_size = SQL-error-report-file-maximum-size
- ~<unsigned integer>((2048-2147483647))<<10000000>> (bytes)
- Specifies the maximum size of an SQL error report file. The value specified by this operand applies to each of the two SQL error report files that are to be created. When the volume of data that is output to an SQL error report file exceeds the value specified by this operand, the output destination is switched to the other file. The two files are used alternately as this process is repeated. If the volume of the SQL error information that is output at one time exceeds the value specified by this operand, the first through the [specified value - 1]-th bytes (up to the 999,999th byte if 1000000 is specified for this operand) of SQL error information is output. In this case, a hash mark (#) is added to the end of the SQL error information.
- Specification guidelines
- Determine the value to be specified for this operand by taking into consideration the volume of SQL error information that you want to retain. You can use the following computation formula:
- (A + B)
volume-to-be-retained - A = 1100 + SQL-statement-size (bytes)
This is the size of each piece of SQL error information, excluding the parameter information output size. If an SQL statement contains a comment or the description of SQL optimization specification, the size of the comment or SQL optimization specification also must be included in the SQL statement size. For details about comments and SQL optimization specification, see the manual HiRDB Version 9 SQL Reference.
- B = (
pd_uap_exerror_log_param_size-operand-value
16
+ 1)
89
parameter-count
This is the parameter information output size.
- 69) pd_uap_exerror_log_param_size = maximum-data-size-of-parameter-information-to-be-output-to-client-error-log-file-and-SQL-error-report-file
- ~<unsigned integer>((0-32008))<<0>> (bytes)
- Specifies the maximum data size for the parameter information to be output to a client error log file and an SQL error report file.
- When 1 or a value greater than 1 is specified
Parameter information is output to a client error log file and an SQL error report file.
- When 0 is specified
Parameter information is not output to a client error log file or an SQL error report file.
- If the parameter information is in the variable-length character string type, BLOB type, or BINARY type, the data size area also is included in the specified value.
- If the size of the parameter information to be output to a client error log file and an SQL error report file exceeds the value specified for this operand, only the parameter information that fits in the file size is output, and the remainder is discarded.
- Relationship to client environment definition
- The value of this operand can be changed for each client. To change the operand for a client, specify the PDUAPEXERLOGPRMSZ operand in the client environment definition. If both this operand and the PDUAPEXERLOGPRMSZ operand are specified, the PDUAPEXERLOGPRMSZ operand in the client environment definition takes precedence.
- For details about the PDUAPEXERLOGPRMSZ operand, see the HiRDB Version 9 UAP Development Guide.