IBM 000-8697 User Manual

Product Environment

Find all records that were updated.

Identify their type (insert, delete, update) using the table on

.

Use the tblog -l output for each record to obtain the local xid, the
tblspace number, and the rowid. (Refer to

for a description

of the tblog -l header.)

Map the tblspace number to a table name by comparing the tblspace
number to the value in the partnum column of the systables system
catalog table.

Using your knowledge of the application, determine what action is
required to correct the situation.

In this example, it is possible to see that the timestamps on the

COMMIT

and

ROLLBACK

records in the different logs are close. No other active transactions

introduce the possibility of another concurrent commit or rollback. In this
case, an insert (

HINSERT

) of assigned rowid 102 hexadecimal (258 decimal)

was committed on the current server. Therefore, the compensating trans-
action is as follows:

DELETE FROM t WHERE rowid = 258

Two configuration file parameters are specific to

IBM I

nformix

STAR

:

■

DEADLOCK_TIMEOUT

■

TXTIMEOUT

Although both parameters specify time-out periods, the two are
independent.

If a distributed transaction within an

IBM I

nformix

STAR

 environment is

forced to wait longer than the number of seconds specified by

DEADLOCK_TIMEOUT

 for a shared-memory resource, the database server

process that owns the transaction assumes that a multiserver deadlock exists.
The following error message is returned:

-154 ISAM error: deadlock timeout expired - Possible deadlock.