3.2.4 Operands related to HiRDB processing
- 5) pd_thdlock_wakeup_lock = Y | N
- This operand is applicable only to the AIX and HP-UX editions.
- This operand specifies the thread lock release notification method. Specify Y in this operand to ensure that release notifications are transmitted.
- Y:
- Temporarily obtains a new separate lock when a thread lock release notification is issued.
- N:
- Does not temporarily obtain a new separate lock when a thread lock release notification is issued.
- Specification guidelines
- During concurrent execution of UAPs, if the average of the SQL runtime is several tens of milliseconds and the maximum value is one second or more, specify Y.
- Notes
- If you specify N or omit this operand, during concurrent execution of UAPs, the SQL runtime might be delayed by about one second.
- If you specify Y, during concurrent execution of UAPs, the SQL runtime might be delayed by several milliseconds.
- 6) pd_db_io_error_action = dbhold | unitdown
- Specifies the processing to be performed by HiRDB when an input/output error occurs in an RDAREA (excluding the master directory RDAREA). If an input/output error occurs in the master directory RDAREA, HiRDB (a unit for a HiRDB parallel server configuration) always terminates abnormally regardless of the specification in this operand. For the actions to be taken when an RDAREA input/output error occurs, see the HiRDB Version 9 System Operation Guide.
- An input/output error in this case refers to an error that occurs when a file manipulation attempt by HiRDB fails due to a cause that cannot be determined by HiRDB. When such an error occurs, -1544 is output as the error code returned in response to a HiRDB file system access request.
- dbhold:
- When an input/output error occurs in an RDAREA, the RDAREA is placed in an error shutdown state.
- unitdown:
- If an input/output error occurs in an RDAREA, HiRDB (a unit for a HiRDB parallel server configuration) terminates abnormally. However, if an input/output error occurs again following abnormal termination, the RDAREA is placed in an error shutdown state. To enable the specification of unitdown again, take one of the following actions:
- Start HiRDB normally.
- Execute the system reconfiguration command (pdchgconf command).
- Specification guidelines
- To determine the specification value for this operand, see HiRDB processing when an RDAREA I/O error occurs in the HiRDB Version 9 System Operation Guide.
- Operand default
- When this operand is omitted, the specification of the same operand in the system common definition is assumed. When the same operand is also omitted in the system common definition, the default is dbhold.
- Notes
- HiRDB terminates abnormally if an input/output error occurs while unitdown is specified. Consequently, in the following cases, the processing target RDAREA might go onto error shutdown status:
The UAP or utility is executing in the pre-update log acquisition mode or the no-log mode
The UAP or utility is being executed on a user LOB RDAREA that has been placed in the no-log mode by specification of NO in the RECOVERY operand of CREATE TABLE.
If you use the facility for taking a unit down when a physical error is detected, avoid running these operations, if possible. If you need to run these operations, make a backup prior to running the UAP or utility in case recovery from an RDAREA error shutdown has to be performed. For details about making back-ups, see the HiRDB Version 9 System Operation Guide.
- If an input/output error occurs during the startup or termination process, HiRDB does not terminate abnormally, even if unitdown is specified.
- When the log-only synchronous method Real Time SAN Replication facility is being used, this operand is ignored even if unitdown is specified while HiRDB when the log application site is starting.
- During recovery processing by the database recovery utility (pdrstr), HiRDB does not terminate abnormally even though unitdown is specified. In this case, re-execute pdrstr to perform recovery.
- Relationship to other operands
- This operand is related to the following operands:
- pd_mode_conf operand
- pd_db_access_error_action operand
- pd_db_hold_action operand
- If unitdown is specified in more than one of the pd_db_io_error_action, pd_db_access_error_action, and pd_db_hold_action operands, the operand value that takes effect is determined in the following order:
- pd_db_io_error_action operand
- pd_db_access_error_action operand
- pd_db_hold_action operand
- If more than one RDAREA input/output, file access, or physical error has occurred, determine the error that caused unitdown based on the above priority. In addition, see the message that is issued.