Oracle® Fusion Middleware

Release Notes for Oracle Forms and Reports

11g Release 2 (11.1.2.1)

E25445-05

November 2012

Oracle Fusion Middleware Release Notes for Oracle Forms and Reports 11g Release 2 (11.1.2.1)

E25445-05

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Primary Author:  Kevin Hwang

Contributing Authors: Peter LaQuerre, Swati Thacker

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- 1.1 Latest Release Information

- 1.2 Purpose of this Document

- 1.3 Bugs Fixed

- 1.4 About the Oracle Forms and Reports 11g Release 2 (11.1.2.1) Documentation Library

- 1.5 Additional Release Notes for This Release

- 1.6 System Requirements and Specifications

- 1.7 Certification Information

- 1.8 Licensing Information

2 Installation, Configuration, and Upgrade

- 2.1 Domain Configuration Fails on SUSE11 Operating Systems

- 2.2 Oracle HTTP Server Port Conflicts After Upgrade from Oracle Fusion Middleware 11g Release 1 (11.1.1)

- 2.3 Error Message About a Failed Copy in the Upgrade Log File Can Be Ignored

- 2.4 OPATCH Failure Warning in the Install Log Can be Ignored

- 2.5 Backing Up Your Database and Database Schemas

- 2.6 Verifying Your Patch Set Installation

3 Oracle Forms

- 3.1 General Issues and Workarounds

- 3.1.1 Backwards Compatibility with Earlier Releases

- 3.1.2 Microsoft Windows Issues and Workarounds

- 3.1.2.1 Shortcut Keys not Working with JAWS

- 3.1.2.2 Invoking Reports when Forms and Reports are on Different Instances

- 3.1.2.3 Using JAWS and Java Access Bridge with Oracle Forms

- 3.1.2.4 Stop dejvm Before Stopping and Restarting WLS_FORMS

- 3.1.2.5 Precedence of Second ORACLE_INSTANCE in Registry

- 3.1.2.6 Unable to Run Forms of the First Installation by Default

- 3.1.3 Linux/UNIX Issues and Workarounds

- 3.1.3.1 LD_PRELOAD Setting Required for Signal Chaining Facility

- 3.1.3.2 Check the Reports Engine Logs for FRM-41214

- 3.2 Configuration Issues and Workarounds

- 3.2.1 Non-Internet Explorer Browser Proxy Settings when Using One-Button-Run

- 3.2.2 WebUtil Client Files Allow Configuration of Destination Directory

- 3.2.3 webutil.properties Files Renamed for Different Libraries

- 3.2.4 Forms does not Work with JDK 1.6.0_12 on Client with WinRunner

- 3.2.5 JavaScript Communication Does not Work in IE for Framed HTML File

- 3.2.6 JavaScript Events Calling Forms Applications in a Safari 5 Browser Do not Work

- 3.2.7 Forms 11gR2 Application Supports JACOB Version 1.14.3

- 3.2.8 Issue When Navigating to Schedule Prestart Page in EM

- 3.3 Documentation Errata

- 3.3.1 Passing userid in Secure Mode

- 3.3.2 Enhanced features for Oracle Real User Insight (RUEI)

- 3.3.3 Changes and workarounds affecting the number of characters that can be typed into an item

4 Oracle Reports

- 4.1 General Issues and Workarounds

- 4.1.1 Mapping Users and Roles to Reports Application

- 4.1.2 Reports Server Failure in Forms and Reports 11gRelease 2 (11.1.2.1)

Preface

This preface includes the following sections:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This document is intended for users of Oracle Fusion Middleware Forms and Reports 11g Release 2 (11.1.2).

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

For more information, see these Oracle resources:

- Oracle Forms and Reports 11g Release 1 (11.1.2) documentation library:

http://docs.oracle.com/cd/E24269_01/index.htm

- The latest Oracle Fusion Middleware 11g Release 1 (11.1.1) documentation library:

http://docs.oracle.com/cd/E23943_01/index.htm

- Oracle Technology Network:

http://www.oracle.com/technetwork/index.html

Conventions

The following text conventions are used in this document:

Convention

Meaning

boldface

Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.

italic

Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.

