Hi, we have to assume that you use an update-trigger for one table which includes an update into the same table or the like. Or table a updating table b updateing table a again or something like this. Or a call to a function within a trigger which itself calls something including a trigger or some mixture of this stuff. In the backtrace we can see 20 recursive trigger-/function-calls. And I think that is not what you want. Did you miss the option ignore trigger for the update IN the trigger to avoid such recursiveness? You wrote of a parameter HASHED_RULESET. This is and will never known. We know a parameter HASHED_RESULTSET. But THIS has nothing to do with your stack-problem. I do not know where you got this misleading name and info from and in which connection to which problem. Therefore I will neither recommend an upgrade to another version nor deny it. Elke SAP Labs Berlin Sitz der Gesellschaft/Registered Office: Walldorf, Germany
Vorstand/SAP Executive Board: Henning Kagermann (Sprecher/CEO), Shai Agassi, Léo Apotheker, Werner Brandt, Claus Heinrich, Gerhard Oswald, Peter Zencke Vorsitzender des Aufsichtsrats/Chairperson of the SAP Supervisory Board: Hasso Plattner Registergericht/Commercial Register Mannheim No HRB 350269 Diese E-Mail kann Betriebs- oder Geschäftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtümlich erhalten haben, ist Ihnen eine Kenntnisnahme des Inhalts, eine Vervielfältigung oder Weitergabe der E-Mail ausdrücklich untersagt. Bitte benachrichtigen Sie uns und vernichten Sie die empfangene E-Mail. Vielen Dank. This e-mail may contain trade secrets or privileged, undisclosed, or otherwise confidential information. If you have received this e-mail in error, you are hereby notified that any review, copying, or distribution of it is strictly prohibited. Please inform us immediately and destroy the original transmittal. Thank you for your cooperation.
