In regard to he corrupted data file . Did you run UVFIXFILE to fix the file ? If not you may want to run this command first. After the fix verify if the file is ok by running the ANALYZE.FILE then list the file. Is the file used in other programs that locks a record but does not write to the record or release the record? Is the program acquiring a lock before it attempts to write to the file? If not change the program, to check for the lock and if no lock acquire a lock then write to the file.
Hope that helps D. Boyd Programmer Analyst date: Thu, 03 Nov 2005 02:22:48 +0530 From: "shuchi bhandari" <[EMAIL PROTECTED]> Subject: [U2] UV corrupted file Hi, One of our UV database files (type 30 - 64 bit) has become corrupt. As a result of this, our programs fail to write to the corrupted file. However even after exiting from the program, the unix session for the logged in user is showing a CPU utilization of around 100%; which in turn his making the system unstable. There seems to be no way of releasing these resources but to kill these idle sessions that seem to have hung for hours. If anybody has any pointers on why this is happening or how can we control it please do let me know. Thanks, rg ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
