# 1170 Forcing Corruption on a Table for Testing Purposes Causes RepairTable/VerifyTable to Fail

---

I have written a data repair utility for our app that has two functions:

(1) verify all data files for the app and report the results, and
(2) perform a repair on the tables for the app.

I have been using another app that generates sample data for our app and killing it in the middle of its generating process in order to create corrupted tables (and this seems to work pretty well). I normally get 1 - 3 tables corrupted by doing this.

So far the Verify/Repair program has worked, but this last time, I have created a table error that causes the VerifyTable function to fail and causes the calling app to simply shut down immediately. I also tried running a verify in DBSYS and it also caused DBSYS to shut down immediately.