i did do a test, and it appears that i am mistaken. I can create all types of errors but not that particular one. Would it be possible to put out more data on the error without sacrificing confidentiality? john
On 12/27/05, john reid <[EMAIL PROTECTED]> wrote: > This is only a guess, as I have no first hand experience with that > error. Is it possible that the item that was locked was re-read after > being updated in storage and with no COMMIT? It ought to be fairly > easy to test that as a possible means of replicating the problem. > > john > > > On 12/23/05, Serguei <[EMAIL PROTECTED]> wrote: > > From time to time when the Basis code executes COMMIT statement on Universe > > the program breaks with the message: > > > > FATAL: Corrupted item in the transaction cache. > > Rolling back uncommitted transactions begun within this execution > > environment. > > FATAL: Corrupted item in the transaction cache. > > > > What this could mean? > > > > Serguei > > ------- > > u2-users mailing list > > [email protected] > > To unsubscribe please visit http://listserver.u2ug.org/ > > > > > -- > john > -- john ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
