Was it broken PRIOR to running memresize? And on what version of UniData 6.0.x? Weren't there issues with Dynamic Files/resizing/guide on early 6.0 versions IIRC? - and the process is totally non-forgiving to people barging in on the file during resize - ensure no one (including web/RedBack users) have system access. All these are probably covered bases, but start at the beginning... A very good place to start. The big question is if memresize *did* the corrupting or *discovered* the corruption...
I also see you had allocated 8MB to the process - speed wise, on a VERY large file, you could easily afford to use 64MB+ (64000) and would probably see faster completion. DW -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chuck Mongiovi Sent: Monday, March 07, 2005 3:59 PM To: [email protected] Subject: [U2] broken dynamic file on UDT Hey all, I've got a *very* large dynamic file running on a UDT 6 / AIX 5 system .. I'm trying to fix it with "memresize" and getting the following error: Resize HISTFILE mod(,sep) = 0(,-1) type = -1 memory = 8000 (k) RESIZE file HISTFILE to 258317. The temporary file for memresize is rsztemp9jrTya. 2:blk check error in U_catch_tuple for file 'HISTFILE' key '35676354', number=224274 cannot read record from HISTFILE,key is 35676354 grp(224275) (1)th key -- RESIZE failed No dictionary file reference in VOC for rsztemp9jrTya. memresize failed. The file DOES have indexes .. I never have any problems with fixing static files, but when thie file breaks (and it has several times), I can't fix it .. I just have to copy as much data out of it as possible and dump the rest .. Any ideas? -Chuck MOngiovi ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
