This content has been marked as final. Show 3 replies
Did you also recreate the capi and tapi belonging to the table? There should be some code inside the tapi or capi which puts the records inside the journal table.
Yes I did recreate the tapi and capi. It's only going wrong for the combination of an update and a delete action on the same record within a transaction. If I only delete a record within a transaction the headstart code is working fine, then I see a "DEL" record in the journal table. This is also the case for insert and update actions.
Maybe the problem has something to do with the procedure perform_business_rule in qms_transaction_mgt. When performing business-rules headstart keeps track of records that are deleted during transaction. This is a comment in the procedure:
-- 188.8.131.52 Do NOT perform the business rule when the key is present in g_del_stack
-- (this is a stack with rules that can be omitted: it concerns deleted rows)
Perhaps a side effect of this mechanism is this problem I encounter. The reason for this, I noticed that the capi code that performs the writing to the journal table is treated as a business-rule by headstart. I became aware of this when I executed capi procedure disable_all_br. First I expected that the journalling code in the capi would not be effected by this procedure, but to my surprise it was. That's the reason I suspect the g_del_stack mechanism for not performing the journalling code in the capi trigger.
Does this ring a bell? And do you know how to solve this?
This doesn't ring a bell and I have no solution.1 person found this helpful