Skip to Main Content

Oracle Forms

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Call form causing problems with Oracle AQ

552305May 14 2009 — edited May 14 2009
Hi All,

i didn't know if i should post this in the forms forum or somewhere else but here goes:

I have a procedure on an insert trigger attached to a table that puts some data onto an Oracle Advanced Queue.

Form A is used to insert into the table and this appears to work fine, when the form is committed the data in the Queue is correct.

occasionally form A will advise you that you need to view some data on form B before committing, form B is then opened using a Call_Form procedure and passed the no_query_only parameter to allow read, write, and insert. if you then come out of the form (not performing any inserts, updates etc) and press commit on form A you get the following error:

ORA-25316: Late in the current transaction to begin an Enqueue/Dequeue operation

now reading another post about this error ( 627088 ) and the error code descriptions i can see that this error normally relates to an enqueue/dequeue on a trigger attached to a materialized view however neither form A or form B use materialized views.

if i change the call to form B to be query_only the error disappears but i do not understand why this error is being raised especially as we also have a form C which is called using no_query_only and this appears to be fine.

can anyone through some light on why i am getting this error? or any other potential fixes?

thanks in advance,
Chris
Comments
Locked Post
New comments cannot be posted to this locked post.
Post Details
Locked on Jun 11 2009
Added on May 14 2009
1 comment
436 views