Hi Daniel,
First of all, I would think that thankfully these database corruptions are rather rare. Extremely annoying if and when they occur, but rare indeed. So I don’t believe there is reason to be particularly scared.
That said, you could obviously check your current database on a spare computer you can set up with the most recent release (B882). Then you back up your current Core, deauthorize the current Core, and try and restore your backup on the test PC with build 882. If it restores well and works, you can try and do a backup from this test PC. If it succeeds I think you can be quite certain that your current database has no ‘latent corruption’ and will update just fine.