At very quick glance, my first guess is that the problem may be caused as a result of having the Oracle 19 client installed. Verify that the system PATH does not include an entry for the Oracle 19 Client as it may be interfering with the Form Builder which uses the 12.1 client (built in).
Looking at your video, I can see that the Builder is in a bad state long before you show the crash. If I understand what you are doing, you are starting the Builder, but not logging in. You then create a trigger that includes a SELECT ... FROM DUAL. Attempting to compile this pl/sql should result in something like "identifier 'DUAL' must be declared". Instead, you are getting "ORA-00942 table or view does not exist". This suggests you have already logged in and are in a bad state, which your video does not show OR again the v19 client is interfering.
If this analysis does not help resolve the issue, please share the SR number with me offline (email) and I will follow up for you.
Regarding Oracle client installed, yes we have it in path (for other need than builder, e.g. sqlplus).
We tried with former config having Oracle client 11 and a new one with Oracle client 12.2 and a last one with 19.3
result is the same in the 3 cases.
But you mentioned having it in path could interfered with Forms builder. I will try.
Yes, the important point is that we are not logging when we try to compile. If we are connecting to a DB, there is no issue (but as you may know, developer are never connected before to compile )
The video was done with Oracle client referenced in the path.
After removing references on Pracle client from PATH variable, result is the same.
Here it is what I did before to reproduce:
PATH=C:\Program Files (x86)\Common Files\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\WINDOWS\System32\OpenSSH\;C:\Program Files\Diva;C:\Program Files\Microsoft VS Code\bin;C:\Program Files\dotnet\;C:\Users\seg\AppData\Local\Microsoft\WindowsApps;
I try to reproduce your case on my demo server. I am connecting forms 22.214.171.124 against a 126.96.36.199 db and can not reproduce the crash.
Do you try connect against a 19.3.x db?
I only have access to 18.3 databases.
I will be sending you an email shortly with my assessment of an SR review. That said, my current concern is that you have (or had) a variety of Oracle products and versions installed. For example, I can see that Forms 11.1.2 either is or was installed. Having multiple versions of the same product installed is very risky on Windows machines. It is possible that your new .4 installation is having problems because of other installed software. Again, I am trying to review your SR and will reply shortly.
One additional curious question is did you complete the configuration by executing the post-install steps instructed in the Install Guide? It requires that a script be run "As administrator" in order to complete the installation. If you did not do this then things won't work. Ok, one more question... was this a full install or Standalone Builder?
Effectively we have the both version of forms installed (F11g and F12c) because all our sites will not migrate in Forms12 at the same time.
I will make a test on a new machine without Oracle client installed and with only Forms12c.
Our installation is a standalone forms builder.
As post install step we executed config_biulder.cmd.
So if you ran the config_builder.cmd this implies you are trying to use the Standalone Builder installation option. Did you run that command with elevated privileges ("Run as administrator")? Doing so is required.
Yes, everything is executed with "run as admin".
I found why builder crashed.
Forms builder crashes when I try to open a source still in Forms11g version (not yet saved in Forms12c) after having a compilation issue on dual object.
Steps to reproduce:
- Open Forms12c not connected to a database
- Create a new module, add a trigger, add pl/sql code accessing to dual and press compile pl/sql code button (like on the video I did).
==> Compile failed because I’m not connecting to a database.
- Press CTRL+SHIFT+K, Forms proposes to connect, I connect. Compile still fails on Dual.
- Open an existing forms module migrated from forms11g to forms12c (migration was done previously just by opening it and saving it ).
==> Module is opened.
- Try to open another existing forms module not yet migrated in Forms12c (never opened and saved with forms12c)
==> Forms crashes.
I tried to reproduce with a new module without any dependencies with our environment but I was not able.
There is something with our forms framework (pll and referenced screen) that generate this crash.
So unfortunately, I can’t provide dummy forms module to reproduce.
Thank you for the update. I am able to reproduce the issue now. It appears to only reproduce when using the Windows Builder. I have created bug 30684548 for this issue. Feel free to follow up with Support if you are interested in the status. I suspect this issue may take some time to get corrected, so please consider the work-around for now, which is to connect to the db before opening any modules.