Filter
Top Products
9-44 IBM Informix OnLine Database Server Administrator’s Guide
Two-Phase Commit and Logical Log Records
Two-Phase Commit and Logical Log Records
Support of two-phase commit requires five additional logical log records.
These records can be used to detect heuristic decisions and, if required, to
help you perform a manual recovery in the event of an inconsistent database
system. The five records and their contents are described in this section. (For
more details about how to display and interpret the contents of the logical
log, refer to page 7-55.) The following illustrations of the two-phase commit
protocol are also included in this section:
BEGPREP
The BEGPREP logical log record is only written by the coordinator OnLine
database server to record the start of a global transaction.
The output from tblog contains three fields: type, flags, and number of partic-
ipants. The value of the flags is always zero in the IBM Informix STAR
environment. The number of participants is expressed as an integer. The
output appears as follows:
BEGPREP 0 number_of_participants
PREPARE
The PREPARE logical log record is only written by a participant OnLine
database server to record the ability of the participant to commit the trans-
action, if so instructed.
The output fromtblog containstwo fields: type and coordinatorserver name,
specified as the DBSERVERNAME. The output appears as follows:
PREPARE coordinator_DBSERVERNAME
Figure 9-10 on page 9-46 shows the logical log records that are written when
a transaction is committed.
Figure 9-11 on page 9-49 shows the logical log records that are written when
a piece of work is heuristically rolled back.
Figure 9-12 on page 9-50 shows the logical log records that are written when
a piece of work is heuristically ended.