Oracle® Fusion Middleware

Release Notes for Oracle BI Discoverer, Forms, Reports, and Portal

11g Release 1 (11.1.1)

E54906-01

June 2014

Oracle Fusion Middleware Release Notes for Oracle BI Discoverer, Forms, Reports, and Portal, 11g Release 1 (11.1.1)

E54906-01

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

Primary Author:  Savija Vijayaraghavan

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 failsafe, 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 Oracle Business Intelligence Discoverer

- General Issues

- Error while Accessing a Discoverer Menu Option in Enterprise Manager

- Issues with Metadata Repository and Oracle Database 10g Release 1

- Compatibility Issues with Required Support Files

- Serif Font Issue in Worksheets

- Additional Fonts Required for Non-ASCII Data When Exporting to PDF

- Query Prediction Requires the Majority of the Query Time

- Word Wrapping Behavior with Oracle BI Discoverer Plus and Oracle BI Discoverer Viewer

- Applet Appears Behind Browser Window

- Issues with Mac OS X Browser and Oracle BI Discoverer Plus

- Issues with Turkish Regional Settings

- Multibyte Characters Rendered as Square Boxes in Exported PDF and Other Formats

- Java Plug-in Not Downloaded Automatically on Firefox

- HTTP 404 Error While Accessing Discoverer on a Remote Machine

- Error While Launching Discoverer Plus Applet on an IPv6 Environment

- Error While Updating the Discoverer Web Services Configuration Parameter

- Exception Logged for Discoverer Web-Based Applications in an Extended Domain

- Issue with Discoverer Application URL in Fusion Middleware Control after a Backup Recovery

- Incorrect Version Number for Discoverer in Fusion Middleware Control 11g

- Oracle BI Discoverer Startup Fails after Shutdown

- The Database Export and Import Utility does not Work with Applications Mode EUL

- Install-level Scripts are not Updated in Existing Instances after Patching

- Issues Specific to Oracle BI Discoverer Plus Relational

- Text Appearing Truncated or Clipped

- Non-ASCII Characters Not Saved Correctly in Title or Text Area

- Canceling Query Causes Discoverer to Hang

- Nonaggregable Values Not Displayed for Scheduled Workbooks

- Migrating Oracle BI Discoverer Plus Relational Worksheets from Oracle BI Discoverer Desktop

- Issues Specific to Oracle BI Discoverer Plus OLAP

- Issues with Applet Download

- Disabled Netscape and Mozilla Browsers

- Tabbing Fails to Synchronize Menus

- Esc Key Fails to Close Certain Dialogs

- Link Tool Works Incorrectly in Some Locales

- Memory Issues when Exporting Extremely Large Graphs

- Issue While Printing Worksheets with Large Data Values

- Issues with Titles and Text Areas

- Errors with JAWS and Format Dialogs

- Issue with Discoverer Plus OLAP Connections on Windows

- Error when Authorizing Multiple Users to Access Discoverer Catalog

- Issues Specific to Oracle BI Discoverer Portlet Provider

- Inability to Turn Off Display of Range Min and Max as Labels

- Issues with Discoverer Portlets in WebCenter

- Issue while Publishing Discoverer WSRP Portlets in Portals Other than Oracle Portal and Oracle WebCenter

- Issue with Portlet Titles in Discoverer WSRP Portlets Published on IBM WebSphere

- Issue with Color and Date Pickers in Discoverer WSRP Portlets

- Worksheet Parameter LOV is not Displayed in Discoverer WSRP Portlets on IBM WebSphere Portal

- Issue with Worksheet Parameter LOV Pop-Up Window in Discoverer WSRP Portlets

- Issues Specific to Oracle BI Discoverer Viewer

- Drill Icons Cannot Be Hidden in Oracle BI Discoverer Viewer

- Error Displaying Page for Multiple SSO Users

- Inability to Disable the Display of Row Numbers

- Issues with Oracle BI Discoverer Viewer Embedded in Frames

- Issue Exporting to PDF Under Certain Circumstances

- Issue When Changing Colors for Oracle BI Discoverer Viewer in Fusion Middleware Control on Mac OS X

- Discoverer Catalog Items Not Visible From UNIX Servers

- Known Bug with JAWS Prevents Drilling Using the Enter Key

- JAWS Does Not Read Asterisks that Precede Fields

- Oracle BI Discoverer Viewer Pages are not Cached by Oracle Web Cache

- Issues Specific to Oracle BI Discoverer EUL Command Line for Java

- Issue with Exported Non-ASCII Data

- Issues Specific to Oracle BI Discoverer Administrator

- Issue with Installation of Video Stores Tutorial

2 Oracle Forms

- General Issues and Workarounds

- Backwards Compatibility with Earlier Releases

- Linux/UNIX Issues and Workarounds

- LD_PRELOAD Setting Required for Signal Chaining Facility

- Check the Reports Engine Logs for FRM-41214

- Forms Builder Does not Launch on Linux RHEL5

- Changing User Permissions

- Oracle Forms Builder Help Menu Displays Incorrect Operating System

- Configuration Issues and Workarounds

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

- WebUtil Client Files Allow Configuration of Destination Directory

- webutil.properties Files Renamed for Different Libraries

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

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

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

- Documentation Errata

- Passing userid in Secure Mode

- JDAPI Programming Example

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

3 Oracle Reports

- General Issues and Workarounds

- Mapping Users and Roles to Reports Application

- Openmotif Library for SUSE Linux 11 Operating Systems

- Configuration Fails While Starting WLS_Reports Server

- Oracle Reports Builder Fails to Open the Data Model from Object Navigator

- Reports Weblayout not Supported on SUSE 10

4 Oracle Portal

- Before You Begin

- General Issues and Workarounds

- Editing a Database Link Requires Password

- Moving Content When Approval Is Enabled Does Not Require Approval

- Firefox and Safari Browsers Do Not Display Tooltips on Oracle Portal Screens

- Non-ASCII URLs Cannot be Decoded in Some Scenarios

- Adding a Zip File with a Non-ASCII Character Name

- Manual Changes to Oracle Portal Default Schema Objects

- Oracle HTTP Server or Web Cache Does Not Start Due to Wallet Permissions

- Error When Creating RCU Portal Schema

- Portal Throws Discoverer Provider is Busy Error Message

- Error When Adding Sample RSS Portlets to a Page

- Internal Error when Using Portal Search With Oracle Text Enabled to Search for Pages

- Cloning Utility Not Supported

- Issue After Creating a Oracle Portal Schema

- Updating Database Tables

- Apply Patch to Address Performance Issue

- Upgrade Issues and Workarounds

- Upgrading Portal 10g SSL Environment to Oracle Portal 11g Release 1 (11.1.1)

- Interoperability Issues and Workarounds

- Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.3

- Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.4

- Creating Webproviders in the Oracle Portal 11g Release 1 (11.1.1) Midtier Interoperability with Oracle Portal Repository 10g Release

- User Interface Issue and Workaround

- Export and Import Issues and Workarounds

- Export and Import Does Not Support Reports Server Components

- Saving the Transport Set

- Error when importing a page group

- Portlet and Provider Issues and Workarounds

- Issue When Accessing Page Portlet Using Federated Portal Adapter

- Error in JPS Portlet After Redeployment

- SSL Support for Oracle Portal Integration Solutions (Microsoft Exchange)

- PDK Issue and Workaround

- Globalization Support Issues and Workarounds

- Text Entry Always Right to Left in BiDi Languages

- Non-ASCII Character Limitations in Oracle Portal

- Multibyte Characters in Log Files

Preface

This preface contains the following sections:

- Audience

- Documentation Accessibility

- Related Documents

- Conventions

Audience

This document is intended for users of Oracle BI Discoverer, Oracle Forms, Oracle Reports, and Oracle Portal.

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 Fusion Middleware Documentation Library 11g Release 1 (11.1.1) at http://docs.oracle.com/cd/E29542_01/pfrd.htm.

- Oracle Technology Network at 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 Oracle Business Intelligence Discoverer

This chapter describes issues associated with Oracle Business Intelligence Discoverer. It includes the following topics:

- General Issues

- Issues Specific to Oracle BI Discoverer Plus Relational

- Issues Specific to Oracle BI Discoverer Plus OLAP

- Issues Specific to Oracle BI Discoverer Portlet Provider

- Issues Specific to Oracle BI Discoverer Viewer

- Issues Specific to Oracle BI Discoverer EUL Command Line for Java

- Issues Specific to Oracle BI Discoverer Administrator

General Issues

This section describes general issues that affect more than one Discoverer component. It includes the following topics:

- Error while Accessing a Discoverer Menu Option in Enterprise Manager

- Issues with Metadata Repository and Oracle Database 10g Release 1

- Compatibility Issues with Required Support Files

- Additional Fonts Required for Non-ASCII Data When Exporting to PDF

- Serif Font Issue in Worksheets

- Query Prediction Requires the Majority of the Query Time

- Word Wrapping Behavior with Oracle BI Discoverer Plus and Oracle BI Discoverer Viewer

- Applet Appears Behind Browser Window

- Issues with Mac OS X Browser and Oracle BI Discoverer Plus

- Issues with Turkish Regional Settings

- Multibyte Characters Rendered as Square Boxes in Exported PDF and Other Formats

- Java Plug-in Not Downloaded Automatically on Firefox

- HTTP 404 Error While Accessing Discoverer on a Remote Machine

