My Oracle Support Banner

FRM-93652 : When FORM_TRIGGER_FAILURE Is Raised In Called Form (Doc ID 1221685.1)

Last updated on OCTOBER 31, 2016

Applies to:

Oracle Forms - Version to [Release 11g]
Information in this document applies to any platform.
***Checked for relevance on 26-Jul-2012***
***Checked for relevance on 15-Mar-2016***


A Form is called via OPEN_FORM and the called form raises a FORM_TRIGGER_FAILURE in the PRE-FORM trigger. At this point the following error is shown.

FRM-93652: The runtime process has terminated abnormally

The stack trace produced has the following information.

Last Trigger FORM/BLOCK/FIELD: BK13501.<NULL>.<NULL>
Last Trigger: PRE-FORM - (Error: Unhandled Exception)
Msg: ORA-100501

Last Builtin: SHOW_ALERT - (Successfully Completed)

----- Call Stack Trace -----
calling call entry argument values in hex
location type point (? means dubious value)
-------------------- -------- -------------------- ----------------------------
siehDumpStackTrace( bl 1005cc918
siehWriteExceptionR bl siehDumpStackTrace( 000000000 ? 9001000A0001908 ?
eport()+0150 )

The problem is not shown when

  1. The form is called using the CALL_FORM built-in.
  2. The form is called directly (form=<formname>)
  3. The same form is run in a 10.1.2.x environment.



The Form was migrated from 10.1.2.x to or


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.