RE: VOC corruption

[Dan Fitzgerald]

hmm... another idea just occurred to me. I forget the environment for this 
problem, but a lot of places have some variant of a script running to query 
shared memory for nattch=0, then removing those that aren't phantoms. 
Unfortunately, at AIX 5.2, ipcs reports nattches of 0 for all memory 
segments. So if you have a script running that you think is removing locks 
held by defunct process, you may be removing valid, active locks, opening 
the door to file corruption. Still, probably not the case here, as the VOC 
shouldn't be seeing much of the I side of I/O.

"Our greatest duty in this life is to help others. And please, if you can't 
help them, could you at least not hurt them?" - H.H. the Dalai Lama

"When buying & selling are controlled by legislation, the first thing to be 
bought & sold are the legislators" - P.J. O'Rourke

Dan Fitzgerald





From: "Ray Wurlod" <[EMAIL PROTECTED]>
Reply-To: U2 Users Discussion List <[EMAIL PROTECTED]>
To: "U2 Users Discussion List" <[EMAIL PROTECTED]>
Subject: RE: VOC corruption
Date: Fri, 30 Apr 2004 06:36:30 +1000
Another "thought from left field".
I wonder whether the rotating file pool may be implicated?  There was a 
brief time when, for a single Dynamic file, opening OVER.30 rotated DATA.30 
out and vice versa (!).  VOC is supposed to be exempt from rotating (it and 
its dictionary are two of the "reserved" eight file units for sizing 
MFILES), but it might be worth checking with support about your particular 
exact release - explicitly request that they check the source code.
--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users
_________________________________________________________________
Test your ‘Travel Quotient’ and get the chance to win your dream trip! 
http://travel.msn.com

--
u2-users mailing list
[EMAIL PROTECTED]
http://www.oliver.com/mailman/listinfo/u2-users