New answers tagged corruption
UPDATE: What Worked... So after reading the link from @Raj and reading @ora-600's answer I tried to validate the database with the RMAN command backup check logical validate database;. While this worked fine, it was also clear that it was not looking at everything that the ANALYZE INDEX command would. After trying many different variations, I finally ...
I think the article Raj quoted (https://www.pythian.com/blog/analyze-index-validate-structure-dark-side/) describes this pretty well. "clustering factor" was also my first guess while reading the description of your problem. I also prefer to use RMAN to check for corruption. RMAN> backup check logical validate database; Afterwards you can query ...
Detach the database from virtual machine and move it to local machine (Windows). Now download and install this repair software on local machine and try to repair detached file. Software will scan the entire file and fixes all the corruption issues in the database.
When a Operating System error is encountered during the IO request, this will be reported as a 823 error. 823 error messages are reported only for failed OS IO operation errors. Given that, you need to check your system event log for any disk or file system related entries. You will need to fix the disk or file system problems or else the corruption will ...
However, after searching for similar issues, all I can see from other people is this error for 'of relation base', not 'in file'. How is 'in file' different, and what does this mean? Is it more likely that I have a hardware issue? No, it's the same issue. The error message used to refer to the relation in older versions of PostgreSQL, but it was ...
Try creating a dummy database as documented in: Creating, detaching, re-attaching, and fixing a SUSPECT database by Paul Randal This sometimes can "trick" the server into mounting a corrupt database.
Top 50 recent answers are included