When rolling forward a specific ai.n, the open database code does an index block clean up and writes two notes into the bi file of the backup database:
- One note updates the block and increments the update counter, for example, from 1211 to 1212.
- The other note updates the master block with a new time stamp.
The new time stamp then failed the roll forward (ai.n) because after it opened this ai.n, it found the time stamp stored in that file didn't match the new time stamp in the master block.
When the
roll forward retry of the same ai.n was then executed, the retry operation ignored the time check, read notes from the AI file then applied each of these after the retry point. Once it reached the block mentioned in the 1124 errors, it found that the block update counter was already 1212, and this then triggered the (1028) error.
There is either a hardware problem this hotspare database is running on, evident from the fact that there are no corruption at source.
And/Or there's a problem with the AI file transfer, evident by the 1029 and 9333 errors in addition to the 1028 roll forward error:
SYSTEM ERROR: Note leading and trailing counts don't match (1029)
Incomplete ai file detected, expected <blocks>, got <blocks>. (9333)
SYSTEM ERROR: Rollforward Apply AI note, BKUPDCTR=<number>, note updctr=<number>. (1028)
