Re: error 293 Inconsistent trigger state in TC block
As it turns out it seems that my initial thought on that the
LongMessageBuffer is too short is wrong. After reading the
commit comments around the ZINCONSISTENT_TRIGGER_STATE (293) I realised
that the resource shortage comes from the configuration variable
TransactionBufferMemory that is used to store the before value and
after value of triggers.
For most triggers this buffer's default size of 1 MByte is quite
sufficient. But foreign key triggers with NO ACTION have a check
that is deferred until commit time. Thus in this case this resource
might be exhausted in conjunction with large transactions.
So the updated advice is to increase the TransactionBufferMemory
configuration parameter.
Subject
Views
Written By
Posted
1122
March 14, 2018 02:19PM
607
March 14, 2018 09:07PM
563
March 15, 2018 12:45PM
572
March 15, 2018 05:45PM
Re: error 293 Inconsistent trigger state in TC block
593
March 16, 2018 12:52PM
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.