- Error While Launching Discoverer Plus Applet on an IPv6 Environment

- Error While Updating the Discoverer Web Services Configuration Parameter

- Exception Logged for Discoverer Web-Based Applications in an Extended Domain

- Issue with Discoverer Application URL in Fusion Middleware Control after a Backup Recovery

- Incorrect Version Number for Discoverer in Fusion Middleware Control 11g

- Oracle BI Discoverer Startup Fails after Shutdown

- The Database Export and Import Utility does not Work with Applications Mode EUL

- Install-level Scripts are not Updated in Existing Instances after Patching

Error while Accessing a Discoverer Menu Option in Enterprise Manager

In Enterprise Manager 11g Fusion Middleware Control, if you select the Catalog > Install from the Discoverer drop down menu, the following ADF error occurs:

ADFC-06003:EL expression
#{viewScope.general_info_dialog.model.regionBound}' for a region TaskFlowId
in binding 'genRegion' evaluated to null, a non-value must be specified"

Workaround

Select Catalog > Manage from the Discoverer menu and then select Catalog > Install. The Install Catalog page appears without any error.

Issues with Metadata Repository and Oracle Database 10g Release 1

When using Oracle Database 10g Release 1 (10.1.x) for the Metadata Repository or after upgrading the Metadata Repository to Oracle Database 10g Release 1, you might see the following error on the Oracle BI Discoverer Plus Connection pages, the Oracle BI Discoverer Viewer Connection pages, and the Public Connection definition page in Fusion Middleware Control:

The connection list is currently unavailable.
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "ORASSO.WWSSO_API_PRIVATE," line 258
ORA-06510: PL/SQL: unhandled user-defined exception
ORA-06512: at "ORASSO.WWSSO_UTL" line 728
ORA-28231: no data passed to obfuscation toolkit
ORA-06512: at line 1 Unable to retrieve connection list

To resolve this issue, make the following changes in the Metadata Repository database:

1. Edit the init%ORACLE_SID%.ora file. This file exists either in the dbs folder or the database folder. For example, in Windows, this file is located in the DB_install_home/database/ folder.

2. Add the following line to this file:
event="10946 trace name context forever, level 36"

3. If an spfile%ORACLE_SID%.ora exists in either the dbs folder or the database folder, rename the file to spfile%ORACLE_SID%.bak. Changes to init%ORACLE_SID%.ora are not loaded if the database server finds an spfile.

4. Log in as a sysadmin.

5. At the SQL prompt, shut down then start up the database server.

6. Restart the Oracle BI Discoverer server using the command opmnctl restartall.

Compatibility Issues with Required Support Files

The Oracle Database and other Oracle database client software (for example, SQL*Plus, the database export utility) use Oracle Required Support Files (RSF).

Oracle BI Discoverer also uses Oracle Required Support Files (RSF), specifically RSF version 11.1.0.7. This version of the Oracle Required Support Files is installed during Oracle BI Discoverer installation.

Note that the Required Support Files version 11.1.0.7 is incompatible with earlier versions of Oracle Database 10g. So if the machine on which you install Oracle BI Discoverer already has a version of Oracle Database 10g or database client software that is earlier than 11.1.0.7, there will be compatibility issues. For example, if you install Oracle BI Discoverer and attempt to run a version of SQL*Plus earlier than 11.1.0.7, then the following error is displayed:

ORA-12557 TNS: protocol adapter not loadable

To avoid the compatibility issues, upgrade Oracle Database 10g or database client software on the machine to the same version (11.1.0.7) as the version of the Required Support Files that were installed with Oracle BI Discoverer.

This issue does not exist for Oracle9i Database Server.

Serif Font Issue in Worksheets

You might notice unsightly font issues when using a non-English locale such as Czech. For example, when a worksheet uses a serif font, text in that worksheet might be displayed incorrectly on the screen and in printouts.

To work around this issue, update the file that maps the serif fonts. The name of this file differs depending on the locale in use. When you use Oracle BI Discoverer Plus Relational or Plus OLAP in English, the file is named file.properties. If you use Oracle BI Discoverer in a non-English locale, then the file name includes the code for the locale, such as file.properties.cs for Czech.

Update the mapping file with the following information:

serif.0=Times New Roman,EASTEUROPE_CHARSET serif.1=WingDings,SYMBOL_CHARSET,NEED_CONVERTED serif.2=Symbol,SYMBOL_CHARSET,NEED_CONVERTED

Consult the following Sun Web site for additional information about fonts:

http://java.sun.com/j2se/1.3/docs/guide/intl/addingfonts.html

Additional Fonts Required for Non-ASCII Data When Exporting to PDF

If you are running Oracle BI Discoverer Plus Relational or Plus OLAP on a Macintosh or Linux client machine, you must add the appropriate font files to your client machine to allow exported PDF files to display non-ASCII data correctly.

These font files include Albany fonts with names such as ALBANWTJ.TTF and ALBANWTK.TTF. The files are stored in the /utilities/fonts directory on the CD-ROM or DVD for the Oracle Application Server Metadata Repository Upgrade Assistant.

To install the additional required fonts:

1. Navigate to the /utilities/fonts directory on the CD-ROM or DVD for the OracleAS Metadata Repository Upgrade Assistant.

2. Copy the appropriate Albany TTF file from the /utilities/fonts directory to the plug-in directory in the $jdk/jre/lib/fonts directory on the Macintosh or Linux client machine.

Query Prediction Requires the Majority of the Query Time

When using Oracle BI Discoverer with a relational data source, you can predict the time that is required to retrieve information by setting the value of the QPPEnable preference to 1. However, in some circumstances, the majority of the time taken to retrieve information is consumed by the prediction activity itself.

To work around this issue, set the value of the QPPObtainCostMethod preference to 0 (use the EXPLAIN PLAN statement to predict query times) rather than to 1 (use dynamic views to predict query times).

For more information about setting preferences, see the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

Word Wrapping Behavior with Oracle BI Discoverer Plus and Oracle BI Discoverer Viewer

To use word wrap settings correctly, you must understand how they are designed for Oracle BI Discoverer:

- Oracle BI Discoverer Plus: Word wrap settings that you make in Oracle BI Discoverer Plus are saved in the worksheet and affect the display of worksheets in Oracle BI Discoverer Plus and when printing to PDF.

- Oracle BI Discoverer Viewer: Word wrap settings that you see in the Print Settings dialog work as follows:

- The word wrap settings do not affect the display of worksheets in Oracle BI Discoverer Viewer.

- For relational data:

- The word wrap settings do affect the printing of worksheets to PDF.

- If the Always wrap text when size exceeds column width box is checked, then the print settings in Oracle BI Discoverer Viewer do override the settings made in a worksheet in Oracle BI Discoverer Plus Relational for printing to PDF.

- If the Always wrap text when size exceeds column width box is not checked, then the print settings in Oracle BI Discoverer Viewer do not override the settings made in a worksheet in Oracle BI Discoverer Plus Relational for printing to PDF.

- For OLAP data:

- The word wrap settings do not affect the printing of worksheets to PDF.

- Regardless of whether the Always wrap text when size exceeds column width check box is selected, the print settings in Oracle BI Discoverer Viewer never override the settings made in a worksheet in Oracle BI Discoverer Plus OLAP for printing to PDF.

Applet Appears Behind Browser Window

When you use Microsoft Internet Explorer, the Oracle BI Discoverer Plus Relational or Plus OLAP applet initialization and download dialog appears behind the browser window from which it was launched. After the applet is downloaded and initialized, it appears in front of the browser window from which it was launched.

To work around this issue:

- Use a browser other than Internet Explorer, such as Netscape Navigator or Mozilla Firefox.

- Use the Oracle BI Discoverer Plus URL parameter _plus_popup=false, which is documented in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

Issues with Mac OS X Browser and Oracle BI Discoverer Plus

The following are issues that you might encounter when you use the Safari browser on Mac OS X with Oracle BI Discoverer Plus Relational or Plus OLAP:

- If you resize the browser window in the applet, then some parts of the content might be clipped. To work around this problem, always maximize the browser window for the applet when working with Mac OS X.

- Keyboard combinations (also known as mnemonics) do not work in Oracle BI Discoverer Plus Relational and Plus OLAP.
For example, you cannot press Alt+F to access the File menu.

- In the Share Workbooks dialog of Oracle BI Discoverer Plus Relational, the leading characters of the "Shared:" list are clipped. In other words, the left edge of the list is truncated. For example, if you shared a workbook with DISCODEV, then you will only see SCODEV in the list. The title for the list is also truncated such that you see only the vertical line of the "d" in "Shared" and the colon (that is, "l:").
The dialog continues to work as expected, but you might have difficulty reading the names in the "Shared:" list.

This issue has no workaround.

Issues with Turkish Regional Settings

Because of Sun JRE 1.4 bug 4688797, you might encounter issues when connecting to a database schema from a computer that has Turkish regional settings. You will encounter the issue when you attempt to connect to a database schema with a user name that contains certain letters, such as the letter 'I' or 'i', for example, in "bibdemo". See the Sun JRE bug for information on the letters that are affected.

To work around this issue, either do not use Turkish regional settings or use a user name that does not contain the affected letters.

Multibyte Characters Rendered as Square Boxes in Exported PDF and Other Formats

When you export a workbook to PDF and other formats, multibyte characters (for example, Korean, Japanese, and Chinese characters) appear as square boxes.

