Charles,
we dont run transaction logging.
THe has been corrupted 3 times in 3 months.
I didnt take a copy of the indexinfocus problems but will look again when
its up and running.
I am guessing that its the edi routine thats causing this problem but the
error message suggests that and there is only one read only file on the
system that i know of..
If anyone knows how to reproduce those error message i would like to know as
i have tried everything i can think of
jak
----- Original Message -----
From: "Stevenson, Charles" <[EMAIL PROTECTED]>
To: <u2-users@listserver.u2ug.org>
Cc: "John Kent" <[EMAIL PROTECTED]>; "Bob Woodward"
<[EMAIL PROTECTED]>
Sent: Wednesday, February 08, 2006 12:45 PM
Subject: RE: [U2] SYS.MESSAGE file being corrupted
From: John Kent
Has anyone experienced the above and have an explanation
Maybe. Except SYS.MESSAGE wasn't being corrupted, but rather text from
SYS.MESSAGE was corrupting other data files.
It this what you mean?
I think I have the dubious honour of finding it first (at least IBM
seemed to not know about it yet), about two years ago.
Nov 23, 2005 release notes for 10.1.16 say it has a fix:
7883 In certain circumstances, UniVerse may have incorrectly written
information from the SYS.MESSAGE file into other files. This may
have caused the header or a primary group of the file to be
overwritten, resulting in file corruption. This problem has
been fixed.
I was running Transaction Logging (TxLg) on UV 10.0.16, HPUX 11i when
logging crashed.
In it's aftermath, IBM found a piece of SYS.MESSAGES in a broken data
file. Another TxLg crash yielded a piece of what should have been
written to a COMO file (from a job that recycled used TxLg logfiles). I
have assumed the two are related.
I have seen some postings at indexinfocus but no resolution.
I whined and complained on this list in Summer 2004, and at the IBM Las
Vegas conference.
John, did you find other postings besides mine?
The above release note, is the next I heard of any progress on the
subject.
There doesnt appear to be any 3rd part software involved and
the application software doesnt ever reference this file but
its occurred 3 times in the last 3 months.
Were you using TxLg?
The quick fix was to make the file read only.
My quick fix was to turn of TxLg. (It is supposed to make the system
more robust, but we experienced our only crashes because of Transaction
Logging. My humourless management was not consoled by the irony.)
[snip]
I cant reproduce this error and the same update can be run
from the menu immediatiatly after the error without a problem.
I could not reproduce the problem on our test system and we turned off
TxLging in production.
[snip]
Any suggestions appreciated
jak
I need to find out if they think the COMO write to the wrong file is
also solved.
Before your post no one has ever mentioned to me that anyone else has
ever experienced this.
The release notes say nothing about TxLg.
The release notes say nothing about COMO or other files besides
SYS.MESSAGES.
Has anyone seen anything like this with other files?
Charles Stevenson
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 267.15.2/253 - Release Date: 7/02/2006
-------
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
