Question (per Mike Henderson's post on this thread):
If a file has been setup for transaction logging,
and you make a copy of a file using OS-level tools (cp, rcp, ftp, tar,
etc.),
how do you remove the TxLg info buried in the file header of the cloned
file?
Answer:
1. Use filepeek to edit the file header directly.
--- or ---
2. - Edit the UV.TRANS record to point to the new cloned file,
- then deactivate it using
UniAdmin,
or the menus in UV home dir,
or the method described a few days ago
in answer to Jeff Fitsgeralds TxLg/resize question,
- then restore the UV.TRANS record to what it should be.
This should _probably_ be done with logging disabled for the system,
but I don't know that it _must_ be so (at 10.0, anyway). If you leave
logging enabled, updates to the original file will continue to be logged
while you are doing all this, since the log number remains in that
file's header and the file header remains flagged for logging. UV.TRANS
is only used during maintenance and rolls-forward.
Of course, updates to the cloned file will be logged too, until you do
this. Furthermore, if anyone opens the cloned file before you finish
this, their process will continue logging the cloned file until they
close the file.
--- or ---
3. Maybe someone at IBM has a better answer.
-------
u2-users mailing list
[email protected]
To unsubscribe please visit http://listserver.u2ug.org/