To work around this issue, copy the following Albany fonts from ORACLE_HOME/jdk/jre/lib/fonts to the fonts folder of your JDK (Oracle JRockit or Sun) within the MW_HOME directory. For example, if you are using Sun JDK, you must copy the fonts to MW_HOME/jre/jdk160_11/lib/fonts.

- AlbanWTJ.ttf

- AlbanWTK.ttf

- AlbanWTS.ttf

- AlbanWTT.ttf

- ALBANYWT.ttf

Java Plug-in Not Downloaded Automatically on Firefox

When you attempt to connect to Discoverer Plus by using the Mozilla Firefox browser on a machine that does not have Java 1.6 installed, the browser does not download the JRE 1.6 plug-in automatically. Instead, the browser displays the following message:

Additional plugins are required to display this page...

You must download the JRE 1.6 plug-in (by clicking the Install Missing Plugin link) and install it manually.

HTTP 404 Error While Accessing Discoverer on a Remote Machine

When you attempt to connect to Discoverer Plus, occasionally, the browser returns an HTTP 404 (File Not Found) error.

The page loads correctly when you refresh the browser a few times.

Error While Launching Discoverer Plus Applet on an IPv6 Environment

If the Web tier is on an IPv6 machine, when you start Discoverer Plus, the following error message might be displayed:

Attempt1. RMI protocol over JRMP transport: Connection refused to host: DiscoServerMahcineName;nested exception is:
@ java.net.ConnectionException: Connection timed out

To work around this issue, in the System MBean Browser of Fusion Middleware Control, change the TransportProtocols attribute of the Plus Config MBean to "jrmp,http" (or "jrmp,https" if Discoverer Plus is accessed by using secure HTTP).

Error While Updating the Discoverer Web Services Configuration Parameter

When you update the web services configuration parameter (Maximum Sessions) using the Discoverer Web Services Configuration page of Fusion Middleware Control and click Apply, the following error message is displayed:

Applying changes - Failed.
Exception caught:

You can ignore the error message because the changes are applied even if the exception is thrown. Alternatively, you can update the MaxSessions attribute of the WebServicesConfig MBean in the System MBean Browser of Fusion Middleware Control.

Exception Logged for Discoverer Web-Based Applications in an Extended Domain

When you extend a domain and add Discoverer application in a remote machine, you may see the following exception in the WebLogic Server log:

java.lang.IllegalArgumentException: ODL-52057: The handler 'disco-server-handler' is not defined.

To work around this issue, modify the log_handlers and loggers elements in the logging.xml file located in the DOMAIN_HOME/config/fmwconfig/servers/WLS_DISCO folder of the machine where the domain exists.

In the log_handlers section, add the handlers as follows:

<log_handler name='discoverer-handler'
class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path'
value='${domain.home}/servers/${weblogic.Name}/logs/discoverer/diagnostic.log'
/>
<property name='maxFileSize' value='1048576'/>
<property name='maxLogSize' value='10485760'/>
<property name='format' value='ODL-Text'/>
<property name='useSourceClassAndMethod' value='false'/>
</log_handler>

<log_handler name='disco-server-handler'
class='oracle.core.ojdl.logging.ODLHandlerFactory'>
<property name='path'
value='${domain.home}/servers/${weblogic.Name}/logs/discoverer/server/diagnost
ic.log'/>
<property name='maxFileSize' value='1048576'/>
<property name='maxLogSize' value='10485760'/>
<property name='format' value='ODL-Text'/>
</log_handler>

In the loggers sections, add the following elements:

<logger name='ORACLE.DISCOVERER.VIEWER' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.PORTLET_PROVIDER' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.MODEL' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.WEB_SERVICES' level='TRACE:32'
useParentHandlers='false'>
<handler name='discoverer-handler'/>
<handler name='odl-handler'/>
</logger>
<logger name='ORACLE.DISCOVERER.SERVER' level='TRACE:32'
useParentHandlers='false'>
<handler name='disco-server-handler'/>
<handler name='odl-handler'/>
</logger>

After adding these elements, save the logging.xml file, and restart the Administration Server and Discoverer Managed Servers.

Issue with Discoverer Application URL in Fusion Middleware Control after a Backup Recovery

When you recover the Oracle BI Discoverer middle tier from a backup, the Discoverer application URL in the Discoverer Home page of Fusion Middleware Control point to a wrong location.

You must configure the application URLs that appear on the Oracle BI Discoverer Home page in Fusion Middleware Control after recovering the Oracle BI Discoverer middle tier from a backup.

For more information, see "How to configure application URLs displayed on the Fusion Middleware Control Discoverer Home page" in the Oracle Business Intelligence Discoverer Configuration Guide.

Incorrect Version Number for Discoverer in Fusion Middleware Control 11g

In Fusion Middleware Control 11g, the Enterprise Manager Fusion Middleware Control pages display wrong version number (11.1.1.2.0) for the Oracle BI Discoverer application. The correct version number for Oracle BI Discoverer is 11.1.1.4.0.

Oracle BI Discoverer Startup Fails after Shutdown

When you first start up the Discoverer application from Oracle Enterprise Manager Fusion Middleware Control or Oracle WebLogic Administration Console after shutting down the application instance, the startup fails with error logs.

To work around this issue, start the Discoverer application again. The second time the application starts without any error message.

The Database Export and Import Utility does not Work with Applications Mode EUL

You cannot use the standard database export and import utilities to export or import the database, EUL tables and database objects referenced by the Applications Mode EUL definitions. The standard database export and import utility can be used only for standard EUL definitions.

To work around this issue, use the Discoverer Export Wizard in Discoverer Administrator to export EUL objects to an EUL export file (*.EEX). After exporting the EUL objects, you can import the .EEX file using the Discoverer Import Wizard.For more information, see "Creating and Maintaining End User Layers" in Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Discoverer.

Install-level Scripts are not Updated in Existing Instances after Patching

When you upgrade Oracle Discoverer 11gR1 PS1 to 11gR1 PS2 or 11gR1 PS3, the patch will be installed in the ORACLE_HOME folder. Therefore, script changes in the new patch set will not be available for existing Oracle Discoverer instances, which are located in the ORACLE_INSTANCE folder. However, new instances that are created after the patch upgrade will be updated.

To work around this issue, after a patch upgrade manually copy the new scripts to the existing ORACLE_INSTANCE folders. For example, copy the new discenv.sh script file from ORACLE_HOME to the ORACLE_INSTANCE/Discoverer/Discoverer_instance-name/util/ folder.

For more information about Discoverer file locations, see "Oracle BI Discoverer Configuration Files" in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

Issues Specific to Oracle BI Discoverer Plus Relational

This section describes issues that are specific to Oracle BI Discoverer Plus Relational. It includes the following topics:

- Text Appearing Truncated or Clipped

- Non-ASCII Characters Not Saved Correctly in Title or Text Area

- Canceling Query Causes Discoverer to Hang

- Nonaggregable Values Not Displayed for Scheduled Workbooks

- Migrating Oracle BI Discoverer Plus Relational Worksheets from Oracle BI Discoverer Desktop

Text Appearing Truncated or Clipped

When you run Oracle BI Discoverer Plus Relational with Sun Java Plug-in 1.4.2_06, the Browser Look and Feel, and an Asian language (such as Korean or Chinese), you might notice that static text and text in buttons in the user interface appears truncated or clipped. To work around this issue, do one of the following:

- Change the Look and Feel to either Plastic or System.

- Use JInitiator 1.3.1.17 instead of the Sun Java Plug-in.

- Install Sun Java Plug-in version 1.4.2_10 or higher.

Non-ASCII Characters Not Saved Correctly in Title or Text Area

When you save a new workbook in Oracle BI Discoverer Plus, any text characters beyond the standard ASCII characters are not saved correctly when all the conditions that are described in the following list are met:

- You are logged in as an Oracle e-Business Suite user.

- The language for the computer is not English.

- Oracle BI Discoverer Plus is running against an Oracle e-Business Suite database that does not have that non-English language installed.

This issue has no workaround.

Canceling Query Causes Discoverer to Hang

If you cancel a query that is running in Oracle BI Discoverer Plus Relational, then you are prompted to either choose YES to undo the changes or NO to show a blank sheet. If you choose YES, then Oracle BI Discoverer Plus Relational hangs and you must close the window and restart.

To work around this issue, choose NO to show a blank worksheet. You can then refresh the sheet and continue working.

Nonaggregable Values Not Displayed for Scheduled Workbooks

Oracle BI Discoverer Plus Relational does not display nonaggregable values for scheduled workbooks. In other words, Oracle BI Discoverer Plus Relational processes scheduled workbooks as if you selected the Show values that cannot be aggregated as: <Non-aggregable label> option in the Worksheet Properties dialog: Aggregation tab.

Nonaggregable values include those based on the following SQL functions:

- A CASE SQL statement

- A DECODE SQL statement

- A PL/SQL function

- A DISTINCT SQL statement

- An analytic function

Migrating Oracle BI Discoverer Plus Relational Worksheets from Oracle BI Discoverer Desktop

If you use Oracle BI Discoverer Plus Relational to open a worksheet that was created using Oracle BI Discoverer Desktop Version 9.0.4 (or earlier), the size of the title area for that worksheet defaults to two lines in height. A title height of two lines might be a problem if a worksheet title requires more than or less than two lines. If you want to change the size of the title area, you must resize the title area manually and save the worksheet.

