Forms 5.0.6.8.0 - ORA-04062: of has been changed.
Patrick Flahan
packaged procedures to build blocks (PL/SQL tables and ref cursors). I
compile the form against one database and the form works fine. I then take
the fmx and run it against a different database with the exact same
structure. The packaged procedures are all compiled and working properly.
The form then generates the ora-04062: of has been changed error message.
Is it just me or does this seem wrong? Why can't I run the form against
different instances without recompiling the form? If anyone else has had
this problem and can provide additional information, I would greatly
appreciate it. I have a patch disk coming from Oracle, but they are sure if
it will fix the problem.
Thanks,
Patrick Flahan
pfl...@romac.com
ste...@zimmer.csufresno.edu
Forms 5 is not certified to run on these earlier versions of Oracle -- I think
it says that in the release notes.
I had the same problem with the Forms 5 version of my QA utility form. You
can read more on my web site http://members.aol.com/stevec5088 then click
the link, "Experiences creating a Forms 5.0 version of QA".
You should no longer get the 04062 errors once both databases you are using
are upgraded.
HTH
Steve Cosner
In article <7686ep$kb9$1...@holly.prod.itd.earthlink.net>,
-----------== Posted via Deja News, The Discussion Network ==----------
http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own
Günter Huerkamp
What is your Database Versions. Since Form 5.0 your Database version
must be 7.3.4 or greater ,
less than you get an
Timestamp Error.
See the relnotes.txt in orant\tools\doc20 directory for more
Information.
Günter
Van Nieuwenhuyse
Either you recompile your form against every db ?!?!
Either you use procedures (the problem only occurs with packages).
Patrick Flahan heeft geschreven in bericht
<7686ep$kb9$1...@holly.prod.itd.earthlink.net>...
Piotr Kolodziej
>I am developing a Form using Forms 5.0.6.8.0 and have been using the
>packaged procedures to build blocks (PL/SQL tables and ref cursors). I
>compile the form against one database and the form works fine. I then take
>the fmx and run it against a different database with the exact same
>structure. The packaged procedures are all compiled and working properly.
>The form then generates the ora-04062: of has been changed error message.
It is a problem with Forms 5.0 PL/SQL Engine calling db packaged functions
even if the version of Oracle Server is 7.3.4 or 8.0.4+.
You should set REMOTE_DEPENDENCIES_MODE=signature at least at the client
side (default is timestamp) and avoid changing package specification
if you don't want to recompile forms at any time (I dont think that you want).
If you have to change package specification, avoid changing specifications
used by forms and insert new components at the tail of package (!!!).
In other case signature of package won't match the signature stored
in compiled form.
Other solution is compiling all used packages with the same timestamp.
Yes, that's a horrible issue with PL/SQL 2 engine in Forms. In fact,
calling stored procedure by forms is just like calling remote procedure
by local in distributed environment. But recompiling procedure in forms
is not as recompiling procedure in database (!)
DIANA, come back! ;-)))
--
Piotr Kolodziej pk...@otago.gda.pl
Just my private opinion.
Patrick Flahan
Forms 5.0.6.8 does not automatically use signature. They are currently
looking into the problem. I also tried to force the forms session to use
signature by using Forms_DDL('alter session set
remote_dependencies_mode=signature'); and this did not seem to help. I am
going to try to move this to a plain stand alone procedure in the database
and see if it helps.
Patrick
Piotr Kolodziej <pk...@otago.gda.pl> wrote in message
news:76d715$ged$1...@korweta.task.gda.pl...
Piotr Kolodziej
Patrick Flahan wrote in message <76j3n6$339$1...@holly.prod.itd.earthlink.net>...
>I looked into this and you are correct. Thanks for your help. Appears
>Forms 5.0.6.8 does not automatically use signature. They are currently
>looking into the problem. I also tried to force the forms session to use
>signature by using Forms_DDL('alter session set
>remote_dependencies_mode=signature'); and this did not seem to help.
Try using dbms_session package.
Regards,
Patrick Flahan
Piotr Kolodziej <pk...@otago.gda.pl> wrote in message
news:76ppb3$e2j$1...@korweta.task.gda.pl...
Piotr Kolodziej
>Which procedure/function?
Oupsss... Sorry. No such function in dbms_session.
I'm not quite sure now if that would take effect with alter session
but you may use dbms_sql as the last resort...