|Oracle® Developer Suite Release Notes
10g Release 2 (10.1.2) for Solaris Operating System (SPARC), Microsoft Windows, and Linux x86
This chapter describes issues associated with Oracle Forms. It includes the following topics:
This section describes general issues and workarounds. It includes the following topics:
For information about upgrading from Oracle6i Forms, see the "Upgrading to Oracle AS Forms Services" chapter in Oracle Application Server Forms Services Deployment Guide. For information about changed or obsolete features, see the Migrating Forms Applications from Forms6i guide.
For information about upgrading from Oracle9i Forms, you can use the Upgrade Assistant. see the Oracle Application Server Upgrade and Compatibility Guide for Microsoft Windows.
For information about upgrading from Oracle9i Forms, you can use the Upgrade Assistant. see the Oracle Application Server Upgrade and Compatibility Guide for Solaris.
Additional information about backwards compatibility is MetaLink Note 113987.1 at:
Regardless from which version of Oracle Forms you are upgrading, you will need to recompile your applications and restart Oracle Forms.
This section contains issues related to Oracle Forms and Unix:
On all Unix platforms, the Forms Builder cannot be started if NLS_LANG includes any UTF8 characterset. Attempting to start the Forms Builder with this setting will cause the following errors:
FRM-91111: Internal Error: window system startup failure.
FRM-10039: Unable to start up the Form Builder.
On Unix platforms, if you relink Forms executables after installation (for example, because you're applying a one-off patch) the permissions on newly created executables will not necessarily be the same as the originals. Use
chmod to change them manually.
This section contains issues related to Oracle Forms and Solaris:
Korean UI strings are truncated when the font size is too large. As a workaround, change
in the file
Japanese UI strings are truncated when the font size is too large. As a workaround, change
in the file
This section contains issues related to Oracle Forms and Microsoft Windows:
You can download the latest version of the JACOB libraries from
You need to add access-bridge.jar and jaccess-1_3.jar to CLASSPATH.
JAWS scripts are now installed with Oracle Forms. The location for these scripts is
ORACLE_HOME/forms/ScreenReader/, and are also available at Oracle Technology Network (OTN) at
With the JDK 1.5 plugin on Microsoft Windows XP Client and IE browser, the browser hangs when exiting the Form and closing the browser. This is a known issue in the Sun Java Plug-in and will be fixed in a future release of the Sun Java Plug-in.
This section describes configuration issues and their workarounds. It includes the following topics:
If you encounter a FORBIDDEN error when using One-Button-Run with any of the supported Browsers other than Internet Explorer, verify if 127.0.0.1 (localhost) is in the proxy settings for your browser. If 127.0.0.1 is not in the exceptions list, then add it. This ensures that the browser will bypass the proxy server.
The environment setting FORMS_RESTRICT_ENTER_QUERY has a default value of
TRUE. This setting disallows users from using QUERY-WHERE functionality until it is set to
With Oracle Forms 10.1.2 and higher, the Forms PJC Wizard is part of the standard Forms installation. The PJC Wizard works with JDeveloper 10g (10.1.2) that is part of Oracle Developer Suite 10g. For versions of JDeveloper that are obtained from OTN, the PJC wizard is available as a separate Jar file to download and place into your JDeveloper installation.
In CJK languages, the Forms client may stop responding when clicking another item while inputting text through inline IME. As a workaround, disable the inline IME. See section 4.10.2, "Inline IME Support" in Oracle Application Server Forms Services Deployment Guide. This issue will be fixed in a future patch set.
The Install JDK 1.4.2 dialog appears when running a Form on the Web for the first time. When you click Install, the JDK 1.4.2 Plug-in is installed instead of the JDK 1.4.2_06 Plug-in. If you're attempting to use the JDK 1.4.2 plugin from Internet Explorer, and it isn't currently installed on your machine, it will download the wrong version. The workarounds are:
Modify formsweb.cfg by finding:
and change it to:
Run the Form (for the first time) from Netscape, which will go to the correct location for the download.
Go to the correct location and manually install the JDK 1.4.2_06 Plug-in.
When using Japanese NLS_LANG (JA16SJIS, JA16EUC etc.) if the queried CLOB data is longer than the maximum length (240 bytes by default) of the Text Item corresponding to this CLOB data, the query fails at runtime. The issue is that the CLOB data is correctly truncated with the maximum length of the Text Item (240 bytes by default) in English NLS_LANG, but not in Japanese NLS_LANG.
This issue may also raise "
FRM-40505: ORACLE error: unable to perform query" on Solaris.
Also, on Linux, error FRM-92101 occurs when encountering this issue.
This issue may also raise "
FRM-40505: ORACLE error: unable to perform query" on Microsoft Windows.
As a workaround, extend the maximum length of the Text Item to fit the length of the CLOB data.
The FRM-92102 error appears and existing Forms sessions disconnect after adding a new user to JAZN (OC4J_BI_FORMS | Applications | formsapp | Security). Thus, if you're adding new JAZN users to the OC4J_BI_Forms instance, you should do this while no Forms session is running.
On the System Component Tables in Enterprise Manager, the CPU and Memory statistics are collected every minute, by default. Note that this potentially can mean that any CPU spikes will not be displayed. In addition, if Forms server processes are dormant, awaiting client activity or requests, it is perfectly normal for the CPU usage to report 0.0%.
On the Forms Overview page, the CPU and Memory statistics are gathered each time the page is rendered when you click the Overview Tab or when you click the refresh icon next to the timestamp. However, due to an operating system restriction, if the Response Time from the Forms Servlet is less than 16ms, it will display as 0.00ms.
This section contains information about documentation errata:
In Chapter 2, Using the Oracle Forms Migration Assistant, some script code is listed as:
for file in $* do frmplsqlconv.sh module=$ff done
The correct listing should be:
for file in $* do frmplsqlconv.sh module=$file done