To resize the title area for a worksheet, open the worksheet and drag the bar at the bottom of the title area pane up or down.

Issues Specific to Oracle BI Discoverer Plus OLAP

This section describes issues that are specific to Oracle BI Discoverer Plus OLAP. It includes the following topics:

- Issues with Applet Download

- Disabled Netscape and Mozilla Browsers

- Tabbing Fails to Synchronize Menus

- Esc Key Fails to Close Certain Dialogs

- Link Tool Works Incorrectly in Some Locales

- Memory Issues when Exporting Extremely Large Graphs

- Issue While Printing Worksheets with Large Data Values

- Issues with Titles and Text Areas

- Errors with JAWS and Format Dialogs

- Issue with Discoverer Plus OLAP Connections on Windows

- Error when Authorizing Multiple Users to Access Discoverer Catalog

Issues with Applet Download

There may be Oracle Business Intelligence Discoverer Plus applet download issues when caching has been enabled in the Sun Java Plug-In.

To avoid these issues, disable caching in the plug-in.

Disabled Netscape and Mozilla Browsers

When you are running Netscape 7.x or Mozilla browsers, the Netscape and Mozilla Mail clients and Web browser may become disabled when Oracle BI Discoverer Plus OLAP modal dialogs are displayed.

Dismissing the Oracle BI Discoverer Plus OLAP dialogs resumes normal operation for the Netscape and Mozilla tools.

Tabbing Fails to Synchronize Menus

When you use the Tab key to select items in a worksheet, the menus do not always synchronize to reflect the currently selected item.

This issue has no workaround.

Esc Key Fails to Close Certain Dialogs

The Esc key does not close the following dialogs: Totals, New Total, Parameter, and Manage Catalog.

Instead of using the Esc key, click the Close or OK button.

Link Tool Works Incorrectly in Some Locales

The Link tool, which enables users to drill out to external URLs from a crosstab cell, might not work correctly in all locales due to URL encoding issues.

This issue has no workaround.

Memory Issues when Exporting Extremely Large Graphs

Exporting extremely large graphs can cause memory issues, requiring a restart of the Oracle BI Discoverer Plus OLAP session.

This issue has no workaround.

Issue While Printing Worksheets with Large Data Values

When printing a worksheet that contains large numbers in the data cells, the string ####### may be printed instead of the actual numbers.

This issue has no workaround.

Issues with Titles and Text Areas

The following issues exist with titles and text areas:

- Nonempty titles and text areas are printed even if they are hidden in the worksheet.
This issue has no workaround.

- When you set the title or text area background to green and export the worksheet to an HTML file, the background is incorrectly set to red in the exported file.
This issue has no workaround.

Errors with JAWS and Format Dialogs

When you use JAWS, you will notice errors when you attempt to format graphs and crosstabs using the Format dialogs.

This issue has no workaround.

Issue with Discoverer Plus OLAP Connections on Windows

When you connect to Oracle BI Discoverer Plus OLAP on a Windows platform by providing only the TNS alias for the database string, errors will occur.

To work around this issue, add the following variable in the DOMAIN_HOME\bin\setDomainEnv.cmd file.

PATH=$ORACLE_HOME\BIN;%PATH%

Error when Authorizing Multiple Users to Access Discoverer Catalog

When you authorize multiple users or roles to access the Discoverer Catalog through Oracle Enterprise Manager Fusion Middleware Control, an error occurs and the authorization fails.

To work around this issue, in the Authorize Users window of the Fusion Middleware Control, select only one user at a time from the Available Users and Roles list. If you have multiple users, repeat the authorization procedure for each user. For more information, see "Authorizing user and role access to the Discoverer Catalog" in Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

Issues Specific to Oracle BI Discoverer Portlet Provider

This section describes issues that are specific to Oracle BI Discoverer Portlet Provider. It includes the following topics:

- Inability to Turn Off Display of Range Min and Max as Labels

- Issues with Discoverer Portlets in WebCenter

- Issue while Publishing Discoverer WSRP Portlets in Portals Other than Oracle Portal and Oracle WebCenter

- Issue with Portlet Titles in Discoverer WSRP Portlets Published on IBM WebSphere

- Issue with Color and Date Pickers in Discoverer WSRP Portlets

- Worksheet Parameter LOV is not Displayed in Discoverer WSRP Portlets on IBM WebSphere Portal

- Issue with Worksheet Parameter LOV Pop-Up Window in Discoverer WSRP Portlets

Inability to Turn Off Display of Range Min and Max as Labels

In the Display Options of a gauge portlet, the Minimum Value and Maximum Value range labels are selected but are also disabled so that you cannot deselect the display of those values. The values for the minimum and the maximum appear at the ends of every gauge in the set except for those gauges where the value to be gauged is out of the range of the minimum and the maximum values. For those gauges where the value to be displayed exceeds the range of the minimum and the maximum values, the gauge will automatically adjust to accommodate the value.

This issue has no workaround.

Issues with Discoverer Portlets in WebCenter

The following issues exist for Discoverer portlets displayed in Oracle WebCenter.

- When a Worksheet portlet is displayed in Oracle WebCenter, the links to navigate to the next set of records does not work.

- When a List of Worksheets portlet is displayed in Oracle WebCenter, the Expand All Icons link does not work.

To work around these issues, set the RenderPortletInIFrame attribute of the portlet tag to TRUE. For more information, see "Setting Attribute Values for the Portlet Tag" in Oracle Fusion Middleware Developer's Guide for Oracle WebCenter.

Issue while Publishing Discoverer WSRP Portlets in Portals Other than Oracle Portal and Oracle WebCenter

When you publish Discoverer WSRP Portlets in portals other than Oracle Portal and Oracle WebCenter (such as Oracle WebLogic Portal and IBM WebSphere Portal), the pop-up windows for input selection will have the same page layout as the portal page with all navigation options. If you select any of these navigation options, the current portlet state will be lost. You might need to start publishing the portlet from the beginnng.

The issue has no workaround.

Issue with Portlet Titles in Discoverer WSRP Portlets Published on IBM WebSphere

You cannot dynamically change the portlet title of a Discoverer WSRP portlet in IBM WebSphere after it is published. Static title is rendered in the portal for each portlet instance.

To work around this issue, set a meaningful title for the portlet by editing the title using the Set Title or Description option in the WebSphere portal. For more information about changing the title of a portlet, see WebSphere documentation.

Issue with Color and Date Pickers in Discoverer WSRP Portlets

The Color and Date pickers in Discoverer WSRP Portlets do not work on portals other than Oracle WebCenter.

On portals such as Oracle Portal, Oracle WebLogic Portal and IBM WebSphere, to workaround this issue, set the value of the configuration parameter useInlineUIXPicker to true. The default value of this parameter is false. When you set the useInlineUIXPicker parameter to true, set the color and date as follows:

- Inline color pickers are enabled in the Gauges Selection page and you can select a color from the palette.

- You cannot select the color using the Format option of the Personalize menu of the worksheet. Use the Analyze option in the portlet window to change the color.

- The Date picker in the Refresh option will not be available. Enter the date manually.

Worksheet Parameter LOV is not Displayed in Discoverer WSRP Portlets on IBM WebSphere Portal

The Worksheet Parameter LOV icon is not displayed when you publish Discoverer WSRP portlets in IBM WebSphere portal.To work around this issue, enter parameter values manually.

Issue with Worksheet Parameter LOV Pop-Up Window in Discoverer WSRP Portlets

In Oracle Portal and Oracle WebLogic Portal, when you select values from the parameter LOV from a worksheet portlet published by using the Discoverer WSRP Portlet producer, the pop-up window is not getting closed on selection of values.You must explicitly close the pop-up window after selection of values.

Issues Specific to Oracle BI Discoverer Viewer

This section describes issues that are specific to Oracle BI Discoverer Viewer. It includes the following topics:

- Drill Icons Cannot Be Hidden in Oracle BI Discoverer Viewer

- Error Displaying Page for Multiple SSO Users

- Inability to Disable the Display of Row Numbers

- Issues with Oracle BI Discoverer Viewer Embedded in Frames

- Issue Exporting to PDF Under Certain Circumstances

- Issue When Changing Colors for Oracle BI Discoverer Viewer in Fusion Middleware Control on Mac OS X

- Discoverer Catalog Items Not Visible From UNIX Servers

- Known Bug with JAWS Prevents Drilling Using the Enter Key

- JAWS Does Not Read Asterisks that Precede Fields

- Oracle BI Discoverer Viewer Pages are not Cached by Oracle Web Cache

Drill Icons Cannot Be Hidden in Oracle BI Discoverer Viewer

The pref.txt file contains a setting called ShowDrillIcon, which is not functioning properly. If you set ShowDrillIcon to False, then drill icons are still displayed in Oracle BI Discoverer Viewer.

The issue has no workaround.

Error Displaying Page for Multiple SSO Users

When an Oracle Single Sign-On (SSO) user tries to view a worksheet from a List of Worksheets Portlet by using the same browser window that is already being used by an SSO user to view that worksheet, the second user sees the following error message: "The page cannot be displayed".

To work around this issue, start a new browser session and view the worksheet.

Inability to Disable the Display of Row Numbers

Oracle BI Discoverer Viewer no longer offers the ability to disable the display of row numbers in a tabular worksheet.

