IBM 000-8697 Instrukcja Użytkownika Strona 677

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
  • Strona
    / 702
  • Spis treści
  • BOOKMARKI
  • Oceniono. / 5. Na podstawie oceny klientów
Przeglądanie stron 676
Product Environment 9-57
IBM Informix STAR Configuration Parameters
1. Find all records that were updated.
2. Identify their type (insert, delete, update) using the table on
page 7-57.
3. Use the tblog -l output for each record to obtain the local xid, the
tblspacenumber,andtherowid.(Refertopage 7-55foradescription
of the tblog -l header.)
4. Map the tblspacenumber to atablename bycomparingthe tblspace
number tothe value in the partnum column ofthe systables system
catalog table.
5. 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
ROLLBACKrecordsinthedifferentlogsareclose.Nootheractivetransactions
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
IBM Informix STAR Configuration Parameters
Two configuration file parameters are specific to IBM Informix STAR:
DEADLOCK_TIMEOUT
TXTIMEOUT
Although both parameters specify time-out periods, the two are
independent.
DEADLOCK TIMEOUT
If a distributed transaction within an IBM Informix STAR environment is
forced to wait longer than the number of seconds specified by
DEADLOCK_TIMEOUT for a shared-memory resource, the database server
processthatownsthetransactionassumesthatamultiserverdeadlockexists.
The following error message is returned:
-154 ISAM error: deadlock timeout expired - Possible deadlock.
Przeglądanie stron 676
1 2 ... 672 673 674 675 676 677 678 679 680 681 682 ... 701 702

Komentarze do niniejszej Instrukcji

Brak uwag