monospace

Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

1 Introduction

This chapter introduces Oracle Fusion Middleware Release Notes for Oracle Forms and Reports 11g Release 2 (11.1.2.1). It includes the following topics:

- Section 1.1, "Latest Release Information"

- Section 1.2, "Purpose of this Document"

- Section 1.3, "Bugs Fixed"

- Section 1.4, "About the Oracle Forms and Reports 11g Release 2 (11.1.2.1) Documentation Library"

- Section 1.5, "Additional Release Notes for This Release"

- Section 1.6, "System Requirements and Specifications"

- Section 1.7, "Certification Information"

- Section 1.8, "Licensing Information"

1.1 Latest Release Information

This document is accurate at the time of publication. Oracle will update the release notes periodically after the software release. You can access the latest information and additions to these release notes on the Oracle Technology Network at:

http://docs.oracle.com/

1.2 Purpose of this Document

This document contains the release information for Oracle Forms and Reports 11g Release 2 (11.1.2.1). It describes differences between the software and its documented functionality.

Oracle recommends you review its contents before installing or working with the product.

1.3 Bugs Fixed

The Oracle Database Client 11g Release (11.1.0.7) bug fixes listed in Table 1-1 are included in this Forms and Reports release:

Table 1-1 Oracle Database Client 11.1.0.7 Bug Fixes

Database Patch Number

Associated Forms Bug Number

Description of Symptoms

7708340

9296440

ERROR "INTERNAL ERROR [PHD_GET_DEFN:DI_U_NAM RHS]" COMPILING A FORM UNDER SPECIAL CONDITIONS

9868734

9049483

FORMS BUILDER 11G CRASHES WHEN OPENING PLL CREATED WITH 10.1.2 ON WINDOWS

NOTE: Additional steps are required on Unix operating systems. See Note 1058240.1 on My Oracle Support for more information.

9965029

9496636

FORMS FRM-93652 WHEN ATTEMPTING TO EXIT FORMS FROM MENU AFTER ENTER QU

10407723

9764631

ORA-06508 RAISED WHEN CLOSE_FORM ISSUED FROM THE CALLED FORM WITH LIBRARY ATTACHERY

1.4 About the Oracle Forms and Reports 11g Release 2 (11.1.2.1) Documentation Library

The Oracle Forms and Reports 11g Release 2 (11.1.2.1) documentation library provides documentation specific to this Oracle Fusion Middleware release.

The books in this library include cross-references to existing Oracle Fusion Middleware 11g Release 1 (11.1.1) documentation that applies to the software in this release.

For example:

- For documentation about installing and using Oracle Forms Services 11g Release 2 (11.1.2.1), refer to the Oracle Fusion Middleware Installation Guide for Oracle Forms and Reports and Oracle Fusion Middleware Forms Services Deployment guide provided in the Oracle Forms and Reports 11g Release 2 (11.1.2.1) library.

- For documentation about configuring the Oracle Forms and Reports 11g Release 2 (11.1.2.1) software for high availability, refer to the relevant information existing Oracle Fusion Middleware High Availability Guide in the latest Oracle Fusion Middleware 11g Release 1 (11.1.1) documentation library.

1.5 Additional Release Notes for This Release

The release notes in this document are specific to the Oracle Forms and Reports 11g Release 2 (11.1.2.1) software.

For additional release notes that apply to this release, review the applicable release notes available in the latest Oracle Fusion Middleware 11g Release 1 (11.1.1) documentation library on the Oracle Technology Network (OTN).

1.6 System Requirements and Specifications

Oracle Fusion Middleware installation and configuration will not complete successfully unless users meet the hardware and software pre-requisite requirements before installation. For more information, review the Oracle Fusion Middleware System Requirements and Specifications document for Oracle Fusion Middleware 11g Release 2 (11.1.2) for Forms and Reports:

http://docs.oracle.com/html/E25460_01/r2_fr_requirements.htm

1.7 Certification Information

The latest certification information for Oracle Fusion Middleware 11g Release 1 (11.1.1) and 11g Release 2 (11.1.2.1) is available at the Oracle Fusion Middleware Supported System Configurations Central Hub:

http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

1.8 Licensing Information

