4 Known Issues and Workarounds

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

The following topics are included:

Oracle Forms General Issues and Workarounds

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

The following topics are included:

Microsoft Windows Issues and Workarounds

This section describes issues related to Oracle Forms and Microsoft Windows.

It includes the following topics:

Shortcut Keys not Working with JAWS

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

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.

Linux/UNIX Issues and Workarounds

This section describes issues related to Oracle Forms and Linux/UNIX.

It includes the following topics:

LD_PRELOAD Setting Required for Signal Chaining Facility

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.

Check the Reports Engine Logs for FRM-41214

If you encounter the Forms error FRM-41214: Unable to run report when trying to run Reports from a Forms session, check the Reports engine logs for more details on the error.

Solaris Issues and Workarounds

This section contains issues related to Oracle Forms and Solaris.

It includes the following topic:

Runtime Issue in Oracle Forms Compiler

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

export LC_ALL=C

Other Known Issues and Workarounds

The section describes other known issues with Oracle Forms.

The following topics are included:

Oracle Forms Builder Run Form Button Fails

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, which 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

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, http://OHShost:OHSport/forms/java.

Oracle Reports Integration Requires New Environment Variable

For applications that use the Oracle Forms built-in RUN_REPORT_OBJECT to integrate with Oracle Reports, it will be necessary to add a new environment variable to the Forms environment configuration (that is, default.env). The new variable name is COMPONENT_CONFIG_PATH and its value should be the fully qualified path to the Reports Tools Component. For example: DOMAIN_HOME/config/fmwconfig/components/ReportsToolsComponent/<reports_tools_component_name>

Forms Builder will not Start on Linux 7 (OEL and RedHat) and SLES 12 SP1 Operating System

Forms Builder will not start on Linux OEL7 or RedHat7 and SUSE Linux Enterprise Server 12 SP1 or newer operating system. The following error appears:

Error while loading shared libraries: libXm.so.3: cannot open shared object file: No such file or directory.

This is the result of the Forms Builder expecting to find libXm.so.3. This version does not exist for newer Linux versions. To work-around the problem, create a soft link.

  1. Create a soft link named libXm.so.3 to libXm.so.4 under /usr/lib64/

    ln -s /usr/lib64/libXm.so.4.0.4 libXm.so.3

  2. Add it to LD_LIBRARY_PATH

    export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib64

Changes and Workarounds Affecting the Number of Characters that can be Typed into an Item


  1. When a form is created using the Forms builder (frmbld), the item property Query Length defaults to zero. When a form was compiled in releases before 11g, this value (zero) caused the Query Length to default to the value of the Maximum Length property. In Oracle Forms 11g, the Query Length defaults to two plus the value of the Maximum Length property. If the behavior of prior releases is desired, then you must set the environment variable FORMS_QUERY_LENGTH_DELTA to '0' when the form is compiled.

  2. The DATE format masks determine the number of characters that can be typed into a text item or combo box. In general, this number is the maximum of the number of characters required for the "output" format mask and for any allowable "input" format mask. The process how "input" and "output" format masks are selected for a combo box, or for a text item whose format mask is not set is described in About Format Elements for Dates. Notice that the FORMS_USER_DATE_FORMAT or FORMS_USER_DATETIME_FORMAT environment variable may specify multiple input format masks. Also observe that for any input format mask that does not contain FX, alternate format masks are also allowable, as described in String-to-Date Conversion Rules in Format Models in the SQL Reference in the Oracle Forms Builder Online Help.

    Note one exception to the rules spelled out above. The behavior described in String-to-Date Conversion Rules allow a fully spelled-out month to be entered for a numeric month (MM form mask element) or abbreviated month (MON form mask element). However, in this case, the number of characters that can be typed into a text item or combo box allows only enough room for an abbreviated month.

    Prior to 11gR1, input DATE format masks were not taken into account. In 10gR2 (10.1.2), the number of characters the end user was allowed to type into a DATE item was determined solely from the output format mask. In Forms 6i (6.0.8), the Maximum Length property of the DATE item was also taken into account.


The changes in behavior documented above may affect users who have set the Auto-Skip property for a DATE item. The end user may now be allowed to type more characters into a specific DATE item, in which case auto-skip will not occur in cases where it did occur before 11gR1. To ensure that auto-skip occurs, add the FX modifier to the format mask that will be used for the item, for example, FXYYYY/MM/DD. If there is no item-specific format mask (that is, no format mask is set either in the item's property palette or programmatically), then the item's format mask will be derived from environment variables. The FORMS_USER_DATE_FORMAT and FORMS_USER_DATETIME_FORMAT environment variables are recommended as they take precedence over any NLS environment variables that might affect DATE format masks.

Notice that specifying the FX modifier will disallow the alternate format masks that are described in String-to-Date Conversion Rules in Format Models of the SQL Reference. Also observe that the FORMS_USER_DATE_FORMAT and FORMS_USER_DATETIME_FORMAT environment variables can explicitly specify alternate format masks, separated by vertical bars, for example, FXDD-MON-YYYY|FXMON-DD-YYYY. If the FORMS_OUTPUT_DATE_FORMAT and FORMS_OUTPUT_DATETIME_FORMAT environment variables are not set, the output format masks are derived from the first format mask specified in each of the FORMS_USER_DATE_FORMAT and FORMS_USER_DATETIME_FORMAT environment variables.

Install Relevant Patches for Running and Accessing FADS Properly

You should download and install patches after completing the installation and configuration of Forms Application Deployment Services (FADS).

The patches should be installed to complete the post-configuration tasks and for FADS to work properly. You should install them in the same order as the following list:
  • 27601763

  • 28644227

  • 26732884

Download the patches from Oracle Support http://support.oracle.com.

Oracle Reports Issues and Workaround

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

The following sections are included:

Use JDBC Thin Connection Format in Reports Server Configuration

When using database as job repository or job status repository, JDBC thick connection urls in reports server configuration files will not work. Instead use JDBC thin connection urls. If connection is of JDBC thick connection format <property value="dbSid" name="dbconn"/> change it to JDBC thin connection format, for example, <property value="example.com:dbport:dbSid" name="dbconn" />.

Admin Pages are Not Available in Enterprise Manager

Oracle Reports Administration pages are not available in Enterprise Manager from release

As an alternative to Reports Administration pages use Oracle Reports Servlet and Enterprise Manager MBean browser for Reports administration, see Administering Oracle Reports Services Using Oracle Enterprise Manager.

Oracle Reports Not Starting when Length of Oracle Home path is more than 64 characters

Oracle Reports executable may not start when length of oracle home path is more than 64 characters in Windows platform.

Contact Oracle Support http://support.oracle.com for the latest available patch.