Issues with Oracle BI Discoverer Viewer Embedded in Frames

Users might see JavaScript errors such as "Access Denied" or other unexpected behavior when both of the following conditions are met:

- When Oracle BI Discoverer Viewer is embedded in an IFRAME tag.

- When the domain of the server that hosts the HTML page with the IFRAME tag is different from the domain of the Oracle BI Discoverer server that is running Oracle BI Discoverer Viewer.

Use one of the following workarounds for this issue:

- Run the Oracle BI Discoverer server and the server that hosts the HTML page with the IFRAME tag in the same domain.

- Alter the Common2_2_20.js file on the Oracle BI Discoverer server using the following steps:

1. Use Fusion Middleware Control to stop all services on the middle tier for Oracle Business Intelligence.

2. Make a backup copy of the Common2_2_20.js file from the following directory:
domain\servers\managed_server\stage\discoverer\release\discoverer\discoverer.war\cabo\jsLib

domain is the path of directory that contains the domain.

managed_server is the name of the managed server on which the Discoverer application is deployed.

release is the release number of Discoverer. For example, 11.1.1.1.0.

3. Edit the Common2_2_20.js file and replace all occurrences of "parent._pprSomeAction" with "window._pprSomeAction".

4. Use Fusion Middleware Control to start all services on the middle tier for Oracle Business Intelligence.

5. Clear the browser cache on the client machine so that the new Common2_2_20.js file will be used.

Issue Exporting to PDF Under Certain Circumstances

If you are using Oracle BI Discoverer Viewer with Microsoft Internet Explorer, you might encounter an error message when you try to export to PDF a worksheet that is named with non-ASCII characters, a space, and a number. The export fails and you will see a message similar to the following one:

No %PDF- in a file header

Use one of the following methods to work around this issue:

- Use a browser other than Internet Explorer, such as one from Netscape or Mozilla.

- Remove the space between the non-ASCII characters and the number, or remove the number altogether.

- Continue to use Internet Explorer and leave the space in the worksheet name, but follow these steps:

1. Start the Adobe Reader.

2. From the Edit menu, choose Preferences, then click Internet.

3. Clear the Display PDF in browser box.

Issue When Changing Colors for Oracle BI Discoverer Viewer in Fusion Middleware Control on Mac OS X

You can use Fusion Middleware Control to change the look and feel of Oracle BI Discoverer Viewer. That page contains a color chooser, or palette. If you use Fusion Middleware Control on Mac OS X with the Safari browser, then the page does not correctly enter the color code when you select a color from the palette.

To work around this issue, you can either use the Firefox browser or you can enter a color code directly.

The color codes are standard HTML hexadecimal color codes. You can enter one of the 49 colors that are available in the color palette, or you can enter any valid HTML hexadecimal color code.

The following list provides examples of colors with their codes:

white #FFFFFF
grey #CCCCCC
black #000000
pink #FFCCCC
red #FF0000
light yellow #FFFFCC
yellow #FFFF00
light green #99FF99
dark green #00CC00
light blue #66FFFF
dark blue #3333FF
lavender #FF99FF
purple #CC33CC

Discoverer Catalog Items Not Visible From UNIX Servers

You might encounter issues when trying to see items in the Discoverer Catalog when using Oracle BI Discoverer Viewer with OLAP data on UNIX servers.

You can resolve this issue on the middle-tier machine where Oracle BI Discoverer runs by performing the following steps.

To check whether the time zone variable is set:

1. Open a shell prompt.

2. Type echo $TZ to display the time zone setting.

If no value is displayed, then the time zone has not been set.

To set the time zone variable:

1. Open a shell prompt.

Note:

The UNIX user that sets the TZ variable must be the same UNIX user that installed Oracle Business Intelligence.

2. If you do not know which shell you are using, type $echo $SHELL to display the name of the current shell.

3. Set the time zone as appropriate.
For example, to set the time zone variable for US/Pacific time:

- For the Bourne, Bash, or Korn shell, type export TZ=US/Pacific

- For the C shell, type setenv TZ US/Pacific

Note:

Consult the shell documentation for the appropriate values.

Known Bug with JAWS Prevents Drilling Using the Enter Key

Oracle BI Discoverer can be used in conjunction with assistive technologies such as the JAWS screen reader. However, a bug in JAWS prevents the drilling feature from working correctly in Oracle BI Discoverer Viewer when querying a relational data source.

Assume that you use the keyboard to navigate to the drill icon beside an item in the worksheet header. When you press the Enter key to drill on that header item, the Drill page should be displayed as described in the "Worksheet Display page: (Page level tools and controls)" topic in the Help system and the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Discoverer Viewer).

However, when JAWS is running, the Drill page is not displayed. Instead, the Drill popup menu is displayed. It is not possible to select items from this popup menu by using the keyboard, and JAWS does not read the items on the popup menu.

This issue has no workaround.

JAWS Does Not Read Asterisks that Precede Fields

In Oracle BI Discoverer Viewer, an asterisk that precedes a text field indicates that the user is required to enter a value into that text field. The JAWS screen reader does not read an asterisk that precedes a required text field and does not otherwise indicate that the field is required.

This issue has no workaround.

Oracle BI Discoverer Viewer Pages are not Cached by Oracle Web Cache

When using Oracle BI Discoverer with Oracle Web Cache, note the following:

- When Oracle Single Sign-On is enabled, Oracle Web Cache does not cache Oracle BI Discoverer Viewer pages, regardless of whether they are accessed using a public connection or a private connection.

- If an Oracle BI Discoverer Viewer page is accessed directly through a URL and the URL contains URL parameters that specify login details (for example, user name, database name), then Oracle Web Cache does not cache the page. For example, Oracle Web Cache does not cache worksheet "Sheet 1" in workbook "Workbook 2" that is displayed by using the following URL:
http://<host.domain>:<port>/discoverer/viewer?us=video5&db=db1&eul=VIDEO5&wbk=Workbook+2&ws=Sheet+1

Note:

In the example above, us= specifies the database user name, and db= specifies the database name.

However, Oracle Web Cache does cache worksheet "Sheet 1" in workbook "Workbook 2" if a user logs in manually to Oracle BI Discoverer Viewer by using the same login details, and navigates to the worksheet.

- You must increase the delays for Oracle BI Discoverer Viewer by at least 60 seconds for Oracle BI Discoverer Viewer to properly cache workbooks with Oracle Web Cache.
For more information, see "How to configure Discoverer Viewer to enable maximum caching" in the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Discoverer.

Issues Specific to Oracle BI Discoverer EUL Command Line for Java

This section describes issues that are specific to Oracle BI Discoverer EUL Command Line for Java.

Issue with Exported Non-ASCII Data

When you export multibyte or Eastern European data (such as the names of items and business areas in Japanese or Russian characters) from Oracle BI Discoverer EUL Command Line for Java on a platform other than Windows, the exported data is corrupted.

To work around this issue, edit the discwb.sh file that is located in the ORACLE_HOME/discoverer directory before exporting. Change the character set value in the NLS_LANG variable to UTF8.

For example, if the original setting of the variable is:

NLS_LANG="GERMAN_GERMANY.WE8ISO8859P1"

Change the setting to:

NLS_LANG="GERMAN_GERMANY.UTF8"

Issues Specific to Oracle BI Discoverer Administrator

This section describes issues that are specific to Oracle BI Discoverer Administrator. It includes the following topic:

- Issue with Installation of Video Stores Tutorial

Issue with Installation of Video Stores Tutorial

Before installing the video stores tutorial in Oracle Database 10g Enterprise Edition Release 2 (version 10.2.0.1 and higher), you must manually create the VIDEO5 user. If you attempt to install the video stores tutorial in Oracle Database 10g Enterprise Edition Release 2, then the installation will fail if the VIDEO5 user does not already exist. To work around this issue:

1. Create the VIDEO5 user manually by completing these steps:

1. Access Oracle Database 10g with SQL*Plus, Enterprise Manager, or any SQL command line tool.

2. Create the VIDEO5 user.

3. Grant CONNECT and RESOURCE privileges to the VIDEO5 user.

For more information about creating users and granting privileges, see the Oracle Database SQL Reference or your DBA

2. Connect to Discoverer Administrator as the EUL owner and install the tutorial. You must enter the VIDEO5 user password during installation.
For information about installing the video stores tutorial, see the Oracle Fusion Middleware Administrator's Guide for Oracle Business Intelligence Discoverer.

2 Oracle Forms

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

- General Issues and Workarounds

- Configuration Issues and Workarounds

- Documentation Errata

General Issues and Workarounds

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

- Backwards Compatibility with Earlier Releases

- Linux/UNIX Issues and Workarounds

- Oracle Forms Builder Help Menu Displays Incorrect Operating System

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 and prior releases, you can use the Upgrade Assistant. For more information, see the Oracle Fusion Middleware Upgrade Planning Guide and Oracle Fusion Middleware Upgrade Guide for Oracle Portal, Forms, Reports, and Discoverer.

Additional information about backwards compatibility is included in My Oracle Support Note 113987.1 at: http://myoraclesupport.oracle.com

Regardless from which version of Oracle Forms you are upgrading, you will need to recompile your applications and restart Oracle Forms.

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.

When Forms and Reports are configured in different instances, set the correct ORACLE_HOME and ORACLE_INSTANCE values 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.

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.

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.

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.

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

