This chapter describes issues associated specifically with Oracle Business Intelligence. It includes the following topics:
Section 53.1, "Oracle Business Intelligence 11.1.1.3.0 and Oracle Fusion Middleware 11.1.1.4.0"
Section 53.3, "Oracle Business Intelligence General Issues and Workarounds"
Section 53.4, "Oracle Business Intelligence Installation Issues and Workarounds"
Section 53.5, "Oracle Business Intelligence Upgrade Issues and Workarounds"
Section 53.6, "Oracle Business Intelligence Analyses and Dashboards Issues and Workarounds"
Section 53.7, "Oracle BI Publisher Reporting and Publishing Issues and Workarounds"
Section 53.8, "Oracle Business Intelligence Metadata Repository Development Issues and Workarounds"
Section 53.9, "Oracle Business Intelligence System Administration Issues and Workarounds"
Section 53.10, "Oracle Business Intelligence Integration and API Issues and Workarounds"
Section 53.11, "Oracle Business Intelligence Localization Issues and Workarounds"
Section 53.12, "Oracle Business Intelligence Documentation Errata"
Depending on your Oracle Fusion Middleware implementation, some information in other chapters of this document might also be relevant, including:
Chapter 5, "Oracle Enterprise Manager Fusion Middleware Control"
Chapter 6, "Oracle Fusion Middleware High Availability and Enterprise Deployment"
Oracle Business Intelligence 11g Release 1 (11.1.1.3) is compatible with Oracle Fusion Middleware 11g, Release 1 (11.1.1.4).
Going forward, newly identified issues with Oracle Business Intelligence Release 11.1.1.3 will be added to the Oracle Business Intelligence chapter in the Oracle Fusion Middleware Release Notes for Release 11.1.1.4 at http://download.oracle.com/docs/cd/E17904_01/relnotes.htm.
This section describes patch requirements for Oracle Business Intelligence. It includes the following topic:
Periodically, Oracle Business Intelligence patches are released. Some patches are mandatory, other patches are optional.
To see the patches that are available, go to My Oracle Support (formerly OracleMetaLink) using the following URL:
To obtain a patch:
Log in to My Oracle Support.
Click the Patches & Updates tab.
In the Patch Search section, enter the patch number in the Patch ID or number is field, and enter your platform in the field after the and Platform is field.
Click Search.
On the Patch Search page, click the patch number in the Patch ID column.
The page content changes and displays detailed information about the patch.
Click Download to download the patch.
Install the patch by following the instructions in the README file included with the patch.
This section describes general issues and workarounds related to Oracle Business Intelligence. It includes the following topics:
Section 53.3.2, "Issue with JAR File Size When Moving from a Test to a Production Environment"
Section 53.3.3, "Oracle BI Server Fails to Start Due to Missing Connect String in tnsnames.ora File"
Section 53.3.4, "Adobe Flash Player Version 10.1 or Later Required to View Graphs and Scorecards"
Oracle Business Intelligence Enterprise Edition 10g included the Oracle BI Disconnected Analytics component. The Oracle BI Disconnected Analytics component is not shipped in (and cannot be used with) Oracle Business Intelligence Enterprise Edition 11g, Release 11.1.1.3.
If you currently use Oracle BI Disconnected Analytics 10g and want to continue to do so, do not install or upgrade to Oracle Business Intelligence Enterprise Edition 11g, Release 11.1.1.3.
This issue is applicable when moving from a test environment to a production environment. The Oracle Business Intelligence installation creates a JAR file of approximately 5 GB. JDK has a file size limit of 4 GB. Therefore, when you un-jar the file using the AS command pasteBinary, a crash occurs.
The workaround is to force the pasteBinary command to use JRockit, which does not have a file size limit. For instructions, see Oracle Fusion Middleware Administrator's Guide.
The Adobe Flash Player is a cross-platform browser-based application runtime environment and is required for rendering graphs and scorecard objects in a browser.
Users must have Adobe Flash Player version 10.1 or later installed on their browsers in order to correctly view all graphs and scorecards generated by Oracle BI EE. Users can obtain information about the version of the Adobe Flash Player that is running on their browser by going to http://www.adobe.com/software/flash/about/.
If you want to use Essbase or Hyperion Financial Management as a data source for the Oracle BI Server, and you want to pass user names directly to the data sources using :USER and :PASSWORD in the connection pool rather than configure a shared connection pool, you must enable compatibility for a shared token that the Oracle BI Server can pass to the Enterprise Performance Management products. To do this, you can download and run a utility that populates data in the EPM Registry tables that are part of the BI Platform schema that is created by RCU.
Before you begin, make sure that you have the database connection information available for the Oracle Business Intelligence database where you populated the BI Platform schemas using RCU. For example, ensure that you have the host name, port, SID, user name, and password for the database.
To enable CSS token generation for single sign-on from the Oracle BI Server to Essbase or Hyperion Financial Management data sources:
In the Oracle Business Intelligence environment, open setDomainEnv.sh (or setDomainEnv.bat on Windows) for editing. You can find this file at:
DOMAIN_HOME/bin
For example:
MW_HOME/user_projects/domains/bifoundation_domain/bin
Add the following entry:
ExtraJavaProperties=-DEPM_ORACLE_INSTANCE= ORACLE_INSTANCE
For example:
ExtraJavaProperties=-DEPM_ORACLE_INSTANCE= C:\My_MW_Home\instances\instance1
Save and close the file.
Download the patch for bug 10263740 from My Oracle Support to obtain the utility. See Section 53.2.1, "Obtaining Patches from My Oracle Support" for more information.
Extract the contents of the archive to:
ORACLE_INSTANCE/config/foundation/11.1.2.0
Create this directory if it does not already exist.
Edit epm_components_creation.sh (or epm_components_creation.bat on Windows) to provide required values for ORACLE_HOME, ORACLE_INSTANCE, and JAVA_HOME as appropriate for your environment.
On Linux systems, make epm_components_creation.sh executable using the following command:
chmod +x epm_components_creation.sh
Run the executable epm_components_creation.sh (or epm_components_creation.bat on Windows), and provide the database host name, port, SID, user name, and password as command-line arguments. For example:
epm_components_creation.sh db_hostname db_port sid db_user db_pwd
The following output is displayed:
Writing credentials to reg.properties file. Credentials written to reg.properties file. Creating Component Types. Component Types Created. Creating Basic Components Basic Components Created All tasks successfully completed.
To validate that the data was successfully populated in the EPM Registry, execute epm_components_creation.sh (or epm_components_creation.bat on Windows) and provide "validate" as a command-line argument. For example:
epm_components_creation.sh validate
The following output is displayed:
Following required properties are available for SHARED_SERVICES_PRODUCT in EPM Registry:- mode=FUSIONAPPS COMPATIBILITY=11120-
See also Section 53.12.6.2, "Connecting to Hyperion Financial Management Data Sources with an 11g Client."
This section describes issues and workarounds related to installing Oracle Business Intelligence. It includes the following topics:
Section 53.4.1, "Error When Installing Oracle Business Intelligence Against a SQL Server Database"
Section 53.4.2, "Scale-Out Scenarios Are Not Supported on OS with Different Patch Levels"
Section 53.4.5, "Oracle BI Configuration Failure Post Successful Cloning"
Section 53.4.6, "Scale Out in Silent Mode Fails When Using Configuration Assistant"
Section 53.4.7, "Need to Correctly Create the Oracle Central Inventory in a Linux Environment"
Section 53.4.8, "Oracle Enterprise Manager Fusion Middleware Control Topology Viewer Status"
Section 53.4.9, "Oracle Business Intelligence Installer Stops at Administrator User Details Screen"
Section 53.4.12, "Installing Oracle Business Intelligence on a Shared Drive May Fail"
Depending on your Oracle Fusion Middleware implementation, some information in Chapter 2, "Installation, Patching, and Configuration" might also be relevant.
If you are using an MS SQL Server database when installing Oracle Business Intelligence, the mds-owsm and bip_datasource JDBC data sources has an invalid test table. This stops the WebLogic Server automatic connection testing from functioning. For example, if the database stops, WebLogic Server does not recognize a hanging or invalid connection.
The workaround is to edit the Test Table Name parameter to allow a SQL string to be executed to test the connection. To do so, set the parameter in the WebLogic Server Administration Console to SQL select 1.
Scale-out scenarios of the BI domain are not supported on machines that have the same operating system but different patch levels. All machines must have the same operating system patch level.
When using the Repository Creation Utility (RCU) to install the BIPLATFORM and MDS schemas on a DB2 database in a Linux environment, note the following:
Make sure the schema names are eight characters or less.
Note: The prefix for both the BIPLATFORM and MDS schema names must be the same.
For example, if you use the prefix "dev," you must edit the default schema name of "dev_BIPLATFORM" to be eight characters or less. You can shorten the suffix, but the prefix for both schema names must be the same. You can edit the schema name by clicking the name to make it an editable field.
If you do not shorten the schema name to eight characters or less, RCU will return an error on the Password page that states, "Please enter valid username/password." This is the same error that is returned if the user on the DB2 instance does not have the same password as entered in RCU.
There may be a name length restriction for the temporary tablespace name. If the BIPLATFORM tablespace name is too long, see the Oracle Fusion Middleware Repository Creation Utility User's Guide for information about creating a new tablespace with a shorter name. You can also use the same tablespace as that for the new MDS schema.
When using Repository Creation Utility (RCU) with an IBM DB2 Database, ensure that the database schemas created by RCU have the required permissions to use the DataDirect ODBC drivers. If these permissions are not set, then Oracle BI Scheduler fails to start as it cannot query the Oracle BI Scheduler tables. You can find the correct permissions in the DataDirect driver documentation at the following location:
http://www.datadirect.com/developer/odbc/docs/odbcdb2bind.pdf
Oracle Business Intelligence uses Oracle WebLogic Server 10.3.3.0. WLS 10.3.3.0 installation location in cloned area has JAVA_HOME path in the .product.properties file set to 32-bit jrockit, which is a nonexistent JAVA_HOME path. This leads to Oracle BI configuration failure.
To work around this issue, modify the .product.properties file under $MW_HOME/wlserver_10.3 directory with appropriate JDK locations for the parameters which has reference to jrockit. This must be done post successful cloning.
Refer to the certification document to look for supported JDKs and JVMs, found at the following URL:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
When scaling out an Oracle Business Intelligence system in silent mode, add the following variables to the [GENERIC] section of the silent mode response file (.rsp):
CONFIG_MW_HOME
CONFIG_ORACLE_HOME
CONFIG_WEBLOGIC_HOME
The values of these variables should be set the same as that of the existing MW_HOME, ORACLE_HOME and WEBLOGIC_HOME variables so that a section of the response file looks similar to the following:
#Specify the Middleware Home location. MW_HOME=/scratch/biee CONFIG_MW_HOME=/scratch/biee #Give the name of the Oracle Home directory. The Oracle Home directory name may only contain alphanumeric , hyphen (-) , dot (.) and underscore (_) characters, and it must begin with an alphanumeric character. ORACLE_HOME=/scratch/biee/Oracle_BI1 CONFIG_ORACLE_HOME=/scratch/biee/Oracle_BI1 #Give the complete path to a valid WebLogic Server Home. WEBLOGIC_HOME=/scratch/biee/wlserver_10.3 CONFIG_WEBLOGIC_HOME=/scratch/biee/wlserver_10.3
When installing Oracle Business Intelligence on a computer running a supported Linux operating system and that has no other Oracle software, ensure that you create the Oracle Central Inventory correctly. This action ensures correct patching functionality.
The status of the Oracle Business Intelligence components shows as Unknown in the Fusion Middleware Control topology viewer page.
There is no workaround for this issue.
If you attempt to install on a Windows machine that is using DHCP, does not have a primary DNS suffix, and does not have a loopback adapter configured, then the Oracle Business Intelligence installer will stop at the screen prompting for the Administrator user details. This appears as a red cross in the tree on the left hand side of the installer. This issue is caused by the installer not being able to resolve the IP address to a hostname.
The workaround is to configure a loopback adapter or primary DNS suffix.
When installing Oracle Business Intelligence onto a shared network drive, under certain circumstances, JRockit may become unstable.
The workaround is to first install Oracle WebLogic Server in custom mode and only install the Sun JDK (that is, deselect JRockit). The next step is to install Oracle Business Intelligence following the instructions for a 'Software Only Install'.
If the Oracle Business Intelligence installation fails at the creation of ASInstance, then you may need to increase the MaxPermSize parameter. The failure at the creation of ASInstance is indicated by the following log file entry:
An internal operation has failed: PermGen space
To increase the MaxPermSize parameter:
Perform a Software Only installation as described in the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
Before running the configuration phase, do the following:
Open the file MW_HOME/ORACLE_HOME/oui/oraparam.ini in a text editor.
Locate the following line:
JRE_MEMORY_OPTIONS=" -mx512m -XX:MaxPermSize=512m"
Increase the numbers for allocating more memory, for example:
JRE_MEMORY_OPTIONS=" -mx1024m -XX:MaxPermSize=1024m"
or
JRE_MEMORY_OPTIONS=" -mx2048m -XX:MaxPermSize=2048m"
Save the oraparam.ini file.
Continue to run the config.bat script as described in the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence.
Attempting to install Oracle Business Intelligence on a shared drive may fail, resulting in the following error message:
Installation Failed. Prepare Session failed You may not have enough space on your drive for a successful install. Do you still want to continue?
To avoid this issue when installing Oracle Business Intelligence on a shared drive, start the Oracle Business Intelligence installer from the command line using the ignoreDiskWarning option. For example, on Linux, use the following command:
./runInstaller -ignoreDiskWarning
This section describes issues and workarounds related to upgrading Oracle Business Intelligence from previous releases. It includes the following topics:
Depending on your Oracle Fusion Middleware implementation, some information in Chapter 3, "Upgrade" might also be relevant.
This section describes general issues and workarounds related to upgrading Oracle Business Intelligence from previous releases. It includes the following topic:
If an attribute column's Value Suppression setting (in the Column Format tab of the Column Properties dialog) is not set to Repeat, then the measure is aggregated to the grain as defined by the position of the column with the format defined. This might cause a change in the conditional formatting after upgrading to Oracle Business Intelligence. If the Value Suppression setting is set to Repeat, then the measure column that the conditional format is based on always uses the detail grain of the table view, in which case the conditional formatting works as expected.
Translated help files for the Oracle Business Intelligence Upgrade Assistant are not available. When running the Upgrade Assistant in a language other than English, clicking Help will display an error.
There is no workaround.
This section describes issues and workarounds related to security when upgrading Oracle Business Intelligence from previous releases. It includes the following topic:
When upgrading an RPD with non-English user or group names, warnings may be reported in the log file, such as "Group name ??? isn't valid in WLS/LDAP : not migrating this group" or "User name ??? isn't valid in WLS/LDAP : not migrating this user" (where ??? is garbled text).
The workaround is to manually create the users or groups. To do so, see the following instructions in Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition:
For a group:
Create the group as described in Section 2.4.4, "How to Create a Group in the Embedded WebLogic LDAP Server."
Create an Application Role as described in Section 2.5.2, "Creating Application Roles Using Fusion Middleware Control."
Add the group to the application role as described in Section 2.5.2.2, "How to Create an Application Role."
If the RPD group was a member of another RPD group, create the same Group and Application Role hierarchy.
For a user:
Create the user as described in Section 2.4.3, "How to Create a User in the Embedded Weblogic LDAP Server."
Assign the user to the required groups as described in Section 2.4.5, "How to Add a User to a Group in the Embedded Weblogic LDAP Server."
When upgrading an RPD, users or groups with names that contain the following invalid characters are not upgraded:
,
+
=
"
\
<
>
;
The workaround is to manually create the users or groups after upgrade is complete, with new names that do not contain the invalid characters. Note that the new names must not contain invalid characters under any circumstances. Failure to follow this instruction will require you to re-install Oracle Business Intelligence.
This section describes issues and workarounds related to Oracle Business Intelligence analyses and dashboards. It includes the following topics:
Section 53.6.1, "General Analyses and Dashboards Issues and Workarounds"
Section 53.6.5, "Microsoft Office Integration Issues and Workarounds"
This section describes general issues and workarounds related to Oracle Business Intelligence analyses and dashboards. It includes the following topics:
Section 53.6.1.2, "Gauge Views May Be Cut Off and Not Visible Under Certain Conditions"
Chapter 53, "Numerical Units on a Dashboard Prompt Slider Might Not Be Translated Correctly"
If a column is renamed in the Business Model, then existing dashboard prompts based on that column do not work with newly created analyses.
The workaround is to use Catalog Manager to rename the column in the catalog.
Under certain conditions, if the size of the canvas assigned to a gauge view is very small, and the legend is set to display on the left, then some of the gauges in the gauge view may be cut off and not visible.
The workaround is to edit the gauge view and change the Legend position to Right, Top, or Bottom. Alternatively, you can increase the size of the gauge view canvas so that all gauges display.
The numerical units (such as million or billion) that are displayed on a dashboard prompt slider might not be translated correctly.
The workaround is to modify the obiprp.promptcomponents.xml file as follows:
Open the obiprp.promptcomponents.xml file for editing. You can find the file here:
ORACLE_INSTANCE\bifoundation\web\msgdb\l_XX\messages\uicmsgs
Ensure that each entry for a numerical unit (such as tag name kmsgSliderBillion, kmsgSliderMillion, or kmsgSliderDecillion) is translated correctly.
Restart the Managed Servers, the Administration Server and all Oracle Business Intelligence Java components, and the Oracle Business Intelligence system components. For information on how to restart the Managed Servers, the Administration Server and all Oracle Business Intelligence Java components, and the Oracle Business Intelligence system components, see Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
This section describes issues and workarounds related to actions. It includes the following topics:
Section 53.6.2.1, "Action to Invoke a Web Service Cannot Use WSDL on HTTPS"
Section 53.6.2.2, "EJBs in Action Framework Must Be Deployed to the WebLogic Managed Server"
A limitation currently exists in the Action Framework functionality when creating an action to invoke a Web service. If the WSDL file for the target Web service is accessible using the HTTPS protocol, then the Action Framework cannot introspect the WSDL file.
The workaround is to make the WSDL file available over HTTP. Secure the target Web service using an appropriate security policy.
A limitation currently exists in the Action Framework functionality when creating actions to invoke Java methods in EJBs. Only EJBs deployed within the same J2EE container as the Action Framework services (by default the WebLogic Managed Server) are available to the Action Framework.
The workaround is to invoke a target EJB. To do so, implement one of the following methods:
Deploy the target EJB to the WebLogic Managed Server in the BI domain (adhering to any license restrictions for WebLogic Server).
Deploy a gateway EJB/Web service on the WebLogic Managed Server specifically to invoke the remote EJB.
Expose the remote EJB as a Web service.
Deploy a gateway Web service on the remote location to invoke the EJB.
This section describes issues and workarounds related to scorecards and KPIs. It includes the following topics:
You can use the full-text catalog search functionality to search in most catalog objects and related documents. Currently, the full-text catalog search functionality searches in scorecards themselves and in the names of related documents, but it does not search in the content of related documents for scorecards.
When using a shared Oracle BI Presentation Catalog and a scaled-out configuration of Oracle BI Presentation Services, users might see "Item Stale : <scorecard path>" errors, when they edit a shared scorecard in parallel.
The workaround to prevent this error is to turn off the Oracle BI Presentation Services Catalog Attribute Cache. To do so, set the following in the instanceconfig.xml file:
<ps:Cache xmlns:ps="oracle.bi.presentation.services/config/v1.1">
<ps:CatalogAttributes>
<ps:Enabled>false</ps:Enabled>
</ps:CatalogAttributes>
</ps:Cache>
For more information on the cache, see Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.
This section describes issues and workarounds related to agents. It includes the following topics:
Section 53.6.4.2, "Agent Deliveries Fail If the Secure Socket Layer (SSL) Is Enabled"
Section 53.6.4.3, "Loss of Agent Customizations If Agent Folder Is Renamed"
If you are using Microsoft Active Directory and Oracle Virtual Directory, then agent deliveries fail.
The workaround is to apply the Oracle Virtual Directory Patch Number 9904956 - GUID Returned for AD User Cannot Be Used in Search Filter.
If the Secure Socket Layer (SSL) is enabled, then agent deliveries fail.
This issue has no workaround.
If you rename a folder that contains an agent that has been published for subscription and that can be customized by subscribers, then any agent customizations that subscribers have done are lost.
This issue has no workaround.
This section describes issues and workarounds related to the integration between Oracle Business Intelligence and Microsoft Office. It includes the following topics:
Section 53.6.5.1, "Using Microsoft Office 2007 with Oracle BI Add-in for Microsoft Office"
Section 53.6.5.2, "Funnel Views Can Be Inserted As Images and Flash Objects"
If you use Microsoft Office 2007 with Oracle BI Add-in for Microsoft Office, then ensure that Office 2007 SP1 at minimum is installed. If you do not, you might encounter file interchangeability issues between Microsoft Office 2007 and Microsoft Office 2003.
For more detailed information on versions, see the certification document available on Oracle Technology Network (OTN):
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
The online help for Oracle BI Add-in for Microsoft PowerPoint states that the funnel view can be inserted only as an image. This is incorrect. The funnel view can also be inserted as a Flash object.
Default title views or data formatting might not be imported successfully into Microsoft Excel or PowerPoint.
In case of data formatting, this happens especially when the default data formatting is saved using Save as the system-wide default for <column> or Save as the system-wide default for this datatype in the Column Properties dialog in Oracle BI EE.
The workaround for both title views and data formatting is to clear the default box and specify the required data formatting or contents for the title views explicitly.
Microsoft Excel and PowerPoint on the same computer share Oracle BI Add-in for Microsoft Office connections. If you create a connection in Excel, then that connection is also available in PowerPoint. However, if you create an Oracle BI Add-in for Microsoft Office connection in Excel while PowerPoint is open, then the connection is not displayed in PowerPoint, and vice versa.
The workaround to create a connection to be shared between Excel and PowerPoint is to ensure that the other Microsoft Office application is closed. Alternatively, you can close both Excel and PowerPoint, and reopen them as needed in order to see connections available in both Excel and PowerPoint.
The Oracle BI Add-in for Microsoft Office 11g installer does not uninstall previous versions of Oracle BI Add-in for Microsoft Office. Therefore, you must manually uninstall any previous Oracle BI Add-in for Microsoft Office installations before installing Oracle BI Add-in for Microsoft Office 11.1.1.3.0.
For more information on installing Oracle BI Add-in for Microsoft Office, see Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition.
Data mismatch might occur between results displayed in Oracle BI EE and the same view imported into Microsoft Excel or PowerPoint. The mismatch might fall into one or more of the following categories:
The views imported into Excel or PowerPoint use a different sort order compared to the ones displayed in Oracle BI EE.
When filters and prompts are applied, subtotals and grand totals are calculated using report-based totals.
When filters and prompts are applied on measures, and one or more columns are unselected while inserting the view in Excel or PowerPoint, the view displayed might not match the one that is displayed in Oracle BI EE. This happens due to the change in the granularity of the analysis as a result of omitting columns, forcing aggregation of measures and applying the filter and prompts next, thus resulting in a different view of the same data.
The workaround is as follows:
In the case of a graph view, insert the view as an image or a Flash object. Flash is supported only in Oracle BI Add-in for Microsoft PowerPoint.
Ensure that there are no excluded columns in the view definition as compared to the criteria definition.
This section describes issues and workarounds related to Oracle BI Publisher. It includes the following topics:
Section 53.7.1, "General Oracle BI Publisher Issues and Workarounds"
Section 53.7.2, "Oracle BI Publisher Security Issues and Workarounds"
Section 53.7.3, "Oracle BI Publisher Delivery Manager Issues and Workarounds"
Section 53.7.4, "Oracle BI Publisher Scheduler Manager Issues and Workarounds"
Section 53.7.5, "Oracle BI Publisher RTF Template Issues and Workarounds"
Section 53.7.6, "Oracle BI Publisher PDF Template Issues and Workarounds"
Section 53.7.7, "Oracle BI Publisher Desktop Tools Issues and Workarounds"
Section 53.7.8, "Oracle BI Publisher Flash Template Issues and Workarounds"
Section 53.7.9, "Oracle BI Publisher Data Template Issues and Workarounds"
Section 53.7.10, "Oracle BI Publisher Report Building Issues and Workarounds"
This section describes general issues and workarounds related to Oracle BI Publisher. It includes the following topics:
Section 53.7.1.1, "JDBC Driver Throws Unsupported Function for setBigDecimal"
Section 53.7.1.5, "Data Model Is Not Editable When Created by Upgrade Assistant"
Section 53.7.1.8, "Missing Data and Charts in the BI Publisher Sales History Report"
Section 53.7.1.12, "WSDL Endpoint URL Incorrect in BI Publisher Web Services"
Data models that include a link between a data set of SQL query type against an Oracle database and a data set of SQL query type against the BI Server based on a numeric database column (used to create a parent-child hierarchical XML data structure with the SQL query against the Oracle database as the parent data set) fail to execute and return the following error: "Java.sql.SQLException: unsupported function at oracle.bi.jdbc.AnaJdbcPreparedStatement.setBigDecimal."
When Oracle BI Publisher is installed in integrated mode with Oracle BI EE, searching the catalog from the BI Publisher user interface (that is, the URL is of the form "http://<host>:<port>/xmlpserver/...") does not work and the following message is returned:
Result Not found Your search - <search criteria> - did not match any documents.
The workaround is to search the catalog from the Oracle BI EE user interface (that is, the URL is of the form "http://<host>:<port>/analytics/...").
When BI Publisher is configured to use the Oracle BI Presentation Catalog as the report repository, the Guest Sign In from the .../xmlpserver URL is not supported.
A user attempting to sign in to the BI Publisher Guest account will encounter the following error: "Error 500 - Internal Server Error."
The workaround to avoid this error is to switch to .../analytics URL and sign in with a named user account.
If you manually enter a repository path to upload the BI Publisher Repository to the Oracle BI Presentation Catalog from the Administration > Server Configuration page, then after you upload the BI Publisher Repository and restart the BI Publisher sever, the path shown for the BI Publisher repository in the Server Configuration page reverts to the default path. However, this does not impact the proper upload of the repository to the Oracle BI Presentation Catalog.
A report that is upgraded from Release 10g to 11g will have a report and a data model created by the Upgrade Assistant. The upgraded data model when seen in the data model editor will not show diagram, data structure and the equivalent code for the data structure. Moreover, the developer or administrator will not be able to edit the data structure. This means that the data model will not allow the developer or administrator to use the Release 11g features editable XML View and Business View.
The workaround is as follows:
Open the data model for editing.
Copy the SQL query statement from the data set.
Create a new data set in the same data model. The following warning is displayed:
"Adding this type of Data Set may break layouts that refer to this data model."
Click OK.
Paste the SQL query into the new data set dialog.
Enter a name for the dataset.
Click OK.
Delete the original data set. The following warning is displayed:
"This item is set as main dataset. Do you want to delete this item?"
Click OK.
Change the data structure in XML View to reflect ROWSET/ROW structure of XML.
Save the data model.
Attempting to connect to BI Publisher shortly after restarting Oracle Process Management and Notification (OPMN) may result in the following error:
"Error Unauthorized Access: please contact the administrator."
After OPMN is started and running, it takes 3 to 5 minutes to start all the Presentation Services processes needed to log in to BI Publisher.
The workaround is to wait 4 to 5 minutes after OPMN is running before attempting to log in. If the error is encountered, clear the browser cache before attempting to log in again.
During installation of Oracle Business Intelligence, if you choose to install only Business Intelligence Publisher (in the Configure Component Screen), then BI Publisher scheduler is not configured by the installer. To configure the scheduler follow these steps:
Login to BI Publisher as administrator.
Click on the Administration link and navigate to Scheduler Configuration in the System Maintenance section.
Make these settings:
In the Scheduler Selection region, select Quartz as the Scheduler from the list.
In the Database Connection region, set the Database ConnectionType to jndi and enter the JNDI name as jdbc/bip_datasource.
Click the Test Connection button to verify the scheduler database connection.
In the JMS Configuration region, select WebLogic as the JMS Provider. A default WebLogic JNDI URL "t3://localhost:9704" will be populated.
If the port number for your installation is different, then edit the JNDI URL.
Click the Test JMS button to verify the JMS setup.
Click the Apply button.
Select the Scheduler Diagnostics tab to check the updated scheduler status.
The BI Publisher report Sales History Report, which is included with the Oracle BI EE 11g, Release 11.1.1.3 samples in the /Shared Folders/Sample Lite/Published Reporting/Reports folder, has missing data and charts.
The workaround is as follows:
Edit the Oracle BI EE analysis Sales by Brand in the /Shared Folders/Sample Lite/Published Reporting/Analyses folder.
From the Subject Areas pane of the Criteria tab, drag and drop the Billed Quantity column from the Base Facts folder of the Sample Sales Lite subject area to the left of the Revenue column in the Selected Columns pane.
Save the Sales by Brand analysis.
Oracle BI Publisher´s Template Builder for Microsoft Word is not compatible with Microsoft Office Live Add-in. The presence of Microsoft Office Live Add-in may cause errors when attempting to install the Template Builder or other unexpected behavior.
The workaround is to uninstall Microsoft Office Live Add-in.
When configuring a JDBC data source connection or an OLAP connection, the list provided in the BI Publisher Add Data Source page includes data sources that are not supported in this release. For the most current list of supported data sources, refer to the System Requirements and Supported Platforms for Oracle Business Intelligence Suite Enterprise Edition 11gR1. The system requirements document is available from this link:
http://www.oracle.com/technology/software/products/ias/files/fusion_certification.html
It is listed with the documents grouped under the Product Area "Additional Oracle Fusion Middleware 11g Release 1 (11.1.1.x) Certifications."
If you are using Internet Explorer 7 as your Web browser and you have selected a bidirectional language for your user interface preference (such as Arabic or Hebrew), the menu options from the global header will not display.
To work around this problem, use Internet Explorer 8 or another supported Web browser.
In release 11.1.1, BI Publisher exposes four Web services:
v2/ScheduleService
v2/ReportService
v2/SecurityService
v2/CatalogService
The list of standalone Web services offered is accessible via http://[hostname]:[portnumber]/[application contextname]/services.
In the WSDL for each Web service, the endpoint for the WSDL URL location (that is, the value for the <wsdlsoap:address location> element) may be incorrectly set to http://localhost:8080, instead of the correct location of the BI Publisher server installation: [machine name] and [port number].
To work around this problem, navigate to the your xmlpserver deployment directory under webapps\xmlpserver and manually update the <wsdlsoap:address location> element in the following files:
CatalogService.wsdl
ReportService.wsdl
ScheduleService.wsdl
SecurityService.wsdl
This section describes issues and workarounds related to Oracle BI Publisher security. It includes the following topic:
By default, the BI Publisher scheduler is configured to use WebLogic Server JMS. The JMS queues are not secured automatically when you configure Oracle Fusion Middleware Security. To secure the JMS queues, you must perform the following:
Enable mutual SSL authentication on bi_server1
Change BI Publisher Scheduler to use T3S protocol for the JMS connection
To enable mutual SSL authentication on bi_server1:
Login to the weblogic console, http://hostname:port/console (that is, http://mymachine:7001/console).
Select Lock & Edit.
Under Domain Structure, select Environment, then Servers, and then from the list of available servers, select bi_server1.
On the Configuration/General tab:
Select the SSL Listen Port Enabled box.
In the SSL Listen Port field, enter the port (that is, 9804).
Click Save.
On the Configuration/SSL tab:
Click Advanced.
In the Two Way Client Cert Behavior box, select Client Cents Requested and Enforced.
Click Save.
Select Release Configuration and activate your changes.
To change BI Publisher Scheduler to use T3S protocol for the JMS connection:
Login to BI Publisher (http://hostname:9704/xmlpserver).
Select Administration.
Select Scheduler Configuration.
In the JMS Configuration region, in the Weblogic JNDI URL field, enter t3s://hostname:9804. This port needs to match the SSL Listen port set in WebLogic.
Click the Test JMS button to verify.
Click Apply.
Please refer to the WebLogic document on how to disable connecting BI Publisher JMS queues from non-SSL port (that is, 9704).
This section describes issues and workarounds related to Oracle BI Publisher Delivery Manager.
There are no known issues at this time.
This section describes issues and workarounds related to Oracle BI Publisher Scheduler Manager.
There are no known issues at this time.
This section describes issues and workarounds related to Oracle BI Publisher RTF templates.
There are no known issues at this time.
This section describes issues and workarounds related to Oracle BI Publisher PDF templates.
There are no known issues at this time.
This section describes issues and workarounds related to Oracle BI Publisher desktop tools.
There are no known issues at this time.
This section describes issues and workarounds related to Oracle BI Publisher Flash templates.
There are no known issues at this time.
This section describes issues and workarounds related to Oracle BI Publisher data templates.
There are no known issues at this time.
This section describes issues and workarounds related to building reports with Oracle BI Publisher. It includes the following topic:
There is no direct conversion between Oracle Reports and Oracle BI Publisher 11g. To convert a report created in Oracle Reports to an Oracle BI Publisher report, follow the two step process:
Convert the Oracle Reports report to an Oracle BI Publisher 10g report following the instructions in the Oracle Business Intelligence Publisher Report Designer's Guide(10g):
http://download.oracle.com/docs/cd/E12844_01/doc/bip.1013/e12187/T518230T518393.htm
Upgrade Oracle BI Publisher 10g to Oracle BI Publisher 11g following the instructions in the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence 11g Release 1 (11.1.1).
This section describes Oracle BI Publisher documentation errata. It includes the following topics:
This section describes documentation errata in the Oracle Fusion Middleware Report Designer's Guide for Oracle Business Intelligence Publisher.
There are no known issues at this time.
This section describes documentation errata in the Oracle Fusion Middleware Administrator's and Developer's Guide for Oracle Business Intelligence Publisher.
There are no known issues at this time.
This section describes issues and workarounds related to developing Oracle Business Intelligence metadata repositories. It includes the following topics:
Section 53.8.1, "General Metadata Repository Development Issues and Workarounds"
Section 53.8.3, "Oracle BI Administration Tool Issues and Workarounds"
This section describes general issues and workarounds related to developing Oracle Business Intelligence metadata repositories. It includes the following topics:
Section 53.8.1.1, "Note about Disallow Online RPD Updates Option in Fusion Middleware Control"
Section 53.8.1.2, "Use of NQClient (BI ODBC Client) Utility Is Deprecated"
The Disallow Online RPD Updates option in the Performance tab of the Capacity Management page in Fusion Middleware Control affects whether you can perform both online and offline updates to repository files, using the Administration Tool or other utilities.
The NQClient (BI ODBC Client) utility is fully deprecated in Release 11g (11.1.1.3) and should not be used. Instead, use the nqcmd utility or one of the many widely available third-party ODBC/JDBC tools to satisfy previous NQClient functionality.
This section describes issues and workarounds related to the Oracle BI Server. It includes the following topic:
Due to an issue in the Oracle Call Interface (OCI) client for the Oracle Database 11g, unexpected Oracle BI Server crashes might occur when the BI Server is running on Microsoft Windows platform and there are a significant number of concurrent users attempting to connect to the Oracle Database 11g.
The work-around is to apply a Windows patch bundle for Oracle Database 11.1.0.7, patch bundle 27 or higher.
This section describes issues and workarounds related to the Oracle BI Administration Tool. It includes the following topics:
Section 53.8.3.1, "Administration Tool Incorrectly Displays Option for Generate Deployment File"
Section 53.8.3.2, "Issue with Online Import Object Checkout"
The Administration Tool provides an option in the Tools > Utilities window for Generate Deployment File. This option appears in error and should not be used.
When using the Administration Tool to import objects in online mode, related objects are not properly checked out. This can lead to repository corruption.
The workaround is to check out all objects before performing the import in online mode. To check out all objects, from the menu bar, select Tools, then select Check Out All.
The Oracle BI Administration Tool multiuser development (MUD) environment enables users to obtain historical information about repository changes, as follows:
Subset changes prior to merge are stored as modified subset repositories.
Each version in the MUD location is stored as repository_name.version_number.
In this release of Oracle Business Intelligence, RPD files are now encrypted with a user-specified repository password. As a result, the Administration Tool can only open repository files that have been fully upgraded and encrypted.
To enable the Administration Tool to open versioned MUD repository files and access MUD history, upgrade all repositories in the MUD directory. Upgrade all repository files in the MUD directory with the following naming patterns, where ddd is the version number:
modified subset of repository_name.ddd
repository_name.ddd
To upgrade MUD repositories so that you can access MUD history:
Run bi-init.cmd (or bi-init.sh on UNIX) to launch a command prompt or shell window that is initialized to your Oracle instance. You can find this utility in:
ORACLE_INSTANCE/bifoundation/OracleBIApplication/coreapplication/setup
Run obieerpdmigrateutil from the resulting shell window with the desired options, as follows:
obieerpdmigrateutil -I input_repository_path -O output_repository_path -L ldif_output_path -U 10g_administrator_username
Where:
input_repository_path is the name and location of the RPD you want to upgrade and encrypt.
output_repository_path is the name and location of the upgraded and encrypted RPD. This value can be the same as the input repository path.
ldif_output_path is the path of the LDIF output file generated by the utility. It contains the users and groups from the old RPD for importing into your LDAP Identity Store.
10g_administrator_username is the Administrator user name for the repository in the previous release.
For example:
obieerpdmigrateutil -I C:\mud_dir\my_repos.001 -O C:\upgr\my_repos.001 -L C:\upgr\ldif\my_ldif.ldif -U Administrator
When prompted, enter the 10g administrator password and a new repository encryption password. Do not forget the repository password, because you cannot open the repository without it. To avoid errors, use the same repository password for all repository files in your MUD environment.
Tip: If you have a large number of MUD repositories, then you might want to create a script to automate the MUD repository migration tasks.
This section describes issues and workarounds related to Oracle Business Intelligence system administration. It includes the following topics:
Section 53.9.1, "General System Administration Issues and Workarounds"
Section 53.9.3, "Deployment, Availability, and Capacity Issues and Workarounds"
Section 53.9.4, "Sign-in and Security Issues and Workarounds"
Section 53.9.5, "Oracle BI Scheduler Issues and Workarounds"
Depending on your Oracle Fusion Middleware implementation, some information in Chapter 4, "Oracle Fusion Middleware Administration" and Chapter 5, "Oracle Enterprise Manager Fusion Middleware Control" might also be relevant.
This section describes general issues and workarounds related to Oracle Business Intelligence system administration. It includes the following topic:
Log file entries for agents might show different Execution Context IDs (ECIDs) from those that appear in Oracle Fusion Middeware Control.
This issue has no workaround.
This section describes issues and workarounds related to configuring Oracle Business Intelligence components (including Answers, Dashboards, Agents, and the Oracle BI Presentation Catalog).
There are no known issues at this time.
This section describes issues and workarounds related to enterprise deployments of Oracle Business Intelligence where high availability, capacity, and performance are typically a priority.
These issues are described in Chapter 6, "Oracle Fusion Middleware High Availability and Enterprise Deployment" of this document.
This section describes issues and workarounds related to security and signing in to Oracle Business Intelligence.
Note:
If you are experiencing security-related issues after upgrading from an earlier release, then also refer to Section 53.5.2, "Security-related Upgrade Issues and Workarounds".This section includes the following topics:
Section 53.9.4.1, "Permission Required to Open Catalog Manager in Online Mode"
Section 53.9.4.2, "Sign-in Might Fail If Username or Password Contains Multibyte Characters"
Only users with the OPSS permission oracle.bi.presentation.catman.manageCatalog can open the Catalog Manager in online mode.
If a user tries to sign in to Oracle Business Intelligence using a username or a password that contains multibyte characters, then the sign-in might fail. This is also the case if Oracle Business Intelligence is configured to work with Oracle Single Sign-On.
This issue has no workaround.
This section describes issues and workarounds related to Oracle BI Scheduler.
There are no known issues at this time.
This section describes issues and workarounds related to integrating Oracle Business Intelligence with other products, including the use of Oracle Business Intelligence APIs. It includes the following topics:
Section 53.10.1, "General Integration Issues and Workarounds"
Section 53.10.2, "Oracle Business Intelligence API Issues and Workarounds"
This section describes general issues and workarounds related to integrating Oracle Business Intelligence with other products.
There are no known issues at this time.
This section describes issues and workarounds related to the use of Oracle Business Intelligence APIs.
There are no known issues at this time.
This section describes issues and workarounds related to integrating Oracle Business Intelligence with other products, including the use of Oracle Business Intelligence APIs. It includes the following topics:
Section 53.11.1, "Product Localization Issues and Workarounds"
Section 53.11.2, "Help System Localization Issues and Workarounds"
This section describes issues and workarounds related to the localization of Oracle Business Intelligence products. It includes the following topics:
When trying to export externalized strings that contain multibyte characters, the option to save the file using ANSI encoding does not work properly.
To work around this problem, save the file using UTF-8 or Unicode encoding.
If a user name contains superscript letters, the user will not be able to perform basic functions within Oracle Business Intelligence. For example, creating a data model for published reporting, uploading a layout template, or scheduling a job.
To work around this problem, do not include superscript letters in a user name.
This section describes issues and workarounds related to the localization of Oracle Business Intelligence help systems. It includes the following topic:
None of the Oracle Business Intelligence help systems are translated in Release 11.1.1.3.
This section describes errata in Oracle Business Intelligence documentation and help systems. It includes the following topics:
Section 53.12.1, "General Oracle Business Intelligence Documentation Errata"
Section 53.12.3, "Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence"
Section 53.12.12, "Oracle Business Intelligence Help System Errata"
This section describes general errata in the Oracle Business Intelligence documentation.
There are no known issues at this time.
This section describes documentation errata in the Oracle Fusion Middleware Quick Installation Guide for Oracle Business Intelligence.
There are no known issues at this time.
This section describes documentation errata in the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence. It includes the following topic:
In Section 4.6.1, "Installing Oracle Business Intelligence Client Tools" of the Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence, the following components were incorrectly included in the list of administration clients:
Oracle Business Intelligence ODBC Driver
Oracle Business Intelligence JDBC Driver
This section describes documentation errata in the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topic:
There is an error in the first paragraph of Chapter 4, "Upgrading Oracle Business Intelligence Enterprise Edition" in the Oracle Fusion Middleware Upgrade Guide for Oracle Business Intelligence Enterprise Edition. The paragraph incorrectly reads:
"This chapter describes how to upgrade your existing Oracle Business Intelligence Enterprise Edition (Oracle BI EE) 10g Release 3 (10.3.2 or later) environment to Oracle Business Intelligence 11g."
The release number mentioned in the paragraph is incorrect. The paragraph should read:
"This chapter describes how to upgrade your existing Oracle Business Intelligence Enterprise Edition (Oracle BI EE) 10g Release 3 (10.1.3.2 or later) environment to Oracle Business Intelligence 11g."
This section describes documentation errata in the Oracle Fusion Middleware User's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topics:
Section 53.12.5.1, "Error in Chapter 3, Section Entitled "Adding Totals to Tables and Pivot Tables""
Section 53.12.5.2, "Information on Taking Ownership of Objects"
Chapter 3 contains a section named "Adding Totals to Tables and Pivot Tables." That section contains a four-step procedure for adding totals to a view. Step 4 was included in that procedure in error and must be removed.
The Properties dialog contains an Ownership area in which you can take ownership of an object in the catalog. The options in this area are not described in the documentation. This area displays only if the proper privileges were assigned to the user, group, or role. You can click links to set the ownership of an object or of an object and all its sub-objects.
This section describes documentation errata in the Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topics:
Appendix A, "Managing the Repository Lifecycle in a Multiuser Development Environment" includes the following sentence:
"The RCU tables can be shared by multiple development sandboxes without conflict."
This sentence is incorrect. Each separate Oracle Business Intelligence system requires its own set of RCU database schemas. See Oracle Fusion Middleware Installation Guide for Oracle Business Intelligence for information about RCU schema requirements.
Oracle Fusion Middleware Metadata Repository Builder's Guide for Oracle Business Intelligence Enterprise Edition provides information about connecting to Hyperion Financial Management data sources. The instructions work if you are using a Hyperion Financial Management 9.3.1 client, but do not work for Hyperion Financial Management 11g clients.
Follow these steps to connect to Hyperion Financial Management data sources with an 11g client:
Open opmn.xml for editing. You can find opmn.xml at:
ORACLE_INSTANCE/config/OPMN/opmn/opmn.xml
Locate the ias-component tag for the JavaHost process. For example:
<ias-component id="coreapplication_obijh1">
Within the environment tag, add new variables required for Hyperion Financial Management, using the following example as a guide. Update the actual values as appropriate for your installation.
<variable id="HYPERION_HOME" value="C:/oracle/Middleware/EPMSystem11R1"/> <variable id="EPM_HOME" value="C:/MW_Home/Oracle_BI1/common/jlib/11.1.2.0"/> <variable id="ADM_HOME" value="C:/MW_Home/Oracle_BI1/common/ADM/11.1.2.0"/> <variable id="HFM_HOME" value="$HYPERION_HOME/products/FinancialManagement/Client"/> <variable id="ADM_ESS_NATIVE_HOME" value="$ADM_HOME/"/> <variable id="CSS_HOME" value="c:/MW_Home/Oracle_BI1/common/CSS/11.1.2.0"/>
Update the PATH variable to include ADM_HOME/bin and the client and common subdirectories of HYPERION_HOME. For example:
<variable id="PATH" value="C:\oracle\product\10.2.0\db_1\BIN$:$ADM_HOME/bin$:$HYPERION_HOME/products/FinancialManagement/Common$:$HYPERION_HOME/products/FinancialManagement/Client$:$ORACLE_HOME/common/ODBC/Merant/5.3/lib$:$ORACLE_HOME/bifoundation/server/bin$:$ORACLE_HOME/bifoundation/web/bin$:$ORACLE_HOME/bifoundation/odbc/lib$:$ORACLE_INSTANCE$:$ORACLE_HOME/lib" append="true"/>
Locate the data id="start-args" tag and update the classpath attribute to include the location of required jar files. For example:
<data id="start-args" value="-Xmx1024M -Djava.security.manager=default -DXDO_
FONT_DIR=$ORACLE_HOME/common/fonts -Djava.security.policy=$ORACLE_
INSTANCE/config/$COMPONENT_TYPE/$COMPONENT_NAME/java.policy
-Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration
-Doracle.core.ojdl.logging.config.file=$ORACLE_INSTANCE/config/$COMPONENT_
TYPE/$COMPONENT_NAME/logging-config.xml -Doracle.home=$ORACLE_HOME
-Doracle.instance=$ORACLE_INSTANCE -Doracle.component.type=$COMPONENT_TYPE
-Doracle.component.name=$COMPONENT_NAME -classpath $COMMON_COMPONENTS_
HOME/modules/oracle.odl_11.1.1/ojdl.jar$:$ORACLE_
HOME/bifoundation/javahost/lib/core/sautils.jar$:$ORACLE_
HOME/bifoundation/javahost/lib/core/mad.jar$:$ORACLE_
HOME/bifoundation/javahost/lib/core/sawconnect.jar$:$ORACLE_
HOME/bifoundation/javahost/lib/core/javahost.jar$:$COMMON_COMPONENTS_
HOME/modules/oracle.xdk_11.1.0/xmlparserv2.jar$:$ORACLE_
HOME/opmn/lib/ons.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.jps_
11.1.1/jps-manifest.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.jps_
11.1.1/jps-api.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.jps_
11.1.1/jps-common.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.jps_
11.1.1/jps-internal.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.nlsrtl_
11.1.0/orai18n.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.nlsrtl_
11.1.0/orai18n-collation.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.nlsrtl_
11.1.0/orai18n-mapping.jar$:$COMMON_COMPONENTS_HOME/modules/oracle.dms_
11.1.1/dms.jar$:$EPM_HOME/epm.jar$:$ADM_HOME/lib/adm.jar$:$ADM_HOME/lib/ap.jar$:$CSS_HOME/lib/css.jar$:$CSS_HOME/lib/common-model.jar$ com.siebel.analytics.javahost.standalone.Main"/>
Save and close the file.
Go to the directory ORACLE_HOME/bifoundation/javahost/lib/obisintegration/adm and delete all jar files except for admintegration.jar and admimport.jar.
Restart the JavaHost process.
This section describes documentation errata in the Oracle Fusion Middleware System Administrator's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topics:
Section 19.3.2, "Manually Configuring for Graphs and Gauges," describes the DefaultImageType element. This element is no longer supported, and its description must be removed from the guide.
Section 18.6.4 describes how to work with the properties of objects in the catalog. The section includes a step for selecting the owner of an object. The section must be updated to state that the Owner list now includes the name that you used to log into Catalog Manager. Therefore, you can use this list to select yourself as the owner of the object, if you have the appropriate permissions. You can select Apply Recursively to take ownership of the object and all its sub-objects.
This section describes documentation errata in the Oracle Fusion Middleware Security Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topic:
Section 5.3, "Configuring the Web Server to Use HTTPS Protocol" contains the following information:
These properties are set by editing MW_Home/user/projects/domains/bifoundation_domain/bin/startManagedWebLogic.sh (or .bat), and adding the properties to the end of the JAVA_OPTIONS value. Note that any \ character in a path must be escaped with another \ character.
For example, the following edits are made if using the demonstration Oracle WebLogic Server certificate:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djavax.net.ssl.trustStore="C:/biee/wlserver_10.3/server/lib/DemoTrust.jks" -Djavax.net.ssl.trustStorePassword=""
If this step is omitted, then Web Services for SOA and BI Search fail.
This information is incorrect. It should read as follows:
These properties are set by:
Editing the following:
In Linux, MW_Home/user_projects/domains/bifoundation_domain/bin/setDomainEnv.sh
In Windows, MW_Home\user_projects\domains\bifoundation_domain\bin\setDomainEnv.cmd
Adding the properties to the end of the JAVA_OPTIONS value
Note that any \ character in a path must be escaped with another \ character.
For example, the following edits are made if using the demonstration Oracle WebLogic Server certificate:
In Linux:
JAVA_OPTIONS="${JAVA_OPTIONS} -Djavax.net.ssl.trustStore=MW_Home/wlsserver_10.3/server/lib/DemoTrust.jks -Djavax.net.ssl.trustStorePassword="
In Windows:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Djavax.net.ssl.trustStore="MW_Home/wlserver_10.3/server/lib/DemoTrust.jks" -Djavax.net.ssl.trustStorePassword=""
If these options are not set, login will fail.
This section describes documentation errata in the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence.
These issues are described in Section 6.4.5, "Documentation Errata for the Oracle Fusion Middleware Enterprise Deployment Guide for Oracle Business Intelligence" of this document.
This section describes documentation errata in the Oracle Fusion Middleware Enterprise Developer's Guide for Oracle Business Intelligence Enterprise Edition. It includes the following topic:
The "New Features" section and Chapter 3, "Integrating Oracle Business Intelligence Presentation Services With Oracle WebCenter" provide information on using JDeveloper to create and configure a WebCenter application that integrates with the Oracle BI Presentation Catalog. This information is in error.
Also in error is the information on the WebCenter in the following sections:
Section 1.4.1.2, "Installing the Required JDeveloper Extensions"
Section 1.8, "Adding or Modifying a Presentation Services Connection After Deployment"
Section 1.8.1.2, "Adding or Modifying a Presentation Services Connection"
A fully productized integration of Oracle Business Intelligence with Oracle JDeveloper and Oracle WebCenter is not available with this Oracle Business Intelligence release and the 11.1.1.3.0 releases of Oracle JDeveloper and Oracle WebCenter.
This section describes documentation errata in the Oracle Fusion Middleware Integrator's Guide for Oracle Business Intelligence Enterprise Edition.
There are no known issues at this time.
This section describes errata in the Oracle Business Intelligence help systems.
There are no known issues at this time.