# DB verifications?

**Category:** [Yahoo Archive](https://www.epiusers.help/c/yahoo-archive/9)
**Created:** 2000-11-01 16:57 UTC
**Views:** 361
**Replies:** 1
**URL:** https://www.epiusers.help/t/db-verifications/1491

---

## Post #1 by @system

<div id="ygrps-yiv-439312692">Progress has a DB Repair Utility @ &#92;Epicor&#92;Progress&#92;Bin called DBRPR.<br/>
Epicor has a document on their web-site regarding its use.  With it you can<br/>
test your DB for corruption.</div>

---

## Post #2 by @system

<div id="ygrps-yiv-1310266804">Well, I&#39;m very relieved.  I thought I had database corruption or something <br/>
going on when I found an AP check (in CheckHed) to a non-existent <br/>
vendor.  Obviously, you can&#39;t delete a vendor after anything is created <br/>
referencing it, so I&#39;m thinking the worst and fearing corrupt indexes or <br/>
database.  Then I find out you can write a check to a non-vendor just by <br/>
punching in the name  [RTF Online Help]  :)<br/>
<br/>
OK, so nothing bad is going on.  But now I&#39;m curious.  If indexes DID <br/>
become corrupt, can or will Progress spot this, and log any warnings <br/>
?   Are there any verification utilities we should run periodically just to <br/>
check?  Pre-Vantage, we had a not-so-robust database that could get hosed <br/>
up, and benefited from periodic sanity checks.  Just wondering if there&#39;s <br/>
any such need here.<br/>
<br/>
   -Thanks,<br/>
        Wayne Cox</div>

---


**Canonical:** https://www.epiusers.help/t/db-verifications/1491
**Original content:** https://www.epiusers.help/t/db-verifications/1491