Oracle® Fusion Middleware

Release Notes for Oracle Forms and Reports

12c (12.2.1.2)

E76631-01

October 2016

Oracle Fusion Middleware Release Notes for Oracle Forms and Reports, 12c (12.2.1.2)

E76631-01

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

Primary Author: Arup Roy

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

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 about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Contents

Preface

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

1 Introduction

- Latest Release Information

- Purpose of this Document

- About the Oracle Forms and Reports 12c (12.2.1.2.0) Documentation Library

- Additional Release Notes for This Release

- System Requirements and Specifications

- Certification Information

- Licensing Information

2 Oracle Forms

- General Issues and Workarounds

- Backwards Compatibility with Earlier Releases

- Microsoft Windows Issues and Workarounds

- Shortcut Keys not Working with JAWS

- Stop dejvm Before Stopping and Restarting WLS_FORMS

- Linux/UNIX Issues and Workarounds

- LD_PRELOAD Setting Required for Signal Chaining Facility

- Check the Reports Engine Logs for FRM-41214

- Solaris Issues and Workarounds

- Runtime Issue in Oracle Forms Compiler

- Configuration Issues and Workarounds

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

- Forms 12c Application Supports JACOB Version 1.18-M2

- Forms 12c ColorScheme Default Value Changed

- Forms Change in Time zone Support

- Known Issues

- FRM-10400 Unable to open Report Builder from Form Builder

- Oracle Forms Builder Run Form Button Fails

- Web Start Does Not Work When WLS_FORMS is Behind a Proxy

- Oracle Reports Integration Requires New Environment Variable

- Oracle Forms Fusion Middleware Control Resource Center Links not Working

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

- Running Oracle Forms applications may throw ORA-306500 Intermittently

- Oracle Forms does not play Audio Files using URL served by WebLogic Server

- Documentation Errata

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

- Auto Backup

3 Oracle Reports

- Deprecation Notice for Oracle Reports

- General Issues and Workaround

- Use JDBC thin connection format in reports server configuration

- Reports Admin pages are not available in the Enterprise Manager from 12.2.1.1 release

- Reports not starting when length of Oracle Home path is more than 64 characters

Preface

Learn about the issues you may encounter when using Oracle Forms and Reports and how to workaround them.

Audience

This document is intended for users of Oracle Fusion Middleware Forms and Reports 12c (12.2.1.2.0).

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 that have purchased support 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:

- The latest Oracle Fusion Middleware Documentation library.

- Oracle Forms and Reports 12.2.1.1.0 documentation library.

- 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 Oracle Forms and Reports Release Notes 12c (12.2.1.2.0). It includes the following topics:

- Latest Release Information

- Purpose of this Document

- About the Oracle Forms and Reports 12c (12.2.1.2.0) Documentation Library

- Additional Release Notes for This Release

- System Requirements and Specifications

- Certification Information

- Licensing Information

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/

Purpose of this Document

This document contains the release information for Oracle Forms and Reports 12c (12.2.1.2.0). It describes differences between the software and its documented functionality.

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

About the Oracle Forms and Reports 12c (12.2.1.2.0) Documentation Library

The Oracle Forms and Reports 12c Release (12.2.1.2.0) 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 2 (11.1.2) documentation that applies to the software in this release.

For example:

- For documentation about installing and using Oracle Forms Services 12c (12.2.1.2.0), refer to the Installation Guide for Oracle Forms and Reports and Forms Services Deployment Guide provided in the Oracle Forms and Reports 12c (12.2.1.2.0) library.

- For documentation about configuring the Oracle Forms and Reports 12c (12.2.1.2.0) software for high availability, refer to the relevant information existing High Availability Guide in the latest Oracle Fusion Middleware 12c (12.2.1.2.0) documentation library.

Additional Release Notes for This Release

The release notes in this document are specific to the Oracle Forms and Reports 12c (12.2.1.2.0) software.

For additional release notes that apply to this release, review the applicable release notes available in the latest Oracle Fusion Middleware 12c (12.2.1.2.0) documentation library on the Oracle Technology Network (OTN).

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 Oracle Fusion Middleware System Requirements and Specifications at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-requirements-100147.html

Certification Information

The latest certification information for Oracle Fusion Middleware 12c (12.2.1.2.0) is available at the Oracle Fusion Middleware Supported System Configurations Central Hub at http://www.oracle.com/technetwork/middleware/ias/downloads/fusion-certification-100350.html

Licensing Information

Licensing information for Oracle Fusion Middleware is available at Oracle Fusion Middleware License Information.

2 Oracle Forms

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

- General Issues and Workarounds

- Configuration Issues and Workarounds

- Known Issues

- Documentation Errata

General Issues and Workarounds

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

- Backwards Compatibility with Earlier Releases

- Microsoft Windows Issues and Workarounds

- Linux/UNIX Issues and Workarounds

