When Real Time SAN Replication is used, the information you need to check the database recovery status is output to a transaction information file each time HiRDB is restarted (no transaction information file is created for the units of a recovery-unnecessary front-end server). The name of the transaction information file is described below.

• File name: $PDDIR/spool/pdtrninf/pdriserecover.HiRDB-server-name.YYYYMMDDhhmmss
  YYYY: Year, MM: Month, DD: Day, hh: Hour (24-hour notation), mm: Minutes, ss: Seconds
  

This file generally uses no more than 600 kilobytes of disk space per server. The maximum number of transactions that can be displayed is 2 x (value of the pd_max_users operand^{#1, #2}) + 7.

#1

For a back-end server, use the value of the pd_max_bes_process operand instead. For a dictionary server, use the value of the pd_max_dic_process operand instead.

#2

If the pd_max_reflect_process operand is specified, add the value specified for it.

File output format

 
RiSe recovery information
TRNGID  TRNBID  STATUS  TIME                                    PDCLTAPNAME XID
AA....AA BB....BB CC....CC DDDD/EE/FF GG:HH:II JJJJ/KK/LL MM:NN:OO PP....PP   QQ....QQ
 

AA....AA: Global identifier of the transaction to be recovered

BB....BB: Branch identifier of the transaction to be recovered

CC....CC: Completion type of the transaction to be recovered

COMMIT: Commit

ROLLBACK: Rollback

PREPARE: Secure state

COMPLETE(C): Already committed

COMPLETE(R): Already rolled back

• If the completion type is COMMIT, ROLLBACK, or PREPARE, it means that the transaction has not completed executing at the remote site.
• If the completion type is COMMIT or ROLLBACK, it means that that transaction was recovered (with the completion type shown in STATUS) during restart processing at the remote site due to one of the following reasons:
  The transaction was not completed at the main site.
  The transaction was completed at the main site but that information did not reach the remote site.
  For these transactions, compare the completion type, the value of PDCLTAPNAME, and the start and end times with a SQL trace that you collected using whatever tool you have available to do this, and re-execute the UAP (or execute a utility) as needed to re-update the missing data.
  
• If the completion type is PREPARE and the transaction is not completed even after a restart, complete it by referring to Actions when there is an undetermined transaction in the HiRDB Version 9 System Operation Guide.

DDDD: Start year for the transaction to be recovered

EE: Start month for the transaction to be recovered

FF: Start day for the transaction to be recovered

GG: Start hour for the transaction to be recovered

HH: Start minute for the transaction to be recovered

II: Start second for the transaction to be recovered

JJJJ: End year for the transaction to be recovered

For COMMIT, ROLLBACK, or PREPARE, 9999 is displayed.

KK: End month for the transaction to be recovered

For COMMIT, ROLLBACK, or PREPARE, 99 is displayed.

LL: End day for the transaction to be recovered

For COMMIT, ROLLBACK, or PREPARE, 99 is displayed.

MM: End hour for the transaction to be recovered

For COMMIT, ROLLBACK, or PREPARE, 99 is displayed.

NN: End minute for the transaction to be recovered

For COMMIT, ROLLBACK, or PREPARE, 99 is displayed.

OO: End second for the transaction to be recovered

For COMMIT, ROLLBACK, or PREPARE, 99 is displayed.

PP....PP: value specified in PDCLTAPNAME the transaction to be recovered

QQ....QQ: XID value for the transaction to be recovered

This information is not output for a utility or if the connected client is not an X/Open-compatible application.

Output example

Explanation

In this example, transactions indicated by [1] have been completely executed while the transactions indicated by [2] will be recovered with the completion type indicated in STATUS when the remote site is restarted. For each transaction, compare the completion type, the value of PDCLTAPNAME, and the start and end times with a SQL trace that you create using whatever application you have for doing this, and separate the applications that have executed completely from those applications that will be completed through rollback or through recovery to identify the recovered content.

If any transactions were started after the transaction with the earliest end time that is in the information file for recovered transactions, and no information for these transactions is output to this file, all such transaction were completed with rollback.