Check UNIX permissions, ulimit, etc. If all else fails, delete the item/record in the file, (UNIX Directory) via UnixWare, as a short term solution. Then create another "directory" with another name. Unix level copy items in "bad" directory to new, good directory you just created. RMDIR bad directory. The using Unix mv command, move the good_dir to the name of the bad_dir you RMDIR-ed: mv good_dir bad_dir_name
If problem persists, problem is within Operating System parameters not being set to deal with a file, (record/item) that large, for some reason. Contact SCO / UnixWare Support, or the VAR. ----- Original Message ----- From: "Glenn Herbert" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, December 01, 2004 9:01 AM Subject: RE: [U2] How to setup MALLOCTRACING? > At 03:30 PM 11/30/2004, you wrote: > >The &COMO&, &SAVEDLISTS& and &HOLD& files are simple type 19 (directory) > >files. Can they get corrupted and what tool should I use to check for this? > > It's not possible for these to get corrupted in the usual sense as Hashed > Files. There is not a universe utility/tool to remedy situations of this > type. It simply sounds like that the disk segment placement is your > limiting factor, which cannot be changed readily. > > Good luck! > ------- > 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/
