Re: Exit_form fails after upgrading to 6.0
Date: Sun, 15 Oct 2000 10:33:00 -0700
Message-ID: <sujq99kn38mccf_at_corp.supernews.com>
<jb_jones_at_my-deja.com> wrote in message news:8s7ion$fp$1_at_nnrp1.deja.com...
> We recently upgraded from Dev 1.6 to Dev 6.0. We now have a problem
> where calling exit_form intermittently causes the application to crash.
> This is running on HP Unix (not PC's) against Oracle 8.0.5.
> The situation is:
> Form A calls Form B. After changing and committing data in Form B, the
> key-commit trigger calls exit_form(NO_VALIDATE). At this point, the
> application crashes, dumping the user to the Unix prompt. This happens
> roughly 10% of the time, and we have not seen anything that
> differentiates a session that crashes from a session that succeeds.
> Instead of using Exit_form, we have tried using NEW_FORM and then
> exiting from the new form, but NEW_FORM fails as well.
> We reported this exit_form problem to Oracle, but from reading the
> TARs, it looks like other people have experienced it as well when
> exiting a called form, and it appears that Oracle does not have a patch
> or know of a work-around. If anyone has found a work-around, I would
> appreciate it very much.
Are you also getting a PL/SQL runtime dump as well? We've come across that problem a lot. If so, look in your working directory, or possibly in your $ORACLE_HOME, for a file called "f60runm_*" and open it - it will have some information in it that might help trace the problem (last built-in called, last trigger called, etc.).
We've been having problems when a form has a local procedure with the same name as a library procedure and the form calls another form that calls the library. Example:
Form A has procedure "foo" which also is in the library, and Form A executes
"foo".
Form A calls form B, which calls "foo" but calls the one in the library
(doesn't have a local copy of "foo". Form B will crash because Forms gets
confused which "foo" to execute. AFAIK, it's an Oracle bug and the only
workaround is to not have local copies of procedures with the same name and
parameters as any attached libraries and find a different way than overriding
the library to do what you wanna do.
Anyway, see if you have any of that going on.
-Matt Received on Sun Oct 15 2000 - 19:33:00 CEST