As I wrote in my first posting, you can prevent this from happening (assuming this is actually what you encountered) by:
So: either 1) upgrade to 7.2.5 or 2) don't use CONFIGURE.FILE to change MINIMUM.MODULO setting to a number smaller than the original modulo - on a file that has the potential for merging. Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 ..Denver, CO 80237 ..USA Tel: +1.720.475.8055 Email: wterh...@rs.com Web: www.rocketsoftware.com/u2 -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Address Sent: Thursday, May 06, 2010 11:52 AM To: U2 Users List Subject: Re: [U2] ERROR IS NOT A UNIDATA DATA FILE How can we prevent this from happening again ? --- On Thu, 5/6/10, Wally Terhune <wterh...@rocketsoftware.com> wrote: From: Wally Terhune <wterh...@rocketsoftware.com> Subject: Re: [U2] ERROR IS NOT A UNIDATA DATA FILE To: "U2 Users List" <u2-users@listserver.u2ug.org> Date: Thursday, May 6, 2010, 1:35 PM IF you encountered the problem I described below, it could also be corrected in a 'live' file (vs restoring from backup) using the UniData fileview utility. In this case the modulo in the file header of the dat001 file would need to be adjusted to match the current modulo recorded in the file header of the over001 file. If anyone is interested in the details - if mrparkland wants to provide the output of the following commands run on a the problem version of the file, I could provide the repair syntax: >From the shell in the account directory where the INVOICES file lives: fileview -p1 INVOICES fileview -o1 INVOICES regards, Wally Terhune U2 Support Architect Rocket Software 4700 S. Syracuse Street, Suite 400 ..Denver, CO 80237 ..USA Tel: +1.720.475.8055 Email: wterh...@rs.com Web: www.rocketsoftware.com/u2 -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Address Sent: Thursday, May 06, 2010 8:48 AM To: U2 Users List Subject: Re: [U2] ERROR IS NOT A UNIDATA DATA FILE We are on 7.2.2. We where able to restore the file from our backup. This file is small. The modulo is 99. Blocksize is 2048. We use FAST to resize our files. --- On Thu, 5/6/10, Wally Terhune <wterh...@rocketsoftware.com> wrote: From: Wally Terhune <wterh...@rocketsoftware.com> Subject: Re: [U2] ERROR IS NOT A UNIDATA DATA FILE To: "U2 Users List" <u2-users@listserver.u2ug.org> Date: Thursday, May 6, 2010, 10:30 AM The only way that I know that this can happen within the UniData engine is by using CONFIGURE.FILE to set MINIMUM.MODULO lower than the modulo they dynamic file was originally created with - and for the file to merge as records are deleted. This is fixed at 7.2.5 by a change to CONFIGURE.FILE to not allow this setting to occur. So: either upgrade to 7.2.5 or don't use CONFIGURE.FILE to change MINIMUM.MODULO setting to a number smaller than the original modulo - on a file that has the potential for merging. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users