|Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows
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:
As part of Oracle Developer Suite, Oracle Forms Developer is also certified on Windows Vista. For more information about installation, patching, and certification, see http://www.oracle.com/technology/software/products/ias/files/as_certification_r2_101202.html.
Using a dual monitor configuration with Oracle Forms is now supported.
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.
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.
Forms applications use Oracle Application Server Single Sign-On only for obtaining database connection authentication. Once this connection is made, interaction with Oracle Application Server Single Sign-On no longer occurs. Exiting a Forms application will not perform an Oracle Application Server Single Sign-On logout. Conversely, logging out of an Oracle Application Server Single Sign-On session will not terminate an active Forms session. The database session will exist until the Forms Runtime (e.g. frmweb.exe) on the server terminates, usually by explicitly exiting the form.
The GO_ITEM Built-in is not allowed to navigate the cursor to an item that is currently disabled. Setting this variable to False restores the behavior found in earlier versions of Forms where this was possible. This variable should only be used for backwards compatibility and may be removed in a future version of Oracle Forms.
New code should avoid navigation to a disabled item. However, if an existing application already includes navigation to a disabled item, and if there is no issue, you can use FORMS_REJECT_GO_DISABLED_ITEM=FALSE. However if you encounter focus problems with FORMS_REJECT_GO_DISABLED_ITEM=FALSE, and FORMS_REJECT_GO_DISABLED_ITEM=TRUE causes errors in the same transaction, then you have to modify your code.
This section contains issues related to Oracle Forms and Microsoft Windows:
GET_WINDOW_PROPERTY(FORMS_MDI_WINDOW,WINDOW_HANDLE) returns zero even with separateframe=true. Oracle Forms Online Help states that this should work on windows platform. This is incorrect as this Built-in does not support MDI.
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.
When you use WebUtil's default configuration section that opens any form with Internet Explorer (versions 6 or 7) and JInitiator (versions 18.104.22.168, 22.214.171.124, 126.96.36.199), the browser hangs. This issue only occurs on dual core computers when you open a new window using Control+N, refreshing, or pressing F5.
You can use these workarounds to keep your browser session from crashing:
Run the browser on a single processor by setting the CPU affinity flag to a single processor.
Use higher versions of the Sun Java Plugin, versions 1.4 and later.
Use a browser other than Internet Explorer.
This section describes configuration issues and their workarounds. It includes the following topics:
The EM_MODE parameter in
formsweb.cfg needs to be set to
1 for Grid Control to collect metrics. This parameter is set to
0 by default. You will need to restart the Enterprise Manager Agent.
After disabling Web Cache, Grid Control reports Forms targets as down, which is false. As a workaround, in the
targets.xml file in
%ORACLE_HOME%/sysman/emd, change the target property with the
NAME="ServletUrl" to read from the HTTP listener port instead of the Web Cache port.
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 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 describes documentation errata. It includes the following topic:
In the topic "About Converting Modules from Binary to Text Format", it states:
"The text version of a module is a human-readable file that describes its objects and code."
It should read:
"The text version of a module is a human-readable file that describes its objects and PL/SQL code translated into hex."
The FIXED_LENGTH property, as mentioned in the online help, is obsolete. It is mentioned as a property of the SET_ITEM_PROPERTY Built-in, and in the PL/SQL and Forms Reserved Words.
In the Oracle Forms Services Deployment Guide, the following parameters are invalid:
In Oracle® Forms Migrating Forms Applications From Forms 6i 10g (10.1.2.0.2) for Windows and UNIX, in Chapter 2, Using the Oracle Forms Migration Assistant, the sample UNIX script says:
for file in $* do frmplsqlconv.sh module=$ff done
This small script does not work in Unix. The corrected script is:
for file in $* do frmplsqlconv.sh module=$file done
In Chapter 6, the section titled "Enabling OracleAS Single Sign-On for an Application" describes correctly the steps to add this parameter to the configuration section of a chosen application. However, if you change an existing section such as the default, the steps are slightly different as the parameter already exists.In this case, Step 5 becomes is where you select the parameter and enter a new value.
In Section 188.8.131.52.1 of Oracle Application Server Forms Services Deployment Guide, the description for Mapping F2 is written as:
To map F2, change the default entry for F2, "List Tab Pages", to another key. Here is an example of the default entry:
113: 0 : "F2" : 95 : "List Tab Pages"
This must be explicitly changed to another key mapping such as the following:
113: 8 : "F2" : 95 : "List Tab Pages"
The last line should read as:
113: 8 : "Alt+F2" : 95 : "List Tab Pages"
In section 7.5.12 of Oracle Application Server Forms Services Deployment Guide, there is a sample formsweb.cfg configuration. The last named section is written as:
[salesApp] form=sales.fmx userid=sales/salespw@orcl
However, this example should read as:
[salesApp] form=sales.fmx userid=sales/salespw@orcl jvmcontroller=
In section 9.2.2 of Oracle Application Server Forms Services Deployment Guide, the script tag is written as:
It should read as:
In section 9.2.5 of Oracle Application Server Forms Services Deployment Guide, the default threshold description is written as:
The default unreasonable threshold is set to 60,000 milliseconds, which may be too small for Oracle Forms Applications. You may want to change this default to 1 minute.
The correct description should read:
The default unreasonable threshold is set to 60,000 milliseconds, which may be too small for Oracle Forms Applications. You may want to change this default to 1 hour.
In section 9.3.1 of Oracle Application Server Forms Services Deployment Guide, the
EndUserMonitoringURL parameter is written as:
It should read as:
EndUserMonitoringURL=http://<hostname>:<webcache port number>/oracle_smp_chronos/oracle_smp_chronos_sdk.gif
Without the correct
EndUserMonitoringURL parameters, End User Monitoring will not work.