MySQL Forums
Forum List  »  NDB clusters

Re: error 293 Inconsistent trigger state in TC block
Posted by: Mikael Ronström
Date: March 14, 2018 09:07PM

293 is equal to ZINCONSISTENT_TRIGGER_STATE. This error code is set
in DbtcMain.cpp. In the code when set we find this comment:

/* Trigger entry found but either :
* - Overload resulted in loss of Trig_Attrinfo
* : Release resources + Abort transaction
* - Bad transaction id due to concurrent abort?
* : Release resources
*/
jam();
errorCode = ZINCONSISTENT_TRIGGER_STATE;

In your case the most likely case is Overload resulted in loss of
Trig_Attrinfo. TRIG_ATTRINFO is a signal sent containing the trigger
information.

Given that you have had to setup the parameters to be so high I presume
you have a significant amount of triggers firing.

Loss of signals is only allowed for a few select signals and
handled in
void Dbtc::execSIGNAL_DROPPED_REP(Signal* signal)

So my presumption is that you ran out of LongMessageBuffer.

Another possible but less likely alternative is that you ran out
SendBufferMemory.

Anyways if you are a customer you should report this incident.
There might be other reasons you get this problem other than the
one I can think of.

Options: ReplyQuote


Subject
Views
Written By
Posted
Re: error 293 Inconsistent trigger state in TC block
119
March 14, 2018 09:07PM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.