A transaction that is in FORGETTING status, as explained here, is one that satisfies all the following conditions:

• The transaction's first status listing under STATUS in the execution results of the pdls -d trn command is FORGETTING (during transaction termination processing).
• The transaction's third status listing under STATUS in the execution results of the pdls -d trn command is w (the transaction is being synchronized between the transaction manager and HiRDB).

The following is an example of a FORGETTING transaction:

pdls -d trn
 
HOSTNAME : host1(153201)
TRNGID           TRNBID           STATUS           PID   SVID   B-SVID
HRD1unt100020b51 HRD1unt100020038 FORGETTING(r,w)    0   bes1   fes1
 

When an error that satisfies one of the following conditions occurs, the transaction is in FORGETTING status on HiRDB:

• The transaction manager is terminating abnormally.
• The first SQL statement (FirstSQL) to access HiRDB after a transaction being managed by the transaction manager starts ends in an error.
• The transaction manager terminated abnormally and then finished restarting before recovery of the HiRDB transaction was complete (the following figure shows an example of a transaction in FORGETTING status).
  

  Figure 20-3 Example of a transaction in FORGETTING status after restarting the transaction manager is completed

  

Because a transaction in FORGETTING status uses HiRDB memory resources that are allocated for transactions, an error might occur if too many transactions are placed in FORGETTING status. Such an error might prevent HiRDB from being able to perform concurrent execution of a large number of transactions from connected users.

If a transaction in FORGETTING status occurs, take one of the following actions:

• Restart the transaction manager.
• Execute the pdfgt command to forcibly terminate the transaction in FORGETTING status.