- Forms Builder Does not Launch on Linux RHEL5

- Changing User Permissions

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.

Forms Builder Does not Launch on Linux RHEL5

On 32-bit Linux computers, when attempting to launch Forms Builder using the command frmbld.sh in $ORACLE_INSTANCE/bin/, the following error message is displayed:

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

As a workaround, create a symlink named libXm.so.3 to libXm.so.4 in ORACLE_INSTANCE/bin/xm and add it to the LD_LIBRARY_PATH. Or install OpenMotif package using the command rpm -i openmotif22-2.2.3-18.i386.rpm

Changing User Permissions

The 11g installation sets the permissions of the files so that only the user who installed 11g can run the executables. For more information, refer to Installing as a Non-Default User on Unix Operating Systems in Oracle Fusion Middleware Forms and Reports System Requirements and Specifications guide.

Oracle Forms Builder Help Menu Displays Incorrect Operating System

When you run Oracle Forms Builder on Microsoft Windows x64 (64-Bit) systems, the operating system is displayed as Microsoft Windows (32-Bit) when you select the About Forms Builder option from the Help menu.

Workaround

Ignore the message as this does not affect the functionality.

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

- WebUtil Client Files Allow Configuration of Destination Directory

- webutil.properties Files Renamed for Different Libraries

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

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

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

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.

WebUtil Client Files Allow Configuration of Destination Directory

WebUtil downloads install.syslib libraries into the bin directory of the JRE or JVM on Windows and into the lib directory of JRE on Linux. 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.

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.

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.

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://testform.us.example.com:8888/forms/java/js2frm1.html" name="fr2"
frameborder="0">
<frame noresize="noresize"
src="http://testform.us.example.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">

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.

Documentation Errata

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

- Passing userid in Secure Mode

- JDAPI Programming Example

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

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.

JDAPI Programming Example

The JDAPI Programming Example in the Forms Developer Online Help must be updated to the following code:

import java.io.File;
import java.io.PrintWriter;
import java.io.FileWriter;
import java.text.MessageFormat;

import oracle.forms.jdapi.*;

