1. Release Notes for Oracle Forms
  2. Known Issues and Workarounds

5 Known Issues and Workarounds

This chapter lists the known issues and workarounds associated with Oracle Forms and Oracle Reports.

The following topics are included:

Oracle Forms Issues and Workarounds

This section details issues pertaining to Oracle Forms, and their workarounds.

Table 5-1 Oracle Forms Issues and Workarounds

Issue Operating System Description
Oracle Forms Builder Run Form Button Fails All

Attempting to use the Run Form button in the Forms builder may fail if the form is not first saved in a directory included in FORMS_PATH. Alternatively, add the working directory to FORMS_PATH. This will generally be the MIDDLEWARE_HOME \bin directory.

This is an intended change in behavior and prevents directory paths from being added to a URL. Although not recommended, the behavior of previous versions can be restored by removing (or commenting) the entire FORMS_MODULE_PATH entry from default.env.

Web Start Does Not Work When WLS_FORMS is Behind a Proxy All

Attempting to start a Forms application using Web Start will fail if WLS_FORMS is behind a proxy server. To correct this problem, set WEBSTART_CODEBASE in formsweb.cfg to the fully-qualified path of the CODEBASE as it appears from the external server. For example:

https://OHShost:OHSport/forms/java
Forms Standalone Launcher (FSAL) proxy server settings may not work as expected All FSAL does not pick up proxy server settings. This issue may prevent accessing servers outside the organization's environment. This issue should not impact users accessing applications within the organization. A post-release patch is planned.
LD_PRELOAD Setting Required for Signal Chaining Facility Linux/UNIX The LD_PRELOAD setting in default.env is required for the working of signal chaining facility in JVM version 1.5 and later. If you are creating or using other environment files, the setting in the environment file for LD_LIBRARY_PATH and LD_PRELOAD must be the same as in default.env.
Unable to Generate some Modules Types Using some NLS_LANG Settings Linux/UNIX

When setting the NLS_LANG Territory to some regions, the compiler may fail and throw a FRM-30312 error.

To work around the issue, change the NLS_LANGUAGE from the typical region's language to AMERICAN. For example, change CROATIAN_CROATIA.UTF8 to AMERICAN_CROATIA.UTF8.

Builder and other Forms utilities not working after completing out-of-place upgrade. Microsoft Windows

The tooling used to perform the out-of-place upgrade does not update the Windows Registry key associated with the Fusion Middleware Oracle Home. As a result, all sub-keys that contain a reference to the path of the Oracle Home will refer to the old location and not the new location.

WARNING:

Because improperly altering the Windows Registry can cause permanent damage to the operating system, it is important to create a backup of the key being altered and/or the entire Registry. If you are not familiar with editing the Registry, please consult with someone who has experience making such changes and/or refer to your Microsoft documentation.

To correct the problem, review the entries found in the Registry key associated with this Middleware installation (for example, HKEY_LOCAL_MACHINE\SOFTWARE\Oracle\KEY_OracleHome<NUMBER>). Manually correct any entries that refer to the path where the Oracle Home was previously located. The corrected value should refer to the path of the new Home location.

Alternatively, you can use the Forms Windows Helper script (frmwinconfig). Refer to the utility's command line help for details. The utility can be found in the Oracle_Home\forms\provision directory. Run the utility as follows to display usage information:

frmwinconfig option=help
Shortcut Keys not Working with JAWS Microsoft Windows

When using Forms Builder with JAWS, the keyboard shortcuts Ctrl+Insert to create items are not working.

As a workaround, use the menu-mnemonics. Use Alt+E to open the Edit menu, then R to choose Create to create items.

Stop dejvm before Stopping and Restarting WLS_FORMS Microsoft Windows Before restarting the Oracle WebLogic managed server, all the JVM Controller processes (dejvm) started by that server must be stopped. Otherwise, WLS_FORMS will not restart after a shutdown.
Unclear Text and Image Rendering Microsoft Windows

On desktops where the Windows Display scaling value is set to any value other than 100%, some distortion may be seen when using Java 11 or later with the Forms Standalone Launcher.

As a workaround, change the Windows Display scaling setting to 100%. It may be necessary to log out of the current Windows session and log in again for the changes to completely restore proper rendering.

One or more of the following Java switches may also help to mitigate the issue. Exactly which is needed will depend on the exact symptom.

  • -Dsun.java2d.dpiaware=true
  • -Dsun.java2d.uiScale=true
  • -Dsun.java2d.autoScaleThreshold=1.5
  • -Dsun.java2d.uiScale=1.0
Windows registry entries for domain overwritten when creating additional domain(s) Microsoft Windows Attempting to configure more than one domain against an Oracle Home results in the Windows Registry entries for the newest domain overwriting the previously configured domain. This should not impact the Forms runtime behavior, but can impact the Forms tooling (such as the Builder, Compiler, and so on).
Runtime Issue in Oracle Forms Compiler Solaris

To resolve a crash of the Oracle Forms compiler at exit, while running compiler, Forms Builder and setting the NLS_LANG, the user also needs to set the environment variable LC_ALL.

export LC_ALL=C
HTTP 404 error when running a form SUSE Linux

After a seemingly successful installation and creation of the WLS Domain, all attempts to run a form result in an HTTP 404 error.

To resolve the issue:

  1. Stop all managed servers.
  2. Locate the setStartupEnv.sh file in $DOMAIN_HOME/bin directory and open it for editing.
  3. Add the following entry immediately below the comments near the top of this file, but above the first code line:
    LD_LIBRARY_PATH="<ORACLE HOME>/lib${CLASSPATHSEP}${LD_LIBRARY_PATH}"
    export LD_LIBRARY_PATH

    where <ORACLE HOME> is the fully-qualified path to the Oracle Home directory for this installation.

  4. Save the changes and close the file.
  5. Restart the server(s) and retest.
FADS does not support deploying application packages that include sql scripts IBM AIX FADS does not support deploying application packages that include sql scripts because Oracle Java and SqlDeveloper are not supported on this platform. These programs are required for FADS to process sql files properly.

Oracle Reports Issues and Workarounds

This section details issues pertaining to Oracle Reports, and their workarounds.

Table 5-2 Oracle Reports Issues and Workarounds

Issue Operating System Description
Naming Service not available in the initial release of 14.1.2.0. All The Reports Naming Service is not available in this release. Plans to provide support for an alternative to the Naming Service in the future are being investigated.