Errors

Question: Which information should I collect for purposes of investigation in the event of an error?

Answer: For a typical situation, use the error information collection command (pdinfoget command) to collect information. Depending on the error content, the information provided in C. Information Needed for Troubleshooting might be required.

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 might be missing in OpenTP1's transaction service definition (trn):
trnstring -n HiRDB_DB_SERVER -d
This specification suppresses OpenTP1 commit optimization and prepare optimization, and is the standard when HiRDB links to OpenTP1 through the XA interface.
A HiRDB client environment variable might be missing or an invalid value might 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 9 UAP Development Guide for the correct ones.