Appendix A.4 Errors
(1) What information do I need in the event of an error?
- Question
- Which information should I collect for purposes of investigation in the event of an error?
- Answer
- In general, save the following information onto a medium such as DAT:
- All files under $PDDIR/spool
- The following shared libraries:
/lib/libM.sl
/lib/libc.sl
/usr/lib/libdld.sl
/usr/lib/librsort.sl
- syslog file
- For an error associated with database conformity, collect the following information:
Contents of the user RDAREAs storing the corresponding table
Contents of the past log files up to that point
Contents of the master directory RDAREA
Contents of the data directory RDAREA
Contents of data dictionary RDAREAs
- Remarks
- HiRDB provides the pdgeter command for collecting all the above error information except No. 4.
(2) After restarting HiRDB, SPP terminated abnormally due to a DB lock-release wait timeout
- Question
- After restarting HiRDB, SPP terminated abnormally due to an RDAREA lock-release wait timeout:
- The database seems to still be locked. What is the cause of this?
- After SPP's abnormal termination, the status during rollback cannot be restored. What is the cause of this?
- An attempt to terminate OpenTP1 normally with the dcstop command (OpenTP1 command) failed because there is an SPP engaged in rollback processing. What is the cause of this?
- Answer
- The following specifications may be missing in OpenTP1's transaction service definition (trn):
trnstring -n HiRDB_DB_SERVER -d*
set trn_tran_optimum_processing=N
These operands suppress OpenTP1's commit optimization and prepare optimization and normally are used when HiRDB is linked with OpenTP1 via the XA interface.
* Supported by TP1/Server Base 03-03 or later.
- A HiRDB client environment variable may be missing or an invalid value may have been specified in OpenTP1's transaction service definition (trn). Check the following client environment variables:
PDHOST
PDNAMEPORT
At the same time, check OpenTP1's user service default definition (usrrc).
- Same as 2 above.
- Note
- When this event occurs, terminate OpenTP1 forcibly, correct the HiRDB system definitions, then restart OpenTP1.
- Reference note
- The environment variables common to trn and usrrc should be specified in env. When they are specified in env, the environment variables are different from those in trn or usrrc; check the HiRDB Version 8 UAP Development Guide for the correct ones.