Order File Corruption
Previous Topic  Next Topic 
  1. Check for a good Backup in Saves Folder then rename the last good Backup File so that it will not be deleted. Call D3 if a good backup does not exist.


  1. Then have everyone log off the system and End the Background processes.


  1. Create a Backup File for ORDER. Get number for File Size from existing Order file in attribute #3 (CT DICT ORDER ORDER in TCL).


Ex.   CF ORDER.BACK05 1 1009 (X

                             ^                     ^

              Backup File Name   File Size


  1. COPY ORDER (I

To: (Backup File Name


  1. QSELECT ORDER,INV.DATE


  1. COPY ORDER (IS

To: (Backup File Name


  1. QSELECT TABLE ORDERLIST


  1. COPY ORDER (IS

To: (Backup File Name


  1. QSELECT TABLE BOLIST


  1. COPY ORDER (IS

To: (Backup File Name


  1. QSELECT ORDER,BILLTO (2


  1. COPY ORDER (IS

To: (Backup File Name


  1. Do a FSFIX on just the order in TCL or DM. At the colon type DB, <enter> MD <enter> Password is support and at will bring you a  >

Ex. > OD PM <enter>

> O ORDER <enter>

> FSFIX

*to verify, rerun the FSFIX or do a COUNT ORDER


12. Go into PM.INDEXES and delete them.


13. If the FSFIX does not work then do a PM.RESIZE on ORDER file and do not back

       it up. Only do this if the FSFIX did not eliminate all the errors and you have a

       complete backup of the file.


14. COPY Backup File  (IS

       To: (ORDER


15. Connect to a good FS file in Save folder (create dev-make if you need to) by doing

       T-SELECT and T-REW in the T-STAT list.


16. SEL-RESTORE ORDER (IS

       Account: PM

       File: ORDER


17. Do a PM.INDEXES and A for all.


18. At this point, most if not all orders should be restored and file fixed. Customer will

       have to check when they get back in the system.