Skip to main content

Good morning everyone,

We have an issue with a TRANSACTION COMMIT failing with a STATUS = 3.

The Unibasic subroutine containing the TRANSACTION START/COMMIT code is called from the outside as a web service.

This failure is intermittent. 

What can cause the STATUS code = 3 ?

Thank you in advance.

André Guindon

Good morning everyone,

We have an issue with a TRANSACTION COMMIT failing with a STATUS = 3.

The Unibasic subroutine containing the TRANSACTION START/COMMIT code is called from the outside as a web service.

This failure is intermittent. 

What can cause the STATUS code = 3 ?

Thank you in advance.

André Guindon

Andre,

7.2.12 was released in October 2011, can I ask why you haven't upgraded as I'm sure your you won't be running on a 14 year old unpatched operating system.

I've checked the 7.2 documentation the Transaction Commit returns same codes as it does now and a 3 when a transaction cannot commit.

In terms of what is causing the failure, my first suggestion would be to be upgrade to a newer supported release of UniData that would allow the problem to be better investigated, if not fixed by updating 14 year old software.

In terms of investigation are you using journalling or the RFS as the way transactions for those are handled is different to those for non journalled or non RFS updates.

Have you tried checking any of the unidata error log files such as udt.errlog (or sm.log for the RFS) to see if there are any messages recorded that could assist you.

If it's being called from UO have you tried turning on the UO logging to see if you get any messages.

Regards,

Good morning everyone,

We have an issue with a TRANSACTION COMMIT failing with a STATUS = 3.

The Unibasic subroutine containing the TRANSACTION START/COMMIT code is called from the outside as a web service.

This failure is intermittent. 

What can cause the STATUS code = 3 ?

Thank you in advance.

André Guindon

Andre,

I agree with Jonathan, upgrading is the best first step, since tracking down this type of intermittent issue could be difficult, and I for one would hate to spend a lot of time finding an issue that was already solved.

That being said, I pulled the following from the documentation poral.  

---

Zoomin GPT Response to "What can prevent "transaction commit" from being successful?"

Several factors can prevent a "transaction commit" from being successful, including:

  • If the ON ERROR clause is not properly coded to abort the transaction when an error occurs during WRITE statements within the transaction, leading to inappropriate commitment.
  • If no transaction is active at the time of attempting to commit.
  • If the record (or ID) involved in the transaction does not exist.
  • System or application-specific issues that could lead to a transaction being unable to commit, as indicated by a status return value of 3.

----

Terms & ConditionsAccessibility statement