write complete waits
The session waits for a buffer to be written. The write is caused by normal aging or by a cross-instance call. Wait Time:
1 second
|
Parameter |
Description |
|---|---|
|
file# |
The rollback segment id that contains the transaction that is being rolled back |
|
block# |
The transaction flags (options) set for the transaction that is being rolled back |
|
id |
Identifies the reason for waiting |
|
Id |
Reason | |
|---|---|---|
|
1022 |
Trying to renew the buffer, but it is currently being written. The buffer is formatted in the cache for a new block (old block discarded). | |
|
1027 |
The buffer is in the middle of a write, wait max 1 second. Then rescan the cache. | |
|
1027 | ||
|
(dup) |
Switch Current (same as previous). | |
|
1029 |
While trying to apply the changes to the block, the block is in the middle of a write. Wait until the block is available in a tight loop. Each wait is one second. The buffer being written is a |
current buffer. |
|
1030 |
A block is marked as corrupted and then we wait until the block is on disk. | |
|
1030 (dup) |
||
|
1031 |
||
|
1033 |
||
|
1034 |
Cross Instance Write: This instance is trying to modify the block, while another instance is trying to get a current version. This instance waits max 1 second. | |
|
1035 |
Cross Instance Write: same as 1034, but the problem now is this happens during a hot backup. | |
|
1035 (dup) |
Cross Instance Write: |