Transaction Backout

Discuss your general Proclaim related queries here.
Posts: 55
Joined: Fri Jul 25, 2014 8:22 am
Location: Manchester
Has thanked: 2 times
Been thanked: 4 times

Transaction Backout

Post by galexander »

Anyone else had experience of this disastrous feature of OpenEdge? User does a days work creating letter, history items etc., comes back the next day and all the history items have gone. User's aren't going mad, their printed/emailed letters show these were created. Has happened here three times now.

Eclipse describe it as Transaction Backout and explained it as below. I've worked with Proclaim for ten years now and never heard of this issue before it happened to us last May, are we unlucky or have others had it?

"Progress treats transactions in a specific way – everything you do goes into what is called a “Before Image” file – once you complete a transaction this is committed to the database from the before image file. If however you start a transaction and do not complete it until much later, everything you do past the point of starting the transaction is considered to be part of the same transaction by Progress. If you then crash, the database will look for incomplete transactions and remove anything associated up to the point that transaction began. It is very rare to lose a large amount of data so I suspect the users may have started a transaction such as a Make Call or Send Letter on a case and have not completed it – if they then crashed out, anything they did prior to that starting will be fine, but anything they did after it may have been removed by the database in order to protect its integrity. Once the data is lost, we cannot recover it other than by retrieving documents from the archive or from your sent items in Outlook – the best way to prevent it from occurring is to avoid keeping actions open and effectively orphaned."

Posts: 473
Joined: Fri Jun 15, 2012 12:44 pm
Has thanked: 15 times
Been thanked: 48 times

Re: Transaction Backout

Post by revellbikes »

I've seen cases where people have been updating linked cases with poorly formatted UPDATE statements that have effectively made proclaim hit the Save button on the current case instead of the linked case. What made it worse was this was added to intelligence on screen and almost went undetected.

It had a similar outcome to that you described, users work throughout the day and come back the next day to find nothing they did saved!