Licensing information for Oracle Fusion Middleware is available at:

http://docs.oracle.com/cd/E36355_01/doc.1112/e36893/toc.htm

2 Installation, Configuration, and Upgrade

This chapter describes known issues and workarounds when installing or upgrading Oracle Forms and Reports 11g Release 2 (11.1.2).

This chapter contains the following sections:

- Section 2.1, "Domain Configuration Fails on SUSE11 Operating Systems"

- Section 2.2, "Oracle HTTP Server Port Conflicts After Upgrade from Oracle Fusion Middleware 11g Release 1 (11.1.1)"

- Section 2.3, "Error Message About a Failed Copy in the Upgrade Log File Can Be Ignored"

- Section 2.4, "OPATCH Failure Warning in the Install Log Can be Ignored"

- Section 2.5, "Backing Up Your Database and Database Schemas"

- Section 2.6, "Verifying Your Patch Set Installation"

2.1 Domain Configuration Fails on SUSE11 Operating Systems

On 32-Bit and 64-Bit SUSE11 operating systems, domain creation may fail at:

opmnctl startproc ias-component=RptSvr_nsh2110213_asinst_1

with the following error:

ORACLE_HOME/bin/rwserver: error while loading shared libraries: libXm.so.3:
cannot open shared object file: No such file or directory.

To work around this issue:

1. Obtain and install openmotif22-libs-2.2.4-189.1.i586.rpm.

2. Create the following soft links in the /usr/lib64 directory:

- libXm.so -> libXm.so.4.0.3

- libXm.so.3 -> libXm.so.4.0.3

- libXm.so.4 -> libXm.so.4.0.3

2.2 Oracle HTTP Server Port Conflicts After Upgrade from Oracle Fusion Middleware 11g Release 1 (11.1.1)

When you upgrade from Oracle Fusion Middleware 11g Release 1 (11.1.1), you can choose to modify your new 11g Release 2 (11.1.2) installation to use the same ports as your 11g Release 1 (11.1.1) installation.

Alternatively, you can continue use the ports defined during the 11g Release 2 (11.1.2) installation.

In the latter case, you can run both the 11g Release 1 (11.1.1) environment and the newly upgraded 11g Release 2 (11.1.2) instance at the same time with no port conflicts.

However, in some cases, after upgrading to Oracle Forms and Reports 11g Release 2 (11.1.2), you might experience port conflicts when attempting to start the Oracle HTTP Server in both the 11g Release 1 (11.1.1) and 11g Release 2 (11.1.2) instances. This is because not all the paths in the Oracle HTTP Server configuration files were upgraded successfully.

This issue occurs if the paths to the admin.conf and ssl.conf files in the httpd.conf file are hard-coded, rather than defined using system variables. As a result, they continue to reference the configuration files in the 11g Release 1 (11.1.1) source Oracle instance, rather than the files in the 11g Release 2 (11.1.2) destination Oracle instance.

To work around this issue, perform the following task in the destination Oracle instance:

1. Locate the httpd.conf file for the destination Oracle HTTP Server.
The file is located in the following location in the destination Oracle instance:

(WINDOWS> DEST_ORACLE_INSTANCE\config\OHS\ohs1\httpd.conf

2. Edit the httpd.conf file with a text editor and replace all source paths with destination paths for all the directives in httpd.conf file.
For example, replace the following path:

"ServerRoot "<Source Oracle Instance>/config/OHS/ohs1"

with

"ServerRoot "<Destination Oracle Instance>/config/OHS/ohs1"

3. Save and close the httpd.conf file.

4. Edit the ssl.conf file located at <Destination Oracle Instance>/config/OHS/ohs1/ssl.conf by replacing the forward slash with the backward slash as shown in the following example:
Before workaround:

</Directory>

BrowserMatch ".*MSIE.*" /
nokeepalive ssl-unclean-shutdown /
downgrade-1.0 force-response-1.0

</IfModule>

After workaround:

</Directory>

BrowserMatch ".*MSIE.*" \
nokeepalive ssl-unclean-shutdown \
downgrade-1.0 force-response-1.0

</IfModule>
</VirtualHost>

5. Save and close the ssl.conf file.

6. Restart the Oracle HTTP Server instance.

2.3 Error Message About a Failed Copy in the Upgrade Log File Can Be Ignored

When you upgrade to Oracle Forms and Reports 11g Release 2 (11.1.2), the Upgrade Assistant generates a log file of the upgrade process. For more information, see "Locating the 11g Release 1 (11.1.1) to 11g Release 2 (11.1.2) Upgrade Log Files" in the Oracle Fusion Middleware Upgrade Guide for Forms and Reports.

In the log file, you might find an error message such as the following:

[copy] Failed to copy ... EmbeddedLDAP.lok due to The process cannot access the file because another process has locked a portion of the file

You can safely ignore this error.

2.4 OPATCH Failure Warning in the Install Log Can be Ignored

On 32-Bit Linux operating systems, you might find the following types of OPATCH failure warnings in the Install log during OPATCH execution:

- OUI-67200:Make failed to invoke "/usr/bin/make -f ins_rdbms.mk iextproc ORACLE_HOME=/scratch/aime1/Oracle/mwARU/Oracle_FRHome1"....'gcc: /scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/hormc.o: No such file or directory
make: *** [/scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/extproc

Error 1

- OUI-67124:Re-link fails on target "iextproc".

- OUI-67200:Make failed to invoke "/usr/bin/make -f ins_rdbms.mk iextproc ORACLE_HOME=/scratch/aime1/Oracle/mwARU/Oracle_FRHome1"....'gcc: /scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/hormc.o: No such file or directory
make: *** [/scratch/aime1/Oracle/mwARU/Oracle_FRHome1/rdbms/lib/extproc

Error 1

This is due to a failure in the Install log. You may safely ignore this warning as it does not impair any functionality.

2.5 Backing Up Your Database and Database Schemas

Section 3.2.4 "Backing Up Your Database and Database Schemas" of the Oracle Fusion Middleware Patching Guide for Oracle Forms and Reports guide mentions the incorrect schema version registry table name. The correct schema version registry table name is SYSTEM.SCHEMA_VERSION_REGISTRY$.

2.6 Verifying Your Patch Set Installation

Section 3.6 "Verifying Your Patch Set Installation" of the Oracle Fusion Middleware Patching Guide for Oracle Forms and Reports guide must include an additional (optional) verification step in order to access the Enterprise Manager Agent at the following URL:

http://host:port/emd/main

3 Oracle Forms

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

- Section 3.1, "General Issues and Workarounds"

- Section 3.2, "Configuration Issues and Workarounds"

- Section 3.3, "Documentation Errata"

3.1 General Issues and Workarounds

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

- Section 3.1.1, "Backwards Compatibility with Earlier Releases"

- Section 3.1.2, "Microsoft Windows Issues and Workarounds"

- Section 3.1.3, "Linux/UNIX Issues and Workarounds"

3.1.1 Backwards Compatibility with Earlier Releases

For information about upgrading from Forms 6i, see the "Upgrading to Oracle Forms Services 11g" chapter in Oracle Fusion Middleware Forms Services Deployment guide. For information about changed or obsolete features, see the Oracle Forms Upgrading Oracle Forms 6i to Oracle Forms 11g Guide.

For upgrading from Oracle Forms 10g or Oracle Forms Services 11g Release 1 (11.1.1), see the Oracle Fusion Middleware Upgrade Planning Guide and Oracle Fusion Middleware Upgrade Guide for Forms and Reports.

You do not need to recompile your Forms 11gR2 application if it was previously compiled in 11gR1. For Forms applications coming from any version older than 11gR1, recompilation will be required.

3.1.2 Microsoft Windows Issues and Workarounds

This section describes issues related to Oracle Forms and Microsoft Windows. It includes the following topics:

- Section 3.1.2.1, "Shortcut Keys not Working with JAWS"

- Section 3.1.2.2, "Invoking Reports when Forms and Reports are on Different Instances"

- Section 3.1.2.3, "Using JAWS and Java Access Bridge with Oracle Forms"

- Section 3.1.2.4, "Stop dejvm Before Stopping and Restarting WLS_FORMS"

- Section 3.1.2.5, "Precedence of Second ORACLE_INSTANCE in Registry"

- Section 3.1.2.6, "Unable to Run Forms of the First Installation by Default"

- Section 3.2.7, "Forms 11gR2 Application Supports JACOB Version 1.14.3"

3.1.2.1 Shortcut Keys not Working with JAWS

When using Forms Builder with JAWS, the shortcut keys 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.

3.1.2.2 Invoking Reports when Forms and Reports are on Different Instances

When Forms and Reports are configured in different instances, set the correct values for the ORACLE_HOME and ORACLE_INSTANCE at the shell and invoke the Forms Builder from the shell rather than from the Windows shortcut menu; otherwise, invoking the Reports Builder from within the Forms Builder fails.

3.1.2.3 Using JAWS and Java Access Bridge with Oracle Forms

JAWS and Java Access Bridge are not installed by default in Oracle Forms 11g. You can install the Java Access Bridge 2.0.1 using the download instructions at http://java.sun.com/products/accessbridge/. The JAWS scripts for the Oracle Forms Builder are installed in ORACLE_HOME\forms\ScreenReader\.

3.1.2.4 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.

3.1.2.5 Precedence of Second ORACLE_INSTANCE in Registry

When two Oracle instances with Forms Services are configured, using a single Oracle home on a Windows machine, then the FORMS_ORACLE_INSTANCE registry entry of the second ORACLE_INSTANCE takes precedence. It is recommended that the Forms Builder component is configured in the second ORACLE_INSTANCE.

3.1.2.6 Unable to Run Forms of the First Installation by Default

Oracle Forms from the first installation does not run by default on a Windows machine with more than one version of Forms. This is because when Fusion Middleware is installed on Windows, the new ORACLE_HOME/bin is added to the beginning of the system variable PATH. Subsequent installations result in addition of ORACLE_HOME/bin to the beginning of the system variable PATH. To run the prior installed versions, as a workaround, edit the system variable PATH. Move the ORACLE_HOME/bin that you want to use to the front of the variable PATH.

3.1.3 Linux/UNIX Issues and Workarounds

This section describes issues related to Oracle Forms and Linux/UNIX. It includes the following topics:

- Section 3.1.3.1, "LD_PRELOAD Setting Required for Signal Chaining Facility"

- Section 3.1.3.2, "Check the Reports Engine Logs for FRM-41214"

3.1.3.1 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.

3.1.3.2 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.

3.2 Configuration Issues and Workarounds

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

- Section 3.2.1, "Non-Internet Explorer Browser Proxy Settings when Using One-Button-Run"

- Section 3.2.2, "WebUtil Client Files Allow Configuration of Destination Directory"

- Section 3.2.3, "webutil.properties Files Renamed for Different Libraries"

- Section 3.2.4, "Forms does not Work with JDK 1.6.0_12 on Client with WinRunner"

- Section 3.2.5, "JavaScript Communication Does not Work in IE for Framed HTML File"

- Section 3.2.6, "JavaScript Events Calling Forms Applications in a Safari 5 Browser Do not Work"

- Section 3.2.7, "Forms 11gR2 Application Supports JACOB Version 1.14.3"

- Section 3.2.8, "Issue When Navigating to Schedule Prestart Page in EM"

3.2.1 Non-Internet Explorer Browser Proxy Settings when Using One-Button-Run

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.

3.2.2 WebUtil Client Files Allow Configuration of Destination Directory

WebUtil downloads install.syslib libraries into the bin directory of the JRE or JVM on Windows operating systems and into the lib directory of JRE on UNIX operating systems. This location can be specified in the parameter install.syslib.location.client.<OS> = <Path on client machine> (where <Path on client machine> represents the path to the location where libraries used on the client by WebUtil are stored and is either absolute or relative to client user home) in webutil.cfg.

3.2.3 webutil.properties Files Renamed for Different Libraries

When install.syslib libraries are downloaded, WebUtil creates the webutil.properties file which is located in the client user home. Different webutil.properties files are maintained on client side to allow different servers to download and manage their libraries on client. The files are named webutil.<HOST>.<CONFIG>.properties on the client, where HOST is the server computer name and CONFIG is the name of configuration section in formsweb.cfg.

3.2.4 Forms does not Work with JDK 1.6.0_12 on Client with WinRunner

Forms does not run when using JDK 1.6.0_12 and later versions on a client that also has WinRunner installed.

As a workaround, rename the two environment variables _JAVA_OPTIONS and JAVA_TOOLS_OPTIONS. For example, rename them to test_JAVA_OPTIONS and test_JAVA_TOOLS_OPTIONS. This will disable WinRunner but allows Forms to run.

3.2.5 JavaScript Communication Does not Work in IE for Framed HTML File

JavaScript communication does not work in framed HTML file that is opened in Internet Explorer 7, or in Internet Explorer 8 with file:// protocol.

As a workaround, use the IP address instead of the machine name in the URL for the frame. For example in testform.htm, change:

<frame noresize="noresize"
src="http://example.domain.com:8888/forms/java/js2frm1.html" name="fr2"
frameborder="0">
<frame noresize="noresize"
src="http://example.domain.com:8888/forms/frmservlet?play=&record=forms&
form=js2frm1&userid=scott/tiger@adt10220" name="fr1" frameborder="0">

to

<frame noresize="noresize"
src="http://IP_Address:8888/forms/java/js2frm1.html" name="fr2"
frameborder="0">
<frame noresize="noresize"
src="http://IP_Address:8888/forms/frmservlet?play=&record=forms&form=js2fr
m1&userid=scott/tiger@adt10220" name="fr1" frameborder="0">

3.2.6 JavaScript Events Calling Forms Applications in a Safari 5 Browser Do not Work

When using JavaScript integration with a Forms application in a Safari 5 browser on Windows, the communication from Forms to JavaScript running in the browser works; however, the calls to the applet from JavaScript do not work.

As a workaround, perform the following:

1. Ensure you are using base.htm.

2. In base.htm, delete the <NOSCRIPT></NOSCRIPT> tags that are wrapping the <APPLET> tag.

3.2.7 Forms 11gR2 Application Supports JACOB Version 1.14.3

Oracle Forms 11gR2, when configured with Webutil at runtime, supports JACOB version 1.14.3 in order to perform the client side OLE integration. Note that this version of JACOB is different from the versions supported in the previous releases of Oracle Forms.

JACOB is a JAVA-COM bridge that allows you to call COM automation components from Java. It uses JNI to make native calls to the COM libraries. JACOB runs on x86 and x64 environments supporting 32 bit and 64 bit JVMs.

3.2.8 Issue When Navigating to Schedule Prestart Page in EM

You will see the following issue when you try to navigate to the Schedule Prestart page in Oracle Enterprise Manager (EM):

- The Schedule Prestart links of the custom deployed applications behave in an unexpected manner. The Forms deployment table on the Forms homepage lists all the custom deployed applications. When you navigate to the Schedule Prestart page from the Schedule Prestart link of any custom deployed application, the page fails to show the prestart schedules of the custom deployed applications. Instead, the Schedule Prestart page always shows the prestart schedules of the default application.

3.3 Documentation Errata

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

- Section 3.3.1, "Passing userid in Secure Mode"

- Section 3.3.2, "Enhanced features for Oracle Real User Insight (RUEI)"

- Section 3.3.3, "Changes and workarounds affecting the number of characters that can be typed into an item"

3.3.1 Passing userid in Secure Mode

The following information on passing userid in secure mode must be added to Oracle Forms Builder online help.

Passing userid as an argument when using the Forms compiler (frmcmp or frmcmp_batch) may lead to security risks. In addition to the interactive dialog mode already available, the compiler can now accept the connect string via standard input. To pass the userid in a secure mode, perform the following:

1. Set the environment variable FORMS_STDIN_PASSWORD to 1.

2. Run the compiler without any connect string. Enter the connect string after the compiler has started.

3. Run the compiler using redirection to pass the password to the compiler. (This is especially useful in compiling several Forms in a script.) For example:

#!/bin/sh
echo "Enter userid"
read -s myuserid
for i in 'ls *.fmb'
do
echo Compiling Form $i ....
frmcmp_batch.sh batch=yes module=$i module_type=form compile_all=yes <<<
"$myuserid"
done

Note that this script is a sample that tries to protect the password, but on some platforms and configurations it may still lead to security risks.

3.3.2 Enhanced features for Oracle Real User Insight (RUEI)

The following information must be added to Oracle Forms Builder online help.

Oracle Real User Experience Insight (RUEI) is a feature of Oracle Fusion Middleware that provides non-intrusive monitoring. It gives an insight into how a user interacts with an application. Oracle Forms 11g Release 2 has added functionality to enhance support for RUEI. Two new constants have been added as valid values for the user_response parameter of the MESSAGE builtin. They are RUEI_BEGIN and RUEI_END.

When the Forms server processes the MESSAGE builtin using either of the newly defined constants, it sends a message to the client so that RUEI can note the information contained in the message. However, the Forms client does not display the message to the end-user. Thus, these new constants allow for RUEI to provide more information about logical operations without changing the end-user's experience. For example,

MESSAGE('my message1', RUEI_BEGIN);

...some plsql code...

MESSAGE('my message1' RUEI_END);

This will not display my message1 on the client, but someone using RUEI to understand the performance of their application may be able to get some insight into how long it took to execute the surrounded pl/sql code.

Also to help enhance the RUEI user experience, if the environment variable FORMS_RUEI_SEND_FORM_NAME is set, the Forms server will send the name of the form module to the client for each window that is created in the form so that RUEI can easily associate a particular window and its contents with a particular form.

3.3.3 Changes and workarounds affecting the number of characters that can be typed into an item

The following information must be added to Oracle Forms Builder online help.

1. When a form is created using the Form builder (frmbld), the item property Query Length defaults to zero. When the form was compiled in releases prior to 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. Refer to "About Format Elements for Dates" for information about how "input" and "output" format masks are selected for a combo box, or for a text item whose format mask is not set. Note that the FORMS_USER_DATE_FORMAT or FORMS_USER_DATETIME_FORMAT environment variable may specify multiple input format masks. Also note that for any input format mask that does not contain FX, alternate format masks are also allowable, as documented in "String-to-Date Conversion Rules" in section "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 in place of 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.

Workarounds

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 prior to 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.

Note that specifying the FX modifier will disallow the alternate format masks that are documented in "String-to-Date Conversion Rules" in section "Format Models" of the SQL Reference. Also note 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.

4 Oracle Reports

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

- Section 4.1, "General Issues and Workarounds"

4.1 General Issues and Workarounds

This section describes general issue and workarounds. It includes the following topic:

- Section 4.1.1, "Mapping Users and Roles to Reports Application"

- Section 4.1.2, "Reports Server Failure in Forms and Reports 11gRelease 2 (11.1.2.1)"

4.1.1 Mapping Users and Roles to Reports Application

In Oracle Fusion Middleware 11g Release 2 (11.1.2) installations, roles and users are not added to the Reports application, by default. To run a report using JPS security, you must add roles and users to the Reports application.

For more information, see:

- "Managing Application Roles" in the Oracle Fusion Middleware Security Guide

- "Managing Users and Security Policies" in the Oracle Fusion Middleware Publishing Reports to the Web with Oracle Reports Services manual

4.1.2 Reports Server Failure in Forms and Reports 11gRelease 2 (11.1.2.1)

Reports Server fails to start after installing and configuring Forms and Reports 11.1.2.1.

To work around this issue, perform the following steps before you start a Reports Server instance:

1. Locate the cwallet.sso file at
domainHome\config\fmwconfig\bootstrap

2. Add the write permission to the SYSTEM user's assigned privileges.

3. Restart Reports Server.
After granting write permission to the file for SYSTEM user, the Reports Server starts.

Oracle Legal Notices

Copyright Notice

Copyright © 1994-2014, Oracle and/or its affiliates. All rights reserved.

Trademark Notice

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

License Restrictions Warranty/Consequential Damages Disclaimer

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

Warranty Disclaimer

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

Restricted Rights Notice

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

Hazardous Applications Notice

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Alpha and Beta Draft Documentation Notice

If this document is in preproduction status:

This documentation is in preproduction status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.