Truncate not allowed when using ruleframe?

Question

Hi all,
I am using the ruleframe transaction management and in proc I use:
execute immediate ('truncate table <table name>');
I will get the following error:
Error QMS-00100: Unhandled Exception ORA-02091: transaction rolled back
ORA-02290: check constraint (HST65.QMS_NEED_TO_CLOSE_TRANSACTION) violated in PL/SQL Program Unit ...
When I start the proc without the ruleframe transaction management, everething just works fine.
Cheers,
Joep Hendrix

Answer 1

You are correct in your analysis.
As soon as a RuleFrame transaction is opened, RuleFrame (i.e. the QMS_TRANSACTION_MGT pacakge) deliberately violates a deferred check constraint by inserting a row into the table QMS_TRANSACTIONS.
Under normal circumstances, you would explicitly close a RuleFrame Transaction by calling QMS_TRANSACTION_MGT.close_transaction. When that procedure is done with all validations, it will remove the row from QMS_TRANSACTIONS. After this, a commit can be successfully performed.
However, if a commit is executed either explicitly or implicitly (e.g. through a table truncate or DDL operation) without explicitly closing the RuleFrame transaction, the Deferred Check Constraint that was violated is still violated and is now enforced as part of the implicit commit. That is the problem you are running into.
Conclusion: truncate table (nor DDL operations) can be performed inside a RuleFrame transaction.
best regards,
Lucas Jellema
AMIS Services BV