- Solaris Issues and Workarounds

Backwards Compatibility with Earlier Releases

For information about changed or obsolete features, see the Oracle Forms Upgrading Oracle Forms 6i to Oracle Forms 12c Guide.

For upgrading from Oracle Forms 10g or Oracle Forms Services 11g (11.1.x), see the Planning an Upgrade of Oracle Fusion Middleware and Upgrade Guide for Forms and Reports.

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

- Stop dejvm Before Stopping and Restarting WLS_FORMS

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

- Check the Reports Engine Logs for FRM-41214

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

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

Configuration Issues and Workarounds

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

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

- Forms 12c Application Supports JACOB Version 1.18-M2

- Forms 12c ColorScheme Default Value Changed

- Forms Change in Time zone Support

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.

Forms 12c Application Supports JACOB Version 1.18-M2

Oracle Forms 12c, when configured with Webutil at runtime, supports JACOB version 1.18-M2 to perform the client side OLE integration. Notice 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 enables 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.

Forms 12c ColorScheme Default Value Changed

Oracle Forms 12c, colorscheme default value has been changed from TEAL to SWAN. This value has been set in the formsweb.cfg as part of the initial installation configuration.

colorScheme=SWAN

This colorscheme presents Forms with an updated and modernized look and feel. It also resembles the Fusion Middleware Control and all other components that are used to manage Forms12c. If you want the old colorscheme, change the value in the default section of the Forms Web Configuration (formsweb.cfg).

Forms Change in Time zone Support

Oracle Forms uses time zone data to support the ADJUST_TZ built-in and to adjust the date/time displayed in DATETIME items. Values loaded from the database or set by application logic are interpreted as being in the "server" time zone, whereas values displayed in DATETIME items are converted from the server time zone to the end-user "local" time zone. The server time zone is specified by FORMS_DATETIME_SERVER_TZ, and defaults to GMT. The end-user local time zone is specified by FORMS_DATETIME_LOCAL_TZ, and defaults to the time zone of the java client. Notice that the default values for FORMS_DATETIME_SERVER_TZ and FORMS_DATETIME_LOCAL_TZ are usually different.

In previous release, Forms interpreted a null value for FORMS_TZFILE as an indication that no time zone adjustment should occur for DATETIME items. As of Forms 12.2.1.1 release, FORMS_TZFILE is no longer inspected, so there is no specific mechanism for suppressing time zone adjustment of DATETIME items. Therefore, customers who were leaving FORMS_TZFILE unset will see a change in behavior compared to Forms 11.1.2 and older unless they take some action to ensure that the end-user local time zone is identical to the server time zone. To ensure this you must add FORMS_DATETIME_LOCAL_TZ=GMT to the environment variable configuration file, for example, default.env.

FORMS_DATETIME_SERVER_TZ defaults to GMT, so there is no need to set it to GMT explicitly if you are planning to use the above procedure.

Known Issues

The section describes known issues. It includes the following topics:

- FRM-10400 Unable to open Report Builder from Form Builder

- Oracle Forms Builder Run Form Button Fails

- Web Start Does Not Work When WLS_FORMS is Behind a Proxy

- Oracle Reports Integration Requires New Environment Variable

- Oracle Forms Fusion Middleware Control Resource Center Links not Working

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

- Running Oracle Forms applications may throw ORA-306500 Intermittently

- Oracle Forms does not play Audio Files using URL served by WebLogic Server

FRM-10400 Unable to open Report Builder from Form Builder

When created a new Report object in the Forms Builder Object Navigator, attempts to open the Report Builder will fail and show this error; FRM-10400 Unable to open Report Builder. As a work-around, manually open the Report Builder as needed.

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>

Oracle Forms Fusion Middleware Control Resource Center Links not Working

Some of the links found on the Oracle Forms home page in Fusion Middleware Control are not working. Use the Oracle Forms Deployment Guide as an alternative source of similar information.

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

Running Oracle Forms applications may throw ORA-306500 Intermittently

Solution: Apply the following patch to the Forms middle tier - for Windows 21892409 / for Unix 21534616

Oracle Forms does not play Audio Files using URL served by WebLogic Server

Oracle Forms audio functionality does not works if the URL, to obtain an audio files, is served by Oracle WebLogic Server. The audio file will fail to load.

The URL for the audio files must be served by the Oracle HTTP Server. Audio files delivered in JAR file can use URL served by either Oracle WebLogic Server or Oracle HTTP Server.

Documentation Errata

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

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

- Auto Backup

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 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. 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. 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 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 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 documented in "String-to-Date Conversion Rules" in section "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.

Auto Backup

Oracle Forms Builder now includes a new feature - Auto Backup. This feature is intended to protect module updates in the event the Forms Builder is unexpectedly terminated. Auto Backup time can be set in the Forms Builder Preferences dialog, General tab. Time is represented in minutes, however valid values are 2 - 1440. Any values less than two, invalid entries, or a null entry will disable the Auto Backup feature.

