I thought I would dig this back up and tell what we did to fix this problem, in case someone searches for our fix. This was under the advisement of Rocket.
I used "fixtool" instead of uvfixfile. It corrected the corruption problem. I created a new 64 bit file that could hold the large amount of data. I copied all of the old data into the new file. I am going to be purging old data from the file, which is what should have been happening from the beginning and would have prevented the issue in the first place. I thank everyone for the suggestions and solutions regarding this. You are very helpful. Kevin Smith -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of David A Barrett Sent: Monday, November 09, 2009 10:14 AM To: [email protected] Subject: Re: [U2] File corrupt Two thoughts on this issue.: 1. Someone suggested using distributed files. Distributed files don't play nice with BSCAN. So if your application uses BSCAN you'll need to work around this. I'm not sure if this has been fixed in UV yet. 2. That script to find the big files was over the top. We use this in cron: testit=`find /u1 /u2 /u3 /u4 -size +1980000000c` if [[ ! -z $testit ]] then ll $testit | mailx -s"Alert, files approaching 2GB!" [email protected] fi In HP-UX you have to enable a file system to allow large files. Consequently, all of our >2GB files are located an a separate file system which isn't included in that find statement. So there's no need for us to go testing for 32 vs 64 bit files. The five line script works fine for us. Dave Barrett Project Manager, Lawyers' Professional Indemnity Company (LAWPRO®) 250 Yonge Street, Suite 3101, P.O. Box 3 Toronto, Ontario M5B 2L7 This e-mail may be privileged and/or confidential, and the sender does not waive any related rights and obligations. Any distribution, use or copying of this e-mail or the information it contains by other than an intended recipient is unauthorized. If you received this e-mail in error, please delete it and advise me (by return e-mail or otherwise) immediately. Ce courrier électronique est confidentiel et protégé. L'expéditeur ne renonce pas aux droits et obligations qui s'y rapportent. Toute diffusion, utilisation ou copie de ce message ou des renseignements qu'il contient par une personne autre que le (les) destinataire(s) désigné(s) est interdite. Si vous recevez ce courrier électronique par erreur, veuillez le supprimer et m'en aviser immédiatement, par retour de courrier électronique ou par un autre moyen. _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users _______________________________________________ U2-Users mailing list [email protected] http://listserver.u2ug.org/mailman/listinfo/u2-users
