G
George Potemkin
Guest
If all databases (source, target and standby) are deathly infected by a corrupted recovery note, which db copy to open using the -F option? Is a standby database the best choice? Source and taget databases were crashed. Some buffers modified by the commited transactions were not written on disk. The -F option will lose these changes. Standby database used to roll forward AI files did not crashed. All recent changes are written to disk. The -F option will not lose the changes done by the commited transactions. At least the theory seems to say this. But in theory there is no difference between theory and practice. In practice there is. In the second incident we were lucky to have only one uncommited transaction (the one with a corrupted recovery note). The customer had opened the database using the -F option but database soon crashed again due to the new corruptions that are expected when someone uses the force access: (14684) SYSTEM ERROR: Attempt to read block 0 which does not exist in area , database . (210) (10831) SYSTEM ERROR: Record continuation not found, fragment recid area 3. (10833) SYSTEM ERROR: Invalid record with recid area 1. The uncommited transaction did not update those areas. And I almost sure these corruptions did not exist before the -F was used. Why we got these errors?
Continue reading...
Continue reading...