I have a end user that we recently purged some data out of his system, did a ""Purge Item History"" for any years including and prior to 2012 for our company. The process completed successfully with no errors.
We ran the ""Rebuild Key Files"" process for all data files in the IM module with ""Integrity Check"" and ""Optimize Files"" both checked to reduce the file size upon completion of the truncation.
The process ran normally, up until it reached the IM_PeriodPostingHistory file, after about an hour we received this error: The read test failed. Error #11: Record not found or Duplicate key on write. There were two options to select, either Rebuild or Cancel. Chose rebuild, the process restarted, .NEW .NWC files were created and the system continued to crank away.
Once completed the log file was clean except this entry.
IM_PeriodPostingHistory.M4T - The read test failed. Error #11: Record not found or Duplicate key on write. Record count indicates all records were recovered. Validating Key definitions for segmented file. Keys from the old file are being compared to the new file. No discrepancies have been found.
Once completed, it looked like the IM_PeriodPostingHistory file was wiped clean given the file size. The .old created listed below.
IM_PeriodPostingHistory.M4T = 13 kb
IM_PeriodPostingHistoryAJE090322287973.OLD = 1,832,231 kb
IM_PeriodPostingHistoryAJE090322287973.OLD.001 = 1,832,231 kb
IM_PeriodPostingHistoryAJE090322287973.OLD.002 = 835,705 kb
This is one of the few end-users I have that has data files large enough to have had to create chained or linked files over the 2GB limit. Odd that it happened on these files. Anyone else run into something like this before?
By the way, this isn't terribly urgent (it's on a test machine - trial conversion), just didn't know where else to post this.