Page 1 of 1

Recursive call of OAM

Posted: Tue Feb 05, 2019 11:30 pm
by pravik
Hi All,

We have a LF with two key fields and in select statement we had specified the 1st key field alone in With_Key, once we compile and check-in respective component crashes.

Further upon checking log we could find we had received error message "Recursive call of OAM" .

Can you please suggest us how do we resolve this issue.

Thanks,
Priya

Re: Recursive call of OAM

Posted: Tue Feb 05, 2019 11:44 pm
by René Houba
Hi Priya,

When does the crash occur?
When you run the program?

Is there a trigger function involved for this file for example where you use the same file?


Kind regards,
René

Re: Recursive call of OAM

Posted: Wed Feb 06, 2019 4:34 pm
by pravik
Hi,

The application gets crashed once we click 'search' button.
There are no trigger functions attached to the respective file used in the component.

Thanks,
Priya.

Re: Recursive call of OAM

Posted: Wed Feb 06, 2019 7:02 pm
by René Houba
Hi Priya,

Can you show the RDML part?

Kind regards,
René

Re: Recursive call of OAM

Posted: Wed Feb 06, 2019 7:13 pm
by pravik
Hi Rene,

PFA, for the RDML code.

Thanks,
Priya.

Re: Recursive call of OAM

Posted: Fri Feb 08, 2019 3:57 am
by atostaine
There is nothing wrong with that code that I can see. Doing a simple select/endselect shouldn't cause an OAM message like that.

Art

Re: Recursive call of OAM

Posted: Fri Feb 08, 2019 9:24 am
by MarkD
So either there is some sort of defect, or there is some operation inside the OAM that is accessing the same table.
Could be in a trigger, a validation rule or virtual field derivation code.
Running with a trace might reveal something interesting - otherwise it should go to support.

Re: Recursive call of OAM

Posted: Fri Feb 08, 2019 11:47 am
by atostaine
Could be a DB Trigger too. Doesn’t have to be defined in Lansa. Check DSPFD myfile and look for triggers