G
George Potemkin
Guest
The scans of ai files allow us to look at the past. ;-) Here is what ai scan says in this case: The error happened after 79 sec since transaction beginning. At this moment the transaction has created 743 notes. Just before the errors the transaction did not update db during 15 seconds. Most likely an user was enterring some data from keyboard (at least the transaction also paused for 13 and 40 seconds before this moment). Then the transaction has updated an existent record: Trid: 1813582918 code = RL_LOGOP_START version = 1 (12528) Trid: 1813582918 dbkey = 0 update counter = 0 (12530) Trid: 1813582918 code = RL_RMCHG version = 2 (12528) Trid: 1813582918 area = 7 dbkey = 5947509888 update counter = 430 (12529) Trid: 1813582918 code = RL_LOGOP_END version = 1 (12528) And then the transaction has removed two index keys of the record: Trid: 1813582918 code = RL_CXREM version = 2 (12528) Trid: 1813582918 area = 7 dbkey = 5944106112 update counter = 13375 (12529) Trid: 1813582918 code = RL_CXREM version = 2 (12528) Trid: 1813582918 area = 27 dbkey = 22753076 update counter = 427 (12529) But according the previous patterns in the same transaction it should create three RL_CXREM notes. I'm waiting from the customer for the block dumps to identify the index whose key the transaction failed to update. Db log says that transaction backout completed immediately after backout's beginning but it's not true. The transaction was rolled back only during database restart. So the errors happened while the session was trying to delete an index key.
Continue reading...
Continue reading...