TrexUpdate failed on table

[Former Member]

HOwdy..

Multi-Host Hana 96

AWS VM Linux SUSE 11 sp3

ApplicationName=dataload

Executor         PlanExecutor.cpp(00825) : plan plan37094@imdbworker01:30003 failed with rc 143; transaction serialization failure until timeout expiresTrexUpdate failed on table 'Repoprod:Campaignmember' with error: transaction order error, rc=4614

Executor         PlanExecutor.cpp(00825) : -- returns for plan37094@imdbworker01:30003:

Executor         PlanExecutor.cpp(00825) : TrexUpdate failed on table 'Repoprod:Campaignmember' with error: transaction order error, rc=4614(143), plan: 1/3 pops: RowPlanOperator pop3(in ab, out cd)

Executor         PlanExecutor.cpp(00825) :

Is this data no being inserted or updated?

I found the insert statement relative to this plan in the performance tab of the admin panel..

It is a simple insert statement?

INSERT INTO "Repoprod"."Campaignmember" ("campaign_id", "client_id", "createdby_id", "createddate", "fan_id", "fanprofile_id", "lastmodifiedby_id", "lastmodifieddate", "optindate", "optoutdate", "shortcode", "subscriptiontype", "verificationcode", "optout") VALUES(?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)

Not sure what Transaction order may be referring to?

Any insight is Appreciated!

[former_member182114]

Hi Zachary,

The message talk about time out.

This error happens all the time? Always for the same insert?

Did you checked if locks could be found on system during this event?

Regards, Fernando Da Rós

[Former Member]

YEs happens often..
THere are locks on tables, but they eventually clear every 10 minutes or so..
Very high transaction.

many writes and reads.

[lbreddemann]

The indexserver trace contains also information about the connection and the transaction with every line that is written in it.

So it should be possible to analyse this issue in a straight forward manner.

Please open a support incident and have a support colleague look into this.