/**
* Dumps passed forms JdapiObjects to an output stream as text.
*
* Set command line options for more output, else only the
* basic form tree structure will be dumped.
*
* See printUsage for command line options.
*/
public class FormDumper
{
/**
* Need this to parse the command line options
*
* The string represents valid command options as detailed in the
* Getopt class
*/

boolean m_dumpAllProps = false;
boolean m_dumpBoolProps = false;
boolean m_dumpNumProps = false;
boolean m_dumpTextProps = false;
boolean m_dumpPropNames = false;
String m_dumpPath = null;
/**
* Output stream, default to STDOUT */
private PrintWriter m_out = new PrintWriter(System.out, true);

/**
* Use this to indent children
*/
private String m_indentation = "";

/**
* Constructor
*/
public FormDumper()
{

}

/**
* Special constructor that does not take command line arguments.
*
* @param out The output writer where to send dump information.
*/
public FormDumper(PrintWriter out)
{
m_out = out;
m_dumpAllProps = true;
m_dumpBoolProps = true;
m_dumpNumProps = true;
m_dumpTextProps = true;
m_dumpPropNames = true;
}

/**
* Set the dump path.
*
* @param path The file where the dumper must send the information
*/
public void setDumpPath(String path)
{
m_dumpPath = path;
}

/**
* Indirect output
*/
public void println(String s)
{
m_out.println(s);
}

/**
* Dump a form to the output stream
*/
public void dumpForm(String filename)
throws Exception
{
FormModule fmb = FormModule.open(filename);
System.out.println("Dumping module " + fmb.getName());

if (m_dumpPath != null)
{
// use this form's FILE name to name the dump file
String thisFormName = new File(filename).getName();
thisFormName = thisFormName.substring(0, (thisFormName.length()-4));
StringBuffer dmpFilename = new StringBuffer();
dmpFilename.append(m_dumpPath);

if (!dmpFilename.toString().endsWith("/"))
{
dmpFilename.append("/");
}
dmpFilename.append(thisFormName);

m_out = new PrintWriter(new FileWriter(dmpFilename.toString()), true);
}

// Call the actual 'dump' method
dump(fmb);

// Dump the coordinate system used by the module
m_indentation = " ";
dump(new Coordinate(fmb));
m_indentation = "";
println("Dumped " + fmb.getName());

// Close the module
fmb.destroy();
}

/**
* Recursively dump a forms JdapiObject and its children to the output stream
*/
protected void dump(JdapiObject jo)
{
String className = jo.getClassName();

// print out a context line for the JdapiObject
// If it is a coordinate system, it does not have a name

if(className.equals("Coordinate"))
{
println(m_indentation + "Coordinate System ");
}
else
{
println(m_indentation + className + " " + jo.getName());
}

// Property classes need special treatment
if(className.equals("PropertyClass"))
{
dumpPropertyClass((PropertyClass)jo);
}
else // Generically dump the required property types only
{
if (m_dumpTextProps)
{
dumpTextProps(jo);
}
if (m_dumpBoolProps)
{
dumpBoolProps(jo);
}

if (m_dumpNumProps)
{
dumpNumProps(jo);
}
// Additionally, dump any Item list elements
if(className.equals("Item"))
{
dumpListElements((Item)jo);
}
}

// use Form's metadata to get a list of all the child JdapiObjects this
JdapiObject can have
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getChildObjectMetaProperties();
JdapiMetaProperty prop = null;
JdapiIterator iter = null;
JdapiObject child = null;

// loop through every possible kind of child JdapiObject this JdapiObject
//can have
while(props.hasNext())
{
prop = (JdapiMetaProperty)props.next();
// only bother if we can access these JdapiObjects
if(!prop.allowGet())
{
continue;
}

// get the actual values for the current child JdapiObject type,
// e.g. get the Items on a Block
iter = jo.getChildObjectProperty(prop.getPropertyId());

// null is returned if there are no property values
if(iter != null)
{
// loop over every child value
while(iter.hasNext())
{
child = (JdapiObject)iter.next();
// recursively navigate to it
m_indentation += " ";
dump(child);
if(m_indentation.length()>2)
m_indentation = m_indentation.substring(0, m_indentation.length()-2)
;
}
}
}
}
/**
* Dump list elements
*
* The JdapiObject is an item; if it is a list item,
* dump the list elements.
*
* @param item
*/
private void dumpListElements(Item item)
{
if( item.getItemType() == JdapiTypes.ITTY_LS_CTID)
{
if (m_dumpPropNames)
{
println(m_indentation + "dumping list elements");
}
for(int i = 1; i <= item.getListElementCount(); i++)
{
String label = item.getElementLabel(i);
String value = item.getElementValue(i);
println( m_indentation + " " + i + ": '" + label + "' '" + value + "'");
}
}
}
/**
* Dump the property class properties
*/
private void dumpPropertyClass(PropertyClass pc)
{
String propertyVal = null;

// test for every single possible property
// this is a bit hacky :)
for(int propertyId = 1; propertyId < JdapiTypes.MAXIMUM_PTID; ++propertyId)
{
if(!pc.hasProperty(propertyId))
{
continue; // this property is not in the set
}
if(pc.hasDefaultedProperty(propertyId) && !m_dumpAllProps)
{
continue;
}
Class pt = JdapiMetaProperty.getPropertyType(propertyId);
if(pt == Boolean.class)
{
if(m_dumpBoolProps)
{
propertyVal = String.valueOf(pc.getBooleanProperty(propertyId));
}
}
else if(pt == Integer.class)
{
if(m_dumpNumProps)
{
propertyVal = String.valueOf(pc.getIntegerProperty(propertyId));
}
}
else if(pt == String.class)
{
if(m_dumpTextProps)
{
propertyVal = pc.getStringProperty(propertyId);
}
}
if(null != propertyVal)
{
if (m_dumpPropNames)
{
println(m_indentation + " " + JdapiMetaProperty.getPro
pertyName(propertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
propertyVal = null;
}
} // End loop over every property
}
/**
* Dump the source JdapiObject text properties
*/
private void dumpTextProps(JdapiObject jo)
{
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getStringMetaProperties();
// for each text property
while(props.hasNext())
{
JdapiMetaProperty prop = (JdapiMetaProperty) props.next();
int propertyId = prop.getPropertyId();
String propertyVal = null;
try
{
propertyVal = jo.getStringProperty(propertyId);
}
catch(Exception e)
{
println(m_indentation + "Could_not_get_property " +
JdapiMetaProperty.getPropertyName(propertyId));
continue;
}
if ( jo.hasProperty(propertyId)
&& (m_dumpAllProps || !(jo.hasDefaultedProperty(propertyId)) ) )
{
if(m_dumpPropNames)
{
println( m_indentation + " " + JdapiMetaProperty.
getPropertyName(propertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
}
}
}
/**
* Dump the source JdapiObject boolean properties
*/
private void dumpBoolProps(JdapiObject jo)
{
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getBooleanMetaProperties();
// for each boolean property
while(props.hasNext())
{
JdapiMetaProperty prop = (JdapiMetaProperty) props.next();
int propertyId = prop.getPropertyId();
boolean propertyVal = false;
try
{
propertyVal = jo.getBooleanProperty(propertyId);
}
catch(Exception e)
{
println(m_indentation + "Could_not_get_property " +
JdapiMetaProperty.getPropertyName(propertyId));
continue;
}
if ( jo.hasProperty(propertyId)
&& (m_dumpAllProps ) )
{
if(m_dumpPropNames)
{
println(m_indentation + " " + JdapiMetaProperty.
getPropertyName(propertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
}
}
}
/**
* Dump the source JdapiObject numeric properties
*/
private void dumpNumProps(JdapiObject jo)
{
JdapiMetaObject meta = JdapiMetadata.getJdapiMetaObject(jo.getClass());
JdapiIterator props = meta.getIntegerMetaProperties();
// for each numeric property
while(props.hasNext())
{
JdapiMetaProperty prop = (JdapiMetaProperty) props.next();
int propertyId = prop.getPropertyId();
int propertyVal = 0;
try
{
propertyVal = jo.getIntegerProperty(propertyId);
}
catch(Exception e)
{
println(m_indentation + "Could_not_get_property " +
JdapiMetaProperty.getPropertyName(propertyId));
continue;
}
if ( jo.hasProperty(propertyId)
&& (m_dumpAllProps || !(jo.hasDefaultedProperty(propertyId)) ) )
{
if (m_dumpPropNames)
{
println(m_indentation + " " + JdapiMetaProperty.getPropertyName(pr
opertyId) + " " +
propertyVal);
}
else
{
println(m_indentation + propertyVal);
}
}
}
}
/**
* Output usage info to STDOUT
*/
public void printUsage()
{
System.out.println("");
System.out.println("Jdapi Form Dumper Utility");
System.out.println("Valid arguments:");
System.out.println("-a : dump all properties, not just overridden ones");
System.out.println("-b : dump boolean properties");
System.out.println("-n : dump numeric properties");
System.out.println("-t : dump text properties");
System.out.println("-p : dump property names, not just values");
System.out.println("-o : file path to output to");
}
/**
* Main method
*/
public static void main(String[] args)
throws Exception
{
FormDumper dmp = new FormDumper();
for (int i = 0; i < args.length; i++)
{
dmp.dumpForm(args[i]);
}
System.out.println("");
System.out.println("Dumps complete");
System.out.println("");
}
}

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

3 Oracle Reports

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

- General Issues and Workarounds

General Issues and Workarounds

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

- Mapping Users and Roles to Reports Application

- Openmotif Library for SUSE Linux 11 Operating Systems

- Configuration Fails While Starting WLS_Reports Server

- Oracle Reports Builder Fails to Open the Data Model from Object Navigator

- Reports Weblayout not Supported on SUSE 10

Mapping Users and Roles to Reports Application

In Oracle Fusion Middleware 11g Release 1 (11.1.1.3.0) 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

Openmotif Library for SUSE Linux 11 Operating Systems

Before installing Oracle Reports 11g Release 1, ensure that the openmotif22-libs-2.2.4-138.17 library is installed on your machine. If this library is not installed, the installation of Oracle Reports fails.

You can download the library from the following location:

http://ftp.novell.com/partners/oracle/sles-11/openmotif_FUSION_SLES11.tgz

Configuration Fails While Starting WLS_Reports Server

While starting managed weblogic server, WLS_REPORTS, configuration fails showing the following errors:

The input line is too long.
The syntax of the command is incorrect.

This occurs when user creates MW_HOME, ORACLE_HOME and domain directory with long names. Consequently the value for environment variable like JAVA_OPTIONS and CLASSPATH become very long, and the actual command for starting the WLS_REPORTS Managed Server exceeds the windows command maximum limit of 8191 characters.

To work around this issue, use short names for ORACLE_HOME, MW_HOME and domain directory on windows.

Oracle Reports Builder Fails to Open the Data Model from Object Navigator

On Microsoft Windows x64 (64-Bit) systems, Oracle Reports builder fails to open the Data Model view when you double-click the data model icon from the Object Navigator.

Workaround

From the File menu, select New, then select Report, and then select the Build a new report manually option to open the Data Model view.

Reports Weblayout not Supported on SUSE 10

As Mozilla Firefox is not supported on SUSE 10, Reports WebLayout is not certified with SUSE 10.

4 Oracle Portal

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

- Before You Begin

- General Issues and Workarounds

- Upgrade Issues and Workarounds

- Interoperability Issues and Workarounds

- User Interface Issue and Workaround

- Export and Import Issues and Workarounds

- Portlet and Provider Issues and Workarounds

- PDK Issue and Workaround

- Globalization Support Issues and Workarounds

Before You Begin

In addition to the known problems and workarounds described in this document, Oracle recommends that you read the My Oracle Support note 834615.1 - Oracle Fusion Middleware 11g Portal (11.1.1) Support Status and Alerts. This article contains known issues that were discovered after the release of Oracle Portal 11g Release 1 (11.1.1).

General Issues and Workarounds

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

- Editing a Database Link Requires Password

- Moving Content When Approval Is Enabled Does Not Require Approval

- Firefox and Safari Browsers Do Not Display Tooltips on Oracle Portal Screens

- Non-ASCII URLs Cannot be Decoded in Some Scenarios

- Adding a Zip File with a Non-ASCII Character Name

- Manual Changes to Oracle Portal Default Schema Objects

- Oracle HTTP Server or Web Cache Does Not Start Due to Wallet Permissions

- Error When Creating RCU Portal Schema

- Portal Throws Discoverer Provider is Busy Error Message

- Error When Adding Sample RSS Portlets to a Page

- Internal Error when Using Portal Search With Oracle Text Enabled to Search for Pages

- Cloning Utility Not Supported

- Issue After Creating a Oracle Portal Schema

- Updating Database Tables

- Apply Patch to Address Performance Issue

Editing a Database Link Requires Password

If the database where the portal schema is installed is version 10.2 or later, then users must re-enter the remote user's password when they rename or edit a database link from the Portal Navigator's Database Objects tab. This is applicable only for those database links that are created with the Specific User option.

Moving Content When Approval Is Enabled Does Not Require Approval

Moving content between pages or between regions of the same page does not trigger approvals. For example, when a target page is configured with an approval process and a contributor moves content from a source page to the target page, the moved content does not trigger the approval process on the target page, even when approval is required for all users.

Firefox and Safari Browsers Do Not Display Tooltips on Oracle Portal Screens

Firefox and Safari browsers do not support the display of tooltip text, which is set using the ALT attribute for image descriptions.

As a workaround, you can download and install browser-specific add-ons, such as Popup ALT Attribute for Firefox (see https://addons.mozilla.org/en-US/firefox/addon/1933).

Non-ASCII URLs Cannot be Decoded in Some Scenarios

If the JVM default character encoding is set to ISO8859-1, the Portal repository database character set must match with the JVM default character encoding. If this condition is not satisfied, non-ASCII URLs may become inaccessible.

Adding a Zip File with a Non-ASCII Character Name

If you are adding a zip file to a page under a pagegroup using non-ascii character name, and when you unzip the file, it throws the following exception:

IllegalArgumentException: null and unzip will be failed.

To avoid this exception, you must use ascii character as the zip file name.

Manual Changes to Oracle Portal Default Schema Objects

Any manual changes to Oracle Portal default objects, such as tables, views, packages, or indexes are not supported. Such changes may render Oracle Portal unusable. Note that the internal structure of Portal objects can change between versions.

For more information, see the 403179.1 My Oracle Support note.

Oracle HTTP Server or Web Cache Does Not Start Due to Wallet Permissions

OPMN runs as a service in Windows. By default, it runs as the SYSTEM user for starting Oracle HTTP Server and Oracle Web Cache. When you are using SSL wallets created through Oracle Wallet Manager or orapki utility for Oracle HTTP Server or Oracle Web Cache, you must grant read permissions for the wallet to the SYSTEM user.

Error When Creating RCU Portal Schema

If RCU portal schema creation fails with the error message ORA-24246: empty access control list (ACL) not allowed, do the following:

1. Connect to the database as a SYS user.

2. At the SQL prompt, run the following command:

BEGIN
DBMS_NETWORK_ACL_ADMIN.drop_acl (
acl         => '/sys/acls/portal-permissions.xml');
COMMIT;
END;
/

Portal Throws Discoverer Provider is Busy Error Message

Portal throws an error message The Discoverer Provider is busy, please try again later. This occurs when you perform the following steps:

1. Click Edit Portlet defaults

2. Click Update for Database section

3. Change selection for User not logged sub-section

4. Click Next to fetch worksheet list

Workaround

To workaround this issue perform the following steps:

1. Add stall timeout to $DOMAIN_HOME/servers/WLS_PORTAL/
stage/portal/portal/configuration/appConfig.xml

For example: <stall>200</stall>

2. Restart WebLogic Server Portal

Error When Adding Sample RSS Portlets to a Page

When you try to add the sample Scrolling RSS Portlet or the sample Simple RSS portlet to a Portal page, an error message is displayed.

The error occurs because the RSS used by the sample portlets are no longer available.

Currently, there is no workaround for this problem.

Internal Error when Using Portal Search With Oracle Text Enabled to Search for Pages

If you have Oracle Text enabled, the following internal server error may occur when you are searching for Pages:

Internal error (WWC-00006)
An unexpected error has occurred (WWS-32100)
Unknown Exception (WWC-45131)
User-Defined Exception (WWV-11230)
Unexpected error - ORA-00600: internal error code, arguments:
[qkeIsExprReferenced1], [], [], [], [], [], [], [] (WWC-35000)

If this error occurs, you must download and install the patch ID 7041059 from https://support.oracle.com/

Cloning Utility Not Supported

The colclone.bat utility is not supported on Windows platform. For cloning purposes, use the manual procedure.

Issue After Creating a Oracle Portal Schema

After creating the Oracle Portal schema, you may get the following error:

checkinstall2=Add ACL for network packages if DB is 11.1 or higher...
old   4:     schema varchar2(2000)   := upper('&&1');
new   4:     schema varchar2(2000)   := upper('CLASSIC17_PORTAL');
Package DBMS_NETWORK_ACL_ADMIN exists, assign ACL if not already assigned
Removing dangling principals,if any from the ACL privilege list ...
ERROR: when assigning network ACL
declare
*
ERROR at line 1:
ORA-24246: empty access control list (ACL) not allowed
ORA-06512: at "SYS.DBMS_NETWORK_ACL_ADMIN", line 421
ORA-06512: at line 1
ORA-01403: no data found
ORA-06512: at line 83

To fix this error, you must create a schema with a different prefix, and then run the following command to clean out the dangling ACL:

begin
DBMS_NETWORK_ACL_ADMIN.DELETE_PRIVILEGE('portal-permissions.xml','PREFIX_PORTA
L');
end;

PREFIX_PORTAL is replaced with the schema prefix used in the schema that was dropped.

You must run the Repository Creation Utility to install the new schema.

Updating Database Tables

In Oracle Portal database object, if you insert one row data which has MB character and then update the row, the update will not work. You must manually update the table and view in the database to avoid this issue and update the table and view successfully.

Apply Patch to Address Performance Issue

After install, you must apply the patch referred to in KM Note 1087226.1. This patch contains a fix to address a serious performance issue that can occur while opening or saving HTML documents using the rich text editor. As this task is performed frequently, it's important to apply this patch to avoid a significant loss in productivity.

Upgrade Issues and Workarounds

This section describes the upgrade issues and workarounds. It discusses the following topics:

- Upgrading Portal 10g SSL Environment to Oracle Portal 11g Release 1 (11.1.1)

Upgrading Portal 10g SSL Environment to Oracle Portal 11g Release 1 (11.1.1)

When you upgrade SSL environment from Oracle Portal 10g to Oracle Portal 11g Release 1 (11.1.1), you will not able to login to Oracle Portal, when you have SSO and Portal Midtier on the same hostname. Internet Explorer has a problem redirecting back and forth on the same hostname between two different ports under SSL mode. As a workaround, you can use Mozilla Firefox.

Interoperability Issues and Workarounds

This section describes the interoperability issues and workarounds. It discusses the following topics:

- Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.3

- Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.4

- Creating Webproviders in the Oracle Portal 11g Release 1 (11.1.1) Midtier Interoperability with Oracle Portal Repository 10g Release

Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.3

For this interoperability scenario to work, you must download and install the patch ID 7685124 from https://support.oracle.com/and see note 816929.1 in My Oracle Support.

Interoperability Between Oracle Portal 11g Release 1 (11.1.1) with Secured Enterprise Search (SES) 10.1.8.4

For this interoperability scenario to work, you must download and install the patch ID 7971335 from https://support.oracle.com/

Creating Webproviders in the Oracle Portal 11g Release 1 (11.1.1) Midtier Interoperability with Oracle Portal Repository 10g Release

In Portal 11g 1 (11.1.1), you cannot create webproviders when you are using 11g midtier with 10g portal repository.

User Interface Issue and Workaround

This section describes issue and workaround related to the Oracle Portal user interface. It includes the following topic:

Cannot Set Privileges Using List View on Pages Inheriting Privileges from Parent or Template

If you use the List View to set access privileges for one or more pages, then privileges will not be set on pages inheriting privileges from a parent page or template. As a workaround, change the privileges for such pages individually, that is, using the Access tab for the subpage.

Export and Import Issues and Workarounds

This section describes issues and workarounds related to export and import in Oracle Portal. This section includes the following topics:

- Export and Import Does Not Support Reports Server Components

- Saving the Transport Set

- Error when importing a page group

Export and Import Does Not Support Reports Server Components

If you include Reports Server Components within a transport set, then they are deleted on export and import. In addition, do not configure the Oracle Reports item type in any page groups intended for export and import. If you do, then the following error is displayed when you try to configure item types in the imported page group (by clicking the Content Type and Classifications Edit link on the Configure tab for the page group):

Internal error (WWC-00006)
Unexpected error - User-Defined Exception (WWC-35000)
Unexpected error - ORA-01403: no data found (WWC-35000)

Saving the Transport Set

After you complete the transport set transfer, click Display Manifest to display the transport set manifest. Ensure that you save the transport set before performing the precheck of the transferred data. This step takes the manifest changes.

Error when importing a page group

Importing a page group may fail with the following error message:

[Error:  (WWU-80338)] context = Schema Validation user =
ORCLADMIN There were some inconsistencies found and hence import process is aborted.Check the debug log for further details.Fix those inconsistencies, by running schema validation in cleanup mode to proceed

This problem might occur after deleting a page group containing shared portlets. You must run SVU in cleanup mode to ensure a smooth export or import process.

Portlet and Provider Issues and Workarounds

This section describes issues and workarounds related to OmniPortlet, Web Clipping, Simple Parameter Form, Page portlet, and WSRP providers. This section includes the following topics:

- Issue When Accessing Page Portlet Using Federated Portal Adapter

- Error in JPS Portlet After Redeployment

- SSL Support for Oracle Portal Integration Solutions (Microsoft Exchange)

Issue When Accessing Page Portlet Using Federated Portal Adapter

The Federated Portal Adapter enables you to display remote portal pages in your portal. However, if both portal instances do not share the same Oracle Single Sign-On server, then you cannot display a remote portal page as a page portlet, even if the remote page is public. A message is displayed instead of the page portlet, as shown in the following example:

Portlet 257,75057 responded with content-type text/plain when the client was requesting content-type text/html

As a workaround, configure both portal instances to use the same Oracle Single Sign-On server.

Error in JPS Portlet After Redeployment

When you redeploy your portlets to the portlet container, all existing sessions between the producer and all of its consumers are lost. If a consumer tries to reuse an existing producer session, then it may receive an error message the first time it tries to contact the producer after redeployment, as shown in the following example:

Error: Could not get markup. The cookie or session is invalid or there is a runtime exception.

To reestablish the producer's session, refresh the portal page. You will not see this error message if you are reaccessing the portlet from a new browser session because it automatically establishes a new producer session.

SSL Support for Oracle Portal Integration Solutions (Microsoft Exchange)

SSL support is not available for Oracle Portal Integration Solutions (Microsoft Exchange). This is a known limitation.

PDK Issue and Workaround

Oracle Portal Developer Kit (PDK) version 10.1.2 is included with the Portal and Wireless installation. Release notes for the PDK-Java and PDK-PL/SQL can be found at the following middle-tier ORACLE_HOME locations:

- PDK-Java: ORACLE_HOME/portal/pdkjava/v2/pdkjava.v2.releasenotes.html

- PDK-PL/SQL: ORACLE_HOME/portal/pdkjava/v2/pdkplsql.release.notes.html

Latest Version of Oracle PDK

New versions of the Oracle PDK are released periodically providing new features, new APIs, and additional documentation. To take advantage of all the latest features, download the latest PDK from the PDK downloads page on the Oracle Technology Network (OTN) at http://www.oracle.com/technology/products/ias/portal/pdk.html.

Release notes for the latest Oracle PDK version are available on Oracle Portal on OTN and also in these PDK download locations:

- pdk\plsql\pdkplsql.release.notes.html

- pdk\jpdk\v2\pdkjava.v2.release.notes.html

Globalization Support Issues and Workarounds

This section describes issues and workarounds related to Globalization Support in Oracle Portal. It includes the following topics:

- Text Entry Always Right to Left in BiDi Languages

- Non-ASCII Character Limitations in Oracle Portal

- Multibyte Characters in Log Files

Text Entry Always Right to Left in BiDi Languages

The direction of all text areas and fields is right to left (RTL). However, you may want some text areas to work left to right (LTR). Internet Explorer users can change this by pressing the left hand side Ctrl and Shift keys.

Non-ASCII Character Limitations in Oracle Portal

When you copy and paste an item URL containing non-ASCII characters from one browser Location or Address field into another, you may not be able to access the item if your login credentials have not been authenticated through OracleAS Single Sign-On.

As a workaround, log in to the portal before you access the item and copy the item URL.

Multibyte Characters in Log Files

In some scenarios, multibyte characters in log files may get corrupted.

For example, when the WLS_PORTAL managed server is started from the Oracle WebLogic Server Administration Console, multibyte characters, such as username, password, and is starting, may get corrupted.

Workarounds:

- Change -Dfile.encoding=iso-8859-1 to -Dfile.encoding=utf8 in the WLS_PORTAL start-up parameter through the Oracle WebLogic Server Administration Console.

- Change -Dfile.encoding=iso-8859-1 to -Dfile.encoding=utf8 in the setDomainEnv.cmd file (Located at MW_HOME\user_projects\domains\DomainName\bin).

- Change -Dfile.encoding=iso-8859-1 to -Dfile.encoding=utf8 in the setDomainEnv.sh file (Located at MW_HOME/user_projects/domains/DomainName/bin).

For more information, see note 403179.1.

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.