I've been playing around with the sports2000 db to see if something is possible. We thought we had corruption on an index area yesterday (thankfully after a DBANALYS we found it was Progress misreporting). Because of a number of things the last backup was therefore broken and due to a tape issue we weren't confident in our AIs either. The plan was to bring replication over to production and use that, but that takes a while.
The corruption was in an index area so I thought I'd have a play around with something. Here is what I did.
Is there anything I can do to get around that?
Yes I know it's not ideal, but I was interested to see if it would work.
11.2.1
The corruption was in an index area so I thought I'd have a play around with something. Here is what I did.
- Created Sports2000 (and did some fiddling to make it Type II storage).
- Took a backup
- Created some records
- Imagined corruption in area 10 (index area)
- Performed crash recovery
- Restored the backup somewhere and copied the files for area 10 over the ones in "production"
- We have date/time stamp issues, so did a proutil unlock
- did idxbuild all
Code:
Fri Nov 28 10:24:46 2014
[2014/11/28@10:24:46.615+0000] P-7656 T-5448 I BROKER 0: (9214) Creation date mismatch.
[2014/11/28@10:24:46.616+0000] P-7656 T-5448 I BROKER 0: (9212) Extent C:\Database\s2k\s2k_10.d1 has the wrong creation date Fri Nov 28 10:22:43 2014,
[2014/11/28@10:24:46.617+0000] P-7656 T-5448 I BROKER 0: (9216) Control Area has a creation date of Fri Nov 28 09:26:24 2014.
[2014/11/28@10:24:46.617+0000] P-7656 T-5448 I BROKER 0: (605) Probable backup/restore error.
Is there anything I can do to get around that?
Yes I know it's not ideal, but I was interested to see if it would work.
11.2.1