Skip Headers
Oracle® Application Server Release Notes
10g Release 2 (10.1.2) for Microsoft Windows (64-Bit) on Intel Itanium
B25335-02
  Go To Documentation Library
Home
Go To Table Of Contents
Contents

Previous
Previous
Next
Next
 

5 Oracle Forms

This chapter describes issues associated with Oracle Forms. It includes the following topics:

5.1 General Issues and Workarounds

This section contains issues related to Oracle Forms and Microsoft Windows:

5.1.1 Availability of JACOB Libraries for WebUtil

You can download the latest version of the JACOB libraries from http://prdownloads.sourceforge.net/jacob-project/.

5.1.2 Java Related Dialogs and Microsoft Windows Are Not Read By JAWS

You need to add access-bridge.jar and jaccess-1_3.jar to CLASSPATH.

5.1.3 Location of JAWS Scripts

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 http://www.oracle.com/technology/products/.

5.2 Configuration Issues and Workarounds

This section describes configuration issues and their workarounds. It includes the following topics:

5.2.1 Exception When Clicking Other Items While Inputting Multibyte Characters

In the Japanese language, 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.

5.2.2 CLOB Data Cannot be Retrieved When Query Data More Than Max Width

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.

5.2.3 FRM-92102 Existing Sessions Disconnect When User Added To JAZN

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.

5.2.4 Monitoring CPU Usage and Response Time

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.

5.3 Documentation Errata

This section describes documentation errata. It includes the following topic:

5.3.1 Incorrect Key Mapping

In Section 4.11.1.2.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"

5.3.2 Incomplete JVM Pooling Example

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= 

5.3.3 Incorrect Script Tag Names

In section 9.2.2 of Oracle Application Server Forms Services Deployment Guide, the script tag is written as:

<SCRIPT SRC="/oracle_smp_EndUserMonitoring/oracle_smp_EndUserMonitoring.js"></SCRIPT>

It should read as:

<SCRIPT SRC="/oracle_smp_chronos/oracle_smp_chronos.js"></SCRIPT>

5.3.4 Incorrect Default Threshold Setting Description

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.

5.3.5 Incorrect Parameter Names in URL

In section 9.3.1 of Oracle Application Server Forms Services Deployment Guide, the EndUserMonitoringURL parameter is written as:

Set EndUserMonitoringURL=http://computername:7777/oracle_smp_EndUserMonitoring/oracle_smp_EndUserMonitoring_sdk.gif

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.