My accuracy may be technically off on the minute details there, but
regardless, UV dynamic files are not compatible with OS-level
replication. This is from an email sent to me by Stephen O'Neal of IBM
U2 Lab Services on 3-18-09:
-------
At the exact instance that a Dynamic File expands or contracts, or a
static file increases overflow, there are multiple writes that occur.
If any of the writes don't make it to disk, you will end up with a
broken file.
When you run FIXTOOL to fix the file, it will either:
+ Fix the file, or
- Truncate the File where the mismatch occurred.
-------
Basically, any U2 file update operation that can't be done in a single
write can lead to file corruption when using OS-level replication. Your
options with UV are to implement transaction logging or use the
workarounds I mentioned earlier.
-John
-----Original Message-----
From: u2-users-boun...@listserver.u2ug.org
[mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Anthony W.
Youngman
Sent: Wednesday, December 16, 2009 5:08 PM
To: u2-users@listserver.u2ug.org
Subject: Re: [U2] Unidata 6.1 Replication
In message
<e6179e13392ec14aabcd5272c3aedd61112ce...@exchangesvr.momtex.com>, John
Hester <jhes...@momtex.com> writes
> There are also issues with UV dynamic files (don't know about UD)
>because some of the file structure information is cached in memory and
>not immediately flushed to disk.
This is no longer true.
Can't remember which IBM'er it was, but it was confirmed that UV flushes
everything at once, and it's been that way for quite a while now.
Cheers,
Wol
_______________________________________________
U2-Users mailing list
U2-Users@listserver.u2ug.org
http://listserver.u2ug.org/mailman/listinfo/u2-users