Once a valid value has been entered, the Forms Builder will monitor open modules for changes. If a change is detected since the last backup was created, an updated backup will be generated. To ensure that a module's backup is properly created, it is recommended that new modules be named and saved immediately upon creation. In the unlikely event of an unexpected shutdown, reopen the Forms Builder and reopen the module that was previously open. A dialog will appear asking if the backup copy of the module is necessary or not.

The following are the limitations of Auto Backup feature:

1. Auto Backup will only function while the Forms Builder is in use. In other words, if the Forms Builder has been minimized or is otherwise not receiving interactions from the user, backups will not be created. In most cases, this will not be an issue because changes are not being made during this time.

2. Until an valid Auto Backup Time has been entered and the Forms Builder has been properly exited, the value set will not be retained. It means that if the Forms Builder has not been properly exited after making a change to the Auto Backup Time and an unexpected termination occurs, upon restarting, the setting will revert to its previous value.

3 Oracle Reports

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

- Deprecation Notice for Oracle Reports

- General Issues and Workaround

Deprecation Notice for Oracle Reports

Oracle Fusion Middleware’s 12c R2 release (12.2.1.3.0) will be Oracle Reports terminal release.

You are advised to use or migrate to Oracle BI Publisher for reporting purposes. Oracle BI Publisher is Oracle’s strategic product for enterprise reporting. This reporting solution allows authoring, managing, and delivering pixel-perfect customer facing reports against various data sources with web browser or familiar desktop tools and minimal impact to transactional system.

Previously, Oracle Reports 10g, shipped in 2005 was its last feature bearing release. Since then Oracle Reports saw the 11g R1, 11g R2 releases. Minor enhancements were added to the product during these releases. In the 11g and in 12c R2 release, the emphasis was on product stability and bug fixing.

The following list will also provide you guidance on the future direction of the product and the options you have to protect your investment or plan the application migration to Oracle BI Publisher:

- Premium support for Oracle Reports 11g R1 is not available while for 11g R2 and 12c R2 will now be available till December 2016 and October 2020 respectively.

- Extended support for Oracle Reports 11g R1, 11g R2 and 12c R2 will be available till June 2017, December 2018 and October 2023 respectively. Oracle Reports customers can migrate to Oracle BI Publisher at their own pace while continuing to receive extended support. Oracle plans no forced upgrades or migrations.

- Oracle is not planning any functional enhancements for Oracle Reports other than critical bug fixes.

- Oracle Reports will be shipped with Oracle Fusion Middleware (12.2.1.3.0) release and it will be its terminal release.

General Issues and Workaround

This section describes general issues and workaround. It includes the following topic:

- Use JDBC thin connection format in reports server configuration

- Reports Admin pages are not available in the Enterprise Manager from 12.2.1.1 release

- Reports not starting when length of Oracle Home path is more than 64 characters

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" />.

Reports Admin pages are not available in the Enterprise Manager from 12.2.1.1 release

As of release 12.2.1.1, reports administration pages are not available in Enterprise Manager. As an alternative use Oracle Reports Servlet and Enterprise Manager MBean browser for reports administration. For more details, see the "Administering Oracle Reports Services Using Oracle Enterprise Manager" chapter in Publishing Reports to the Web with Oracle Reports Services.

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. To fix the issue, apply ARU patch number 19380012.

Oracle Legal Notices

Copyright Notice

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

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, then 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.

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.

Third-Party Content, Products, and Services Disclaimer

This software or hardware and documentation may provide access to or information about 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 unless otherwise set forth in an applicable agreement between you and Oracle. 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, except as set forth in an applicable agreement between you and Oracle.

Pre-General Availability Draft Documentation Notice

If this document is in public or private pre-General Availability status:

This documentation is in pre-General Availability 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.

Private Pre-General Availability Draft Documentation Notice

If this document is in private pre-General Availability status:

The information contained in this document is for informational sharing purposes only and should be considered in your capacity as a customer advisory board member or pursuant to your pre-General Availability trial agreement only. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. The development, release, and timing of any features or functionality described in this document remains at the sole discretion of Oracle.

This document in any form, software or printed matter, contains proprietary information that is the exclusive property of Oracle. Your access to and use of this confidential material is subject to the terms and conditions of your Oracle Master Agreement, Oracle License and Services Agreement, Oracle PartnerNetwork Agreement, Oracle distribution agreement, or other license agreement which has been executed by you and Oracle and with which you agree to comply. This document and information contained herein may not be disclosed, copied, reproduced, or distributed to anyone outside Oracle without prior written consent of Oracle. This document is not part of your license agreement nor can it be incorporated into any contractual agreement with Oracle or its subsidiaries or affiliates.

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 that have purchased support 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.