| Oracle® Business Intelligence Suite Enterprise Edition Release Notes Release 10.1.3.4.2 Part Number E10404-34 |
|
|
View PDF |
| Oracle® Business Intelligence Suite Enterprise Edition Release Notes Release 10.1.3.4.2 Part Number E10404-34 |
|
|
View PDF |
This chapter provides release notes for Oracle BI Publisher.
This section provides release notes for Oracle Business Intelligence Publisher (Oracle BI Publisher). It contains the following topics:
Section 3.1.1, "JDK 5.0 Bug Affects Oracle BI Publisher Performance"
Section 3.1.2, "Shuttle Icons Might Appear as Text Strings in HP-UX PA-RISC (32-Bit) Installation"
Section 3.1.4, "PDF Form Processor Lacks Support for Landscape Template for Repeatable Fields"
Section 3.1.5, "Flash Report PDF Output Might Not Render with Adobe Reader 7.0.x"
Section 3.1.7, "Alternate Table Rows Formatting Not Working in HTML, RTF, and Excel Outputs"
Section 3.1.8, "Date Formats Might Display Incorrectly in Microsoft Excel Output"
Section 3.1.9, "Header and Footer Margin from Edge Not Preserved in RTF Output"
Section 3.1.10, "Rounding Issue When Adding Decimal Numbers"
Section 3.1.11, "CUPS Server Does Not Appear as a Delivery Destination in Clustered Environment"
Section 3.1.13, "Concatenated Data Sources Do Not Load Properly to the Template Builder"
Section 3.1.17, "Scheduler Database Type Might Reset to Different Version"
Section 3.1.18, "Images Do Not Generate Correctly Without X Server"
Section 3.1.19, "Reports with Multibyte Character File Names Do Not Download Properly"
Section 3.1.20, "Multibyte Character File Names Not Supported at Runtime"
Section 3.1.22, "Enabling SSL Is Recommended for Web Service Communication"
Section 3.1.23, "Using a SSL-Enabled Web Services as a Data Source"
Section 3.1.25, "Oracle BI Publisher Web Client Might Enter Stale State"
Section 3.1.27, "Proxy Configuration Might Be Required for Accessing Data Sources Over the Internet"
Section 3.1.28, "Internal Server Error 500 and 501 When Using Discoverer Worksheet as a Data Source"
Section 3.1.33, "Issue with Multibyte Character User Names and LDAP Server"
Section 3.1.37, "Fixes for Section 508 Accessibility Standards"
Section 3.1.38, "Extended ASCII Characters Are Not Correctly Created in XML Data"
Section 3.1.42, "Adobe Acrobat Reader 8.0 Not Supported with PDF Mapping"
Section 3.1.43, "Privileges Not Being Inherited Properly Throughout LDAP Group Hierarchy"
Section 3.1.44, "When the Guest Folder Name Is Changed, Users Are Prompted to Log In"
Section 3.1.46, "Current_Server_URL Does Not Return a Value"
Section 3.1.48, "Reports Using Data Template Fail with Data Not Defined"
Section 3.1.51, "Deleted User Folder Must Be Manually Deleted from the Repository"
Section 3.1.53, "Unable to Access PublicReportServices Web Service WSDL"
Section 3.1.54, "Changes to Oracle BI Publisher Web Services ScheduleRequest Complex Types"
Section 3.1.56, "Changes to the ParamNameValue Complex Type"
Section 3.1.57, "500 Internal Server Error Appears After Choosing Link to Document Only"
Section 3.1.58, "Installer Creates Configuration Files Without Fully Qualified Host Names"
Section 3.1.65, "MHTML Output Format Not Supported on Mac OS X Client"
Section 3.1.66, ""Croatian" Is Not Properly Translated in the Locale Selection List"
Section 3.1.67, "Parameter Values for Bursting to a Printer Incorrectly Documented"
Section 3.1.72, "Validation of Data Type Added for Parameters Defined in the Data Template"
Section 3.1.73, "Microsoft SQL Server 2008 Not a Choice in the Add Data Source Page"
Section 3.1.74, "Microsoft SQL Server 2008 Not a Choice in the Scheduler Configuration Page"
Section 3.1.75, "Netezza 4.5 Not a Choice in the Add Data Source Page"
Section 3.1.76, "File Required for BI Publisher Single Sign-On Configuration Not Installed"
Section 3.1.79, "BI Publisher References Discoverer Worksheets by Name"
Section 3.1.80, "BI Publisher Report Parameters Support Text Box or List of Values"
Section 3.1.81, "Superuser Privileges Are Limited to Functions on Admin Page"
Section 3.1.82, "End on Even or End on Odd Page Feature Only Supported for PDF Output"
Section 3.1.83, "Analyzer for Excel Cannot Process Very Large Data Files in Native Mode"
Section 3.1.84, "BI Publisher Deployments to WebLogic 10.3 Require Additional Setting at Startup"
Section 3.1.86, "Error When Opening BI Publisher PowerPoint (MHTML) Output in PowerPoint 2010"
Section 3.1.87, "Different BI Publisher Instances Cannot Share Scheduler Schema"
Section 3.1.88, "Avoid the Use of Soft Returns in RTF Templates"
Section 3.1.89, "First Day of Week Displayed in the Date Picker Not Correct for Some Locales"
Section 3.1.90, "Multibyte Characters in Chart Titles May Appear Garbled"
Section 3.1.91, "Bursting Engine Does Not Support Attributes in XML Data"
Section 3.1.92, "New Features Not Documented in the 10.1.3.4.2 New Features Guide"
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
There is a bug in Java SE Development Kit (JDK) 5.0 version 1_5_0_7 that impacts the performance of Oracle BI Publisher. For better performance, upgrade to JDK 5.0 update 11 (1_5_0_11). Download and install this update from the following location:
http://java.sun.com/javase/downloads/index_jdk5.jsp
After installing the JDK update, you must modify the OC4J start-up script or batch file to point to the new JDK location.
To modify the OC4J start-up script:
On Windows, open <OracleBI>\oc4j_bi\bin\oc4j.cmd for editing. On Linux or UNIX computers, open $OracleBI\setup\oc4j.sh for editing.
Set the JAVA_HOME variable to point to the new JDK location. For example, JAVA_HOME=D:\Program Files\Java\jdk1.5.0_11.
If you installed Oracle BI Presentation Services using the Basic Install option on the computer where JDK has been updated, then you must modify the instanceconfig.xml file to point to the new JDK location:
To modify the instanceconfig.xml file:
Open the <OracleBIData>/web/config/instanceconfig.xml file for editing.
Set the JavaHome parameter to the point to the new JDK location. For example, <JavaHome>D:\Program Files\Java\jdk1.5.0_11</JavaHome>.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
This issues applies only to installations of BI Publisher on the HP-UX PA-RISC (32-bit)
operating system.
After first installing BI Publisher, the "Move" and "Move All" shuttle icons that enable you to move items from one list to another might appear as text strings rather than icons. To correct this issue, restart the BI Publisher server.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If scroll bars or a report appear clipped when you have an Oracle BI Publisher report embedded in a dashboard, then you might need to increase the height property of the object on the dashboard page. Edit the properties of the Oracle BI Publisher object on the dashboard page and try a height setting greater than 550 pixels until you find one that correctly displays the entire report and the scroll bar controls.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When you create PDF output in Portrait mode with repeatable fields, the report output is correctly formatted. However, when the same report is created in Landscape mode, the table headers are correct but the following occurs:
Repeating line information (that is, each data field in the iteration) rotates by 90 degree.
The repeating lines spread across in a horizontal direction from right to left instead of top to bottom in a vertical direction.
This issue has no workaround.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
PDF output generated from BI Publisher Flash templates might not render properly if you are using Adobe Reader 7.0.x.
To work around this issue, upgrade to Adobe Reader version 7.1 or higher.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The RC4 algorithm is less secure than newer algorithms such as AES and is not recommended for use in new applications. However, the RC4 algorithm is the only supported encryption algorithm for Adobe Acrobat 6.0. Support for AES encryption for Adobe Acrobat 7.0 and higher versions is planned for future releases of Oracle BI Publisher.
This issue has no workaround.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The user guide contains the "Row Formatting" topic that describes how to set the background color on alternate rows in a tabular report. This description works for PDF output only. In HTML, RTF, and Excel output formats, the alternate rows do not show the background color. In these output formats, all the rows appear with a white background.
This issue has no workaround.
This issue applies to Versions 1 0.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When generating Microsoft Excel output from an RTF template, Excel might ignore or misinterpret formatting of date values. This might be more likely to occur when you run the operating system in languages other than English. You might be able to work around this issue by removing the date format applied to the field.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Microsoft Word provides a Page Setup option for specifying the margin for the headers and footers from the edge of the page. This option is available by choosing the File menu, then Page Setup, then the Margins tab, and the From edge box. This margin setting is not retained when the output format is RTF. The output is created with the default margin settings instead. The margin settings do work correctly for other output formats such as HTML, PDF, and Excel.
This issue has no workaround.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
As Oracle XDK conforms to XSL standards for IEEE 754, you might encounter rounding issues when adding numbers that are decimals. For example, suppose you add 13683.80 and 516.39, using this syntax in Oracle BI Publisher:
<?13683.80 + 516.39?>
The value returned is 14200.189999999999 which is a limitation based on the IEEE 754 Binary Floating-Point-Arithmetic.
To work around this issue, use the format-number function or the round syntax as shown here to obtain a return value of 14200.19:
<?format-number:(13683.80 + 516.39);'D99'?>
or
<?(round((13683.80 + 516.39)*100) div 100)?>
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4.1 and 10.1.3.4.2.
If you are using a clustered environment and you have a CUPS server implemented as a delivery option with no other printers defined, then you might not see the CUPS Server as a delivery option.
To work around this problem, add a real or dummy printer destination by creating an entry in the Admin > Delivery > Printer interface.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When viewing a report layout that has a chart in Excel output, you might not see the chart and might instead see only a small icon in the place where you expect the chart to be.
To work around this problem, you must unblock security on image URLs, as described in the follow steps:
Open the WEB-INF/web.xml file.
Find the following block:
<filter-mapping> <filter-name>SecurityFilter</filter-name> <url-pattern>/xdo/tmp/*</url-pattern> </filter-mapping>
Change the <url-pattern> element as shown:
<filter-mapping> <filter-name>SecurityFilter</filter-name> <url-pattern>/xdo/tmp/*.tmp</url-pattern> </filter-mapping>
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If the data source is concatenated XML from multiple SQL queries, then the XML data does not load properly to the Template Builder from the direct connection to the Oracle BI Publisher server.
To work around this issue, after building the data model, generate sample data and save it to an accessible directory. Use the Template Builder's load data function (choose Oracle BI Publisher, Data, and Load Sample XML Data) to load the report data to the Template Builder. For more information on using the Template Builder in disconnected mode, see the Oracle Business Intelligence Publisher Report Designer's Guide.
This issue applies to Versions 10.1.3.4 and 10.1.3.4.1. This issue is fixed in 10.1.3.4.2.
When using the Template Builder, if you attempt to insert a group or a repeating group around a chart, then no dialog box is displayed to allow you to specify the properties of the repeating group. To work around this issue, insert a temporary field above the chart, then select that field and the chart before inserting the repeating group. The properties dialog is displayed and you can define the repeating group. After you insert the repeating group, you can delete the temporary field.
Follow these steps:
Place your cursor before the chart in the template.
From the Oracle BI Publisher menu select Insert, then Field.
Select any element from your data displayed in the Field dialog and insert
it before the chart.
After the field has been inserted, select the field and the chart.
From the Oracle BI Publisher menu select Insert, then Repeating Group.
Specify the properties for the repeating group in the BI Publisher Properties dialog, and insert the repeating group.
After the repeating group has been inserted, delete the temporary field
you created before the chart.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, and 10.1.3.4. This issue is fixed in 10.1.3.4.1.
The online help included with the Template Builder for Microsoft Word Add-in contains an incorrect description of setting the font size for Tree View panes and Properties panes. The description is found on the help page for the Options Dialog, under the UI tab description. The font size setting has been removed from the Options, UI tab; therefore the section titled "Font Size" on the help page is incorrect and should be disregarded.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Starting with version 10.1.3.2.1, if the administrator has not correctly configured the Oracle BI Publisher scheduler, then the Schedules tab and the Schedule buttons are disabled even when the user has the XMLP_SCHEDULER role. To enable the Schedules tab and the Schedule button, you must configure and install the Scheduler tables.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
On the Scheduler Configuration page, after you select your database type and apply your settings, the database type might reset to a different version of your selected type in the user interface. Although the type displays differently on the Scheduler Configuration page this has no impact on the underlying implementation or the functionality of the scheduler.
This might occur in the following cases:
Microsoft SQL Server 2000 resets to Microsoft SQL Server 2005
IBM DB2 v8 resets to IBMDB2 v9
MySQL 5.0 resets to MySQL 4.1
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you run Oracle BI Publisher server on a UNIX or Linux computer that does not have an X Server installed, then reports that contain images might not be properly generated.
To work around this issue if you run Java 1.4.2 or later, start the environment with a headless implementation. Specify the following property at the java command line:
-Djava.awt.headless=true
For JDK versions before 1.4.2, see the documentation on how to implement X Host for your environment.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If a report file name contains multibyte characters and you download the report by selecting the Report Actions icon then clicking Download this report, then the file names in the generated zip file are invalid. This is due to a Java bug (details available from the Sun Developer Network at: http://bugs.sun.com/bugdatabase/view_bug.do;:YfiG?bug_id=4244499). Consequently, the downloaded report zip file cannot be uploaded back to the Oracle BI Publisher server. To work around this issue, use only ASCII characters in report file names.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Because the encoding of multibyte character file names is dependent on the operating system and locale of the runtime environment, Oracle BI Publisher cannot support multibyte characters in file names. To work around this issue, use only ASCII characters in file names.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Oracle BI Publisher does not support column-level time zone settings applied in Oracle BI Presentation Services. Oracle BI Publisher reports that use Oracle BI Answers requests with column-level time zone settings might result in different dates displayed in Oracle BI Presentation Services and Oracle BI Publisher. This is not an issue for reports without column-level time zone settings, if the User Time Zone setting for Oracle BI Publisher and Oracle BI Presentation Services is the same.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Oracle recommends that you enable HTTPS on the middle tier computer that is hosting the Web services, because the trusted user name/password that is passed can be intercepted. This also pertains to Web services that are used for communication between Oracle BI Publisher and Oracle BI Presentation Services and between Oracle BI Publisher and Oracle BI Discoverer.
Once you set up SSL, follow the instructions in Section 3.1.23, "Using a SSL-Enabled Web Services as a Data Source" to import certificates.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you receive errors when making calls to a Web service that is protected through Secure Sockets Layer (SSL) (that is, uses https://), then you might need to export the certificate from the Web server hosting the Web service and import it into the Java keystore on the computer that is running Oracle BI Publisher. An example error might be: "SSL received a record that exceeded the maximum permissible length".
The steps for importing the certificate are:
Navigate to the HTTPS site where the WSDL resides.
Download the certificate following the prompts (the prompts you see vary depending on the browser that you use).
Install the Certificate into your keystore using the Java keytool, as follows:
keytool -import -file <certfile> -alias <certalias> -keystore <keystore file>
(Conditional) If you do not yet have a system-wide keystore for Java set up, then set the JAVA_OPTS environment variable to tell the BI Publisher server where to find the keystore, as follows:
set JAVA_OPTS=-Djavax.net.ssl.trustStore=<keystore file>
Note:
If you set the -keystore option in Step 3 to your {java.home}/lib/security/cacerts directory, this step is not required because {java.home}/lib/security/cacerts is a system-wide keystore.
Restart the application server.
These steps should not be required if the server certificate is linked to a certificate authority (for example, Verisign). But if the Web service server is using a self-generated certificate (for example, in a testing environment), then these steps are required.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If your system is SSO-enabled, then you must modify your mod_osso.conf file to disable SSO to allow Web service communication between Oracle BI Publisher and its client components, the Template Builder and the Excel Analyzer.
To open up the xmlpserver to allow the Web services, enter the following directives in the mod_osso.conf file:
<Location /xmlpserver/services/>
require valid-user
AuthType Basic
Allow from All
Satisfy any
</Location>
<Location /xmlpserver/report_service/>
require valid-user
AuthType Basic
Allow from All
Satisfy any
</Location>
<Location /xmlpserver/ReportTemplateService.xls/>
require valid-user
AuthType Basic
Allow from All
Satisfy any
</Location>
For the complete procedure for setting up Oracle BI Publisher with Oracle Single Sign-On, see the BI Publisher documentation.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
After extended use, the Oracle BI Publisher Web Client might enter a state in which the top header frame colors appear reversed (blue screen objects appear white), however, the navigation links remain white. Therefore you might not be able to see Welcome, <username> Preferences Sign Out Help. To correct this problem, restart the browser.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you work with multiple languages in the BI Publisher Template Builder for Word and you want to show and input the text on the Template Builder dialogs correctly, then you must set the client operating system regional settings for the target text.
To set the Regional and Language Options in Microsoft Windows:
From the Windows Control Panel, choose Regional and Language Options.
Click the Advanced tab.
Under Language for non-Unicode programs, select the appropriate language from the list.
The Template Builder does not support other languages than those available from the system regional settings.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you want to use external Web Services or HTTP data sources and the Oracle BI Publisher server is set up behind a firewall or requires a proxy to access the Internet, then you must configure Oracle Containers for J2EE (OC4J) or your supported J2EE application server to be aware of the proxy.
To configure OC4J:
Edit the <Oracle_Home>\oc4j\bin\oc4j.cmd file.
Locate the following lines below the 'rem JVMARGS' line:
set JVMARGS=-Djava.library.path=C:\oracle\bi\server\Bin;C:\oracle\bi\web\bin-DSAROOTDIR=C:\oracle\bi -DSADATADIR=C:\oracle\bidata -XX:MaxPermSize=128m -Xmx512m %OC4J_JVM_ARGS%
Insert the following string after the 'set JVMARGS=' part of the line:
-Dhttp.proxyHost=<proxy.mycompany.com> -Dhttp.proxyPort=80
For example, after inserting the above string, the new 'set JVMARGS=' line should look like the following:
set JVMARGS=-Dhttp.proxyHost=<proxy.mycompany.com> -Dhttp.proxyPort=80 -Djava.library.path=C:\oracle\bi\server\Bin;C:\oracle\bi\web\bin -DSAROOTDIR=C:\oracle\bi -DSADATADIR=C:\oracle\bidata -XX:MaxPermSize=128m -Xmx512m %OC4J_JVM_ARGS%
For information about configuring other application servers, consult the documentation.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If the HTTP server where Oracle BI Publisher is running is timing out when using Oracle BI Discoverer worksheets in the report data model, then you might encounter either of the following errors:
500 Internal Server Error (The server encountered an internal error or misconfiguration and was unable to complete your request.)
Error 501
If you encounter error 500 or 501, then the HTTP server where Oracle BI Publisher is running might be timing out before the Discoverer Web service returns the data from the worksheet. If so, you can correct this problem by increasing the Timeout value and decreasing the KeepAliveTimeout value in the file <Oracle_Home>\Apache\Apache\conf\httpd.conf.
For example you might change the Timeout value from 7200 to 10000, and the KeepAliveTimeout value from 150 to 30.
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1. These features were added to the 10.1.3.4 versions of the BI Publisher documentation.
Some additional new features are included in this release that are not documented in the Oracle Business Intelligence New Features Guide. Those features are listed here with some descriptions.
Report Definition Features:
Oracle BI Publisher's data template data source now provides native support for BLOB, CLOB, long and raw data types.
When defining parameters for a report, if you select Menu as the parameter type, you now have the option under the "Can select all" check box to choose between "Null value passed" and "All values passed". Previously, the selection for "all" passed a null value by default.
Properties added to the Runtime Configuration page:
RTF Output: Default Font - enter the default font name and size (for example: Arial:12) to use when no font is defined. This is particularly useful to control the sizing of empty table cells in generated reports.
HTML Output: Use percentage width for table columns - set this property to True to render table columns according to a percentage value of the total width of the table rather than as a value in points.
FO Processing:
Disable external references - a "True" setting (default) disallows the importing of secondary files such as sub-templates or other XML documents during XSL processing and XML parsing. This increases the security of your system. Set this to "False" if the report or template calls external files.
FO Parsing Buffer Size - (default 1,000,000) sets the size of the buffer for the FO Processor. When the buffer is full, the elements from the buffer are rendered in the report. Reports with large tables or crosstabs might require a larger buffer to properly render those objects in the report. Increase the size of the buffer at the report-level for these reports. Note that increasing this value affects the memory consumption of the system.
RTF Template Enhancements
Report Viewing and Output Features:
Support for comma-delimited value (CSV) output - CSV is supported as an output for any report with a simple <rowset>/<row> data structure.
Views created in the online Analyzer can be saved as templates.
When in View mode, you now see "Link to this Report" displayed on the page. This enables you to capture the URL of the currently viewed report. The Link to this Report selection has four options:
Current Page
No Header
No Parameters
Document Only
Administration Features:
For the LDAP security model, a new property, Group Retrieval Size, has been added. This enables support of the LDAPv3 control extension for simple paging of search results. By default, pagination is not used. If this property is provided then the value determines the number of results to return on a page (for example, 200).
Your LDAP server must support control type 1.2.840.113556.1.4.319 to support this feature, such as OID 10.1.4. See your LDAP server documentation for information on support of this control type. For more information about LDAP pagination and the required control type, see the article: RFC 2696 LDAP Control Extension for Simple Paged Results Manipulation.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If SSO is enabled, the Report Editor panel might fail to display correctly if you are also using Internet Explorer 6.0 as the browser. To work around this issue, use either Internet Explorer 7.0 (or later supported versions) or Firefox 2.0 (or later supported versions).
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4.1, and 10.1.3.4.1.2.
If you want to use both the Oracle BI Publisher Analyzer for Excel and the Oracle BI Add-in for Microsoft Office, then you must install the Oracle BI Publisher Analyzer for Excel first. If you install the Oracle BI Add-in for Microsoft Office first, then you must uninstall it before you can install the Oracle BI Publisher for Analyzer for Excel, then reinstall the add-in.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
This issue applies to Sun Java System Web Server deployments only.
To enable users to download and install the Analyzer for Microsoft Excel from their BI Publisher session, you must update your Web server mime.types file as follows:
Locate the line:
type=magnus-internal/cgi exts=cgi,exe,bat
Update it as follows:
type=magnus-internal/cgi exts=cgi,bat
Locate the line:
type=application/octet-stream exts=bin
Update it as follows:
type=application/octet-stream exts=bin,exe
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4.1, and 10.1.3.4.2.
If you have configured Oracle BI Publisher to use an LDAP server, users with multibyte characters in their user name cannot see the Admin tab, even when granted the Administration Role. To work around this issue, create a user name with ASCII characters for users that need the Administration role.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4.1, and 10.1.3.4.2.
If you create an Analyzer template with multibyte characters in the template name and run the report by selecting the View link or button, then you receive the following error:
500 Internal Server Error
Servlet error: An exception occurred. The current application deployment descriptors do not allow for including it in this response. Please consult the application log for details.
If you select View again, then the report renders correctly. To work around this issue, use only ASCII characters in template names, or turn off the auto-run option for the report.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you are using the Template Builder for Word on Microsoft Windows XP and have applied the Microsoft Security Update for Windows XP KB936021, then you might receive the following error when trying to load XML data:
Compile error in hidden module module-starter.
To work around this issue, do the following:
Close Microsoft Word.
From the Windows Start Menu, select Programs, then Oracle BI Publisher Desktop, then Template Builder for Word Language.
Select your language and click OK.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you integrate Oracle BI Publisher Enterprise with Oracle E-Business Suite, you might not be able to see the Admin tab after logging in to Oracle BI Publisher with an E-Business Suite user who has the appropriate Oracle BI Publisher responsibilities. This results when the database NLS_LANG setting does not match the OC4J NLS_LANG setting.
OC4J derives its NLS_LANG value from the operating system locale. Therefore, to resolve this issue, you must define the LANG environmental variable for your OC4J operating system with the proper locale name to match the NLS_LANG setting for the E-Business Suite database. For example, if OC4J is deployed on Linux, and the NLS_LANG for the E-Business Suite database is defined as "American_America.UTF8", then you must define the LANG environmental variable for your Linux OS as "en_US.UTF-8".
For more information on setting this variable, see the following notes on My Oracle Support:
Note: 264157.1: The Correct NLS_LANG Setting in UNIX Environments
Note: 351919.1: Globalization Support : JavaVM, Oracle JDBC Driver, NLS_LANG and OC4J
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
Three areas of the BI Publisher View report page have been enhanced to meet accessibility standards. These are the following:
An alternate text tag has been added to the Oracle logo in the banner.
Proper label tags for assistive technology have been added to the Parameter, Template, and Output format lists.
A "Skip Navigation" tag has been added to the navigation links.
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
When using Oracle BI Publisher's data template to generate XML data, extended ASCII characters, such as é or ë are not created correctly in the XML data when the property scalable_mode is set to "on." This property is set in the <properties> section of the data template as follows: <property name="scalable_mode" value="on"/>.
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
On certain platforms, when generating a report in PDF format from the View Report page, the "processing" or "busy" indicator might not appear to indicate that Oracle BI Publisher is processing the request, leaving the user unsure if the submit action was successful.
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
If you use the <?xdofx:chr(n)?> function in an RTF template, then you might encounter the following error when trying to run or preview the report:
oracle.xdo.parser.v2.XPathException: Extension function error: Method not found 'chr'
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
If you are using Oracle BI Publisher's bursting feature and your bursting job includes PDF reports to be sent to a printer, then the print reports might fail with the following error:
Client: (40A) Document Format Not Supported This is caused by the setting of the document content type to application/PDF by the bursting engine, which is not recognized by all printers.
To correct this issue, the bursting engine sets the content type to application/octet-stream for print jobs.
This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Oracle BI Publisher's PDF mapping tool that maps data fields to form fields in a PDF template currently does not support Adobe Acrobat Reader 8.0. You must use Acrobat Reader 7.0 (or Acrobat Reader 6.0 if English is the only language required for your site).
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
If you are using an LDAP security model, then the privileges of member groups might not be properly inherited from the parent groups. For example, suppose you have an Oracle Internet Directory (OID) group named XMLP_Development and this group is a member of another group called XMLP_Admin. Users who are members of the group XMLP_Development might not inherit the privileges assigned to XMLP_Admin as expected.
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
If the administrator changes the name of the Oracle BI Publisher "Guest" folder and restarts the server for this change to take effect, then users are prompted to enter credentials the next time that they try to access this folder. To work around this issue, do not change the name of the Guest folder.
This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1 and 10.1.3.4.2.
If your environment is SSO-enabled and you use Microsoft Internet Explorer 6.0 as the browser and you use Oracle Application Server Web Cache, then you might encounter Javascript errors when trying to access the Oracle BI Publisher Report editing panel. To work around this issue, disable "cache compress js" in Oracle AS Web Cache.
This issue applies to Version 10.1.3.3. It is fixed in Version 10.1.3.3.1.
The system parameter CURRENT_SERVER_URL, which you can include in RTF layout templates, does not return a value.
This issue applies to Versions 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1 and 10.1.3.4.2.
When the OC4J that is running Oracle BI Publisher is started in an Arabic locale, the Oracle Business Intelligence Presentation Catalog does not display.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1 and 10.1.3.4.2.
Reports that use the BI Publisher data template as the data model might fail with the following error: "Data not defined."
This error occurs if you defined a parameter in the data template but you do not pass a value to it through the user interface. For example, if the data template includes a parameter such as the "P1" parameter that is shown in the following code sample:
<data Template name="prodTemplate" dataSourceRef="demo-hr">
<parameters>
<parameter name="P1" dataType="character"
defaultValue="Hello"/>
</paramters>
<dataQuery>
<sqlStatement name="prodStmt">
<![CDATA[
select last_name, first_name, salary from employees where
salary > 4000]]
</sqlStatement>
</dataQuery>
</dataTemplate>
and you do not specify this parameter in the "Parameters" section of the report definition that you created using the BI Publisher Edit Report interface, then you receive the error.
This was not an issue in 10.1.3.2, but reports constructed this way produce the error in 10.1.3.3.
To work around this issue, either define the parameter in the Edit Report interface or remove the parameter from the data template.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The Oracle BI Publisher Query Builder includes an option to "Check All" when selecting columns from a table. If the table contains more than 20 columns, then only the first 20 columns are selected.
To work around this issue, you must manually select all columns.
This issue applies to Versions 10.1.3.3 and 10.1.3.3.1, 10.1.3.3.2, and 10.1.3.3.3; this issue is fixed in 10.1.3.4.
When creating a query for a list of values, you can choose the "Default Data Source" option or select a specific data source. If you select the "Default Data Source" option and run the report, then the system might either display the "Processing" indicator and never return any data, or the system might fail to run and return the following error:
Parameter name: <parameter> Can not establish database connection (null)
To work around this issue, select a specific data source when creating a query for an LOV.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When you delete a user, the user directory under the Reports tab/repository (Home>Users) is not deleted and cannot be deleted through the user interface.
To work around this issue, you must manually delete the user folder from the repository. Complete the following steps to delete the folder from the repository:
If you use a file-based repository, then log in to the computer where Oracle BI Publisher is installed.
Locate the user folder under the %BIPublisher_Repository%/Users directory. Each user folder starts with a tilda character, for example: ~User1.
Manually remove the deleted user's folder.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you create and schedule a report using a Discoverer worksheet as a data source and the report includes parameter names that contain multibyte characters, then the report history does not correctly display the parameter names with the multibyte characters. The parameter names display garbled.
This issue applies to Version 10.1.3.3.1. It is fixed in Version 10.1.3.3.2.
If you attempt to access the Oracle BI Publisher Web service WSDL on the Oracle 10g platform (10.1.3.0.0), for example:
http://localhost:9704/xmlpserver/services/PublicReportService?wsdl
then you encounter the following error:
AXIS error
Sorry, something seems to have gone wrong... here are the
details:
Fault - ; nested exception is:
oracle.xml.parser.v2.XMLDOMException Implementation does not
support the object requested.
To get the WSDL for Oracle BI Publisher 10.1.3.3.1 PublicReportServices, see the Oracle Business Intelligence New Features Guide for Version 10.1.3.4.1.
Starting with Version 10.1.3.3.2, this problem is fixed and you can access and display the WSDL correctly.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Oracle BI Publisher's Web Service API definition includes the complex type "ScheduleRequest." In Version 10.1.3.3.2, several elements defined under ScheduleRequest have been changed from type "string" to type "boolean."
Any applications built against Oracle BI Publisher Web Services Version 10.1.3.3.1 that use ScheduleRequest must be modified for this change.
The changed elements are:
notifyWhenFailed
notifyWhenSuccess
notifyWhenWarning
saveDataOption
saveOutputOption
scheduleBurstringOption
schedulePublicOption
useUTF8Option
The updated definition for Version 10.1.3.3.2 is as follows:
<complexType name="ScheduleRequest">
<sequence>
<element name="deliveryRequest" nillable="true"
type="impl:DeliveryRequest"/>
<element name="endDate" nillable="true" type="xsd:dateTime"
/>
<element name="jobCalendar" nillable="true" type="xsd:string"
/>
<element name="jobLocale" nillable="true" type="xsd:string"
/>
<element name="jobTZ" nillable="true" type="xsd:string" />
<element name="notificationTo" nillable="true">
type="xsd:string" /
<element name="notifyWhenFailed" type="xsd:boolean" />
<element name="notifyWhenSuccess" type="xsd:boolean" />
<element name="notifyWhenWarning" type="xsd:boolean" />
<element name="repeatCount" type="xsd:int" />
<element name="repeatInterval" type="xsd:int" />
<element name="reportRequest" nillable="true"
type="impl:ReportRequest" />
<element name="saveDataOption" type="xsd:boolean" />
<element name="saveOutputOption" type="xsd:boolean" />
<element name="scheduleBurstringOption" type="xsd:boolean" />
<element name="schedulePublicOption" type="xsd:boolean" />
<element name="startDate" nillable="true" type="xsd:dateTime"
/>
<element name="useUTF8Option" type="xsd:boolean" />
<element name="userJobName" nillable="true" type="xsd:string"
/>
</sequence>
</complexType>
The new definition is correctly documented in the Oracle Business Intelligence New Features Guide for Version 10.1.3.4.1.
This issue applies to Version 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
In Version 10.1.3.3.1, PublicReportService Web service API validateLogin throws the exception "SOAPFault thrown" when the user's credential validation fails. In Version 10.1.3.3.2 when a user's credential validation fails, validateLogin returns false in the validateLoginResponse.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Oracle BI Publisher's Web service API definition includes the complex type "ParamNameValue." In Version 10.1.3.3.1, "isMultiValuesAllowed" and "multiValuesAllowed" were redundant. In Version 10.1.3.3.2 and later, "multiValuesAllowed" is removed. The new definition of the ParamNameValue complexType is as follows:
ParamNameValue
<complexType name="ParamNameValue">
<sequence>
<element name="isMultiValuesAllowed" type="xsd:boolean" />
<element name="name" nillable="true" type="xsd:string" />
<element name="values" nillable="true"
type="impl:ArrayOf_xsd_string"/>
</sequence>
</complexType>
Any applications built against Oracle BI Publisher Web Services Version 10.1.3.3.1 that use "ParamNameValue" must be modified for this change.
The new definition is correctly documented in the Oracle Business Intelligence New Features Guide for Version 10.1.3.4.1.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4.1, and 10.1.3.4.2.
When you choose an analyzer template with interactive output format and click "Link to this report" and then choose the "Document Only" option, if you copy the URL into a new browser window to request the report by this URL, you will encounter a 500 internal error.
This issue has no workaround.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The instanceconfig.xml file that is created by the installer does not use fully qualified host names for Oracle BI Publisher. As a result, users on different domains cannot view Oracle BI Publisher reports that are embedded in dashboards. For example, if there is a dashboard on machine1.a.domain.com that users on machine2.b.domain.com want to view, this issue would not allow Oracle BI Publisher reports to be displayed.
To work around this issue, you must manually update the instanceconfig.xml file to use a fully qualified host name.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you click the Dashboards link from the Oracle BI Publisher application to navigate to the Business Intelligence Dashboards page, then you are prompted to log in again before you can access the Dashboards page.
This issue has no workaround.
This issue applies to Versions 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Microsoft applications, including Excel, have a file name length limit. The limit differs by versions and OS combinations. For Excel to open a file, the total length of the full path and file name including extension cannot exceed the limit (usually 200 - 256 characters). If your file name exceeds this limit and you try to launch the Excel Analyzer, then you receive the following error:
"Unable to find file <filename>.xls, please check file name spelling, and make sure file location is correct."
This error is most likely to occur when the file name contains multibyte characters.
To work around this issue, rename the report with a shorter name and refrain from using multibyte characters in the file name.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The text for this item has been removed. For more information about this new feature, see the Oracle Business Intelligence New Features Guide Version 10.1.3.4.1.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
The text for this item has been removed. For more information about this new feature, see the Oracle Business Intelligence New Features Guide Version 10.1.3.4.1.
This issue applies to Versions 10.1.3.3, 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1 and 10.1.3.4.2.
A configuration problem can occur between Oracle BI Publisher and Oracle BI Server. When this problem occurs, users are unable to log in to Oracle BI Publisher or are unable to run or create Oracle BI Publisher reports based on Oracle BI Answers requests.
When Oracle BI Publisher is installed as part of Oracle BI Enterprise Edition Plus, the Oracle BI Publisher's security model is set to Oracle BI Server and the Administrator password is set to the default Oracle BI repository file's (RPD) default password.
This configuration ensures that Oracle BI Publisher is automatically configured with the Oracle BI Server security and that users can connect to Oracle BI Publisher using their Oracle BI user names and passwords. Everything functions correctly if the user installs and uses the default repository (RPD) file that is provided or continues to use the default Oracle BI Server Administrator password.
However, if you use another RPD or change the default Administrator password, problems can occur when connecting and logging in to Oracle BI Publisher. In addition, any RPD file except the provided default likely does not include the Oracle BI Publisher roles.
Use the following procedure if you cannot access Oracle BI Publisher. This procedure resolves most Oracle BI Publisher and Oracle BI Server configuration problems. After you complete this procedure, you can log in to Oracle BI Publisher with Oracle BI Server accounts that have been enabled for access to Oracle BI Publisher as described in the 10.1.3.2 Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
Open the xmlp-server-config.xml file. This file is located in ...\xmlp\XMLP\Admin\Configuration\xmlp-server-config.xml.
Edit the Oracle BI Publisher configuration file by setting the Security Model property to XDO.
<property name="SECURITY_MODEL" value="XDO"/>
Re-start the Oracle BI Publisher server or if Oracle BI Publisher is running in an J2EE application server, restart the J2EE application server (for example, stop/start OC4J) to apply the changes that you made to the configuration file.
Log in to Oracle BI Publisher by using login: Administrator and password: Administrator.
Go to the Oracle BI Publisher Admin tab on the Security Configuration window to enable a local superuser by specifying a user name other than Administrator (for example, Admin or Root) and set the password.
Note:
This account enables you to log in to Oracle BI Publisher regardless of the status of the security model with which Oracle BI Publisher is configured.
If you want to continue using Oracle BI Server as the security model for Oracle BI Publisher, then select it and update the following items:
Reset the Security Model to Oracle BI Server.
Reset the Connection String to the JDBC connection to the Oracle BI Server (for example, jdbc:oraclebi://hostname:9703/).
Set the Administrator Username as needed.
Set the Administraor Password as needed.
Go to the Oracle BI Presentation Services Integration page and change the Administrator Password to the password that is used for the Oracle BI Server Administrator.
Note:
Anytime that you change the Oracle BI Server Administrator password, you must log in to Oracle BI Publisher as the Oracle BI Publisher local superuser (see Step 5 of this procedure) and re-set the Oracle BI Server Administrator password in the Security Configuration window and the Oracle BI Presentation Services Integration window.
In the Oracle BI Presentation Services Integration page, go to Data Sources > JDBC Connection and for Oracle Business Intelligence EE, reset the Oracle BI Server Administrator password.
The installer uses the computer name in some configuration files and, depending on the network environment, it sometimes causes issues with autologin to Oracle Business Intelligence Publisher. To fix this issue, browse to and open the Oracle BI Server configuration file, which is located in ...\bidata\web\config\instanceconfig.xml
Locate the AdvancedReporting section of the document, and modify the three URL elements to use fully qualified host names. For example:
<ServerURL>http://server:9704/xmlpserver/services/XMLPService </ServerURL>
<WebURL>http://server:9704/xmlpserver</WebURL>
<AdminURL>http://server:9704/xmlpserver/servlet/admin
</AdminURL>
to
<ServerURL>http://server.company.com:9704/xmlpserver/
services/XMLPService</ServerURL>
<WebURL>http://server.company.com:9704/xmlpserver</WebURL>
<AdminURL>http://server.company.com:9704/xmlpserver/servlet/
admin</AdminURL>
If you are using an RPD other than the default RPD or an RPD based on the 10.1.3.3.1 default RPD, then you must run cryptotools to add the Oracle BI Publisher credentials to the Oracle BI Presentation Services Credential Store in the RPD file. For information about how to perform this task, see Chapter 11 of the 10.1.3.2 Oracle Business Intelligence Infrastructure Installation and Configuration Guide.
Restart the Oracle BI Publisher and Oracle BI Presentation Services to apply your changes.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Note:
This issue has been fixed in Smart Space, Fusion Edition 11.1.1.1.
To enable BI Publisher to work with Oracle Smart Space, Fusion Edition (Release 11.1.1), you must force the BI Publisher Web service to appear as RPC-encoded. The solution for this issue is to set the JVM parameter described below.
Important:
Setting this parameter causes the Oracle BI Add-in for Microsoft Office to fail. You therefore cannot integrate BI Publisher with Smart Space if you also want to use the add-in.
To enable BI Publisher to integrate with Smart Space, modify the Java command that starts your J2EE application server that runs BI Publisher to include the following parameter:
-Daxis.ServerConfigFile=server-rpc-config.wsdd
For example, if you are using the default oc4j.cmd, then change this line:
set JVMARGS=-Djava.library.path=C:\oracle\bise1\bi\server\Bin;C:\oracle\bise1\bi\web\bin -DSAROOTDIR=C:\oracle\bise1\bi -DSADATADIR=C:\oracle\bise1\bidata -XX:MaxPermSize=128m -Xmx512m %OC4J_JVM_ARGS%
to this:
set JVMARGS=-Djava.library.path=C:\oracle\bise1\bi\server\Bin;C:\oracle\bise1\bi\web\bin -DSAROOTDIR=C:\oracle\bise1\bi -DSADATADIR=C:\oracle\bise1\bidata -Daxis.ServerConfigFile=server-rpc-config.wsdd -XX:MaxPermSize=128m -Xmx512m %OC4J_JVM_ARGS%
If you are not integrating BI Publisher with Oracle Smart Space, then this command is unnecessary.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
An MHTML reader is currently not available for Mac OS X. If your client is running Mac OS X and you choose the MHTML output format for a report, then you see an error message. This issue has no workaround.
This issue applies to Versions 10.1.3.3.2 and 10.1.3.3.3; it is fixed in 10.1.3.4.
When viewing the Oracle BI Publisher locale selection list, "Croatian" might be listed as "Croatian" rather than the appropriate translation for the currently selected locale.
In the Oracle Business Intelligence Publisher Report Designer's Guide (for release 10.1.3.4) and the Oracle Business Intelligence Publisher User's Guide (for releases before 10.1.3.4), the Parameter Mapping table under the topic "Enabling Bursting" incorrectly lists the parameters for the Printer channel.
The correct parameter values are shown in Table 3-1 alongside the incorrect listings currently shown in the documentation.
This issue applies to Versions 10.1.3.4.1 and 10.1.3.4.2.
Users of Fusion Intelligence receive the following error when attempting to launch BI Publisher from Oracle Business Intelligence:
"Oracle BI Publisher Enterprise. Error processing your BI Publisher request. Please contact your administrator to review the log files. Error Details Error Codes: S8VLP8HS"
The Fusion Intelligence authentication method does not work with BI Publisher and users cannot navigate to BI Publisher from the More Products menu when using Fusion Intelligence.
There is no workaround for this issue.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
In the Oracle Business Intelligence Publisher Report Designer's Guide, chapter "Extended Function Support in RTF Templates," under the topic "Extended SQL and XSL Functions," the syntax for the division function is incorrectly given as:
<?xdofx:2/3?>
the correct syntax is:
<?xdofx:2 div 3?>
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2
In the Oracle Business Intelligence Publisher Report Designer's Guide, under the topic "Scheduling a Report" the description for the Run Monthly option states that you can select multiple days of the month to run a report, as follows: "To select multiple days of the month to run the report, enter each day separated by a comma (example: 1,15,28)."
This description is incorrect. The field for entering the day of the month does not support multiple days. You can only enter one day of the month with this option.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2
BI Publisher uses the internationalization (I18N) library that is packaged with Oracle 9i Database. If you are using BI Publisher with Oracle Database10g or later, then formatting of date and time values for certain locales returned by the Oracle Database do not match those returned by BI Publisher.
There is no workaround for this issue.
This issue applies to Version 10.1.3.4.1 and 10.1.3.4.2.
Before Version 10.1.3.4.1, the data type of a parameter passed by a BI Publisher Data Template was not validated. Parameter values were passed as string objects regardless of the data types defined for the parameters in the data template. Therefore, parameters could be passed from the data template to a function or to a report that defined the parameter data type differently, without encountering an error.
In 10.1.3.4.1 data type validation has been implemented. Now if the parameter data type passed by the data template does not match the parameter data type defined in the function or report, an error is thrown.
Note that you might encounter errors for reports that previously ran successfully. To avoid errors, ensure that a parameter data type defined in a data template matches the data type defined in the function or report to which it is passed.
This issue applies to Version 10.1.3.4.1 and 10.1.3.4.2.
In release 10.1.3.4.1, BI Publisher introduced certification for Microsoft SQL Server 2008. However, the BI Publisher Add Data Source page does not include Microsoft SQL Server 2008 as an option in the list of Driver Types.
To add a JDBC connection to a Microsoft SQL Server 2008 data source, choose Microsoft SQL Server 2005 as the Driver Type, and enter the remaining information to connect to your database.
This issue applies to Version 10.1.3.4.1 and 10.1.3.4.2.
In release 10.1.3.4.1, BI Publisher introduced certification for Microsoft SQL Server 2008. However, the BI Publisher Scheduler Configuration page does not include Microsoft SQL Server 2008 as an option in the list of supported Database Types.
To use Microsoft SQL Server 2008 as your scheduler database, choose Microsoft SQL Server 2005 as the Database Type, and enter the remaining information to connect to your database.
This issue applies to Versions 10.1.3.4.1 and 10.1.3.4.2.
In release 10.1.3.4.1, BI Publisher introduced certification for Netezza 4.5. However, the BI Publisher Add Data Source page does not include Netezza 4.5 as an option in the list of Driver Types.
To add a JDBC connection to a Netezza 4.5 data source, choose Netezza 4.0 as the Driver Type, and enter the remaining information to connect to your database.
This issue applies to Version 10.1.3.4.1; this issue is fixed in 10.1.3.4.2
The 10.1.3.4.1 BI EE installer fails to install a file (ssodefaults.xml) required to fully use the BI Publisher Single Sign-On options from the BI Publisher Admin interface.
To work around this issue, manually copy ssodefaults.xml from the installation media to your existing BI Publisher repository.
The file ssodefaults.xml is located in the Server_Ancillary directory of the installation media as follows:
\Server_Ancillary\Oracle_Business_Intelligence_Publisher\XMLP\Admin\Security\ssodefaults.xml
Copy it to your existing BI Publisher repository,for example:
C:\oracle\bi\xmlp\XMLP\Admin\Security
This update does not require a restart of the application to take effect.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
In the Oracle Business Intelligence Enterprise Edition Deployment Guide, under the topic: "Configuring BI Presentation Services and BI Publisher When SSL Is Enabled," the connection string example given for BI Publisher is incorrect. On page 121, the connection string format is shown as follows:
jdbc:oraclebi://<BI Server>:9703;ssl=true;sslKeystorefilename=<path and filename of keystore>;sslKeystorepassword=<password of keystore and key>;trustanyserver=true;
The BI Server port must be followed by a slash "/" not a semicolon ";" as shown in the documentation.
The proper format is as follows:
jdbc:oraclebi://<BI Server>:9703;ssl=true/sslKeystorefilename=<path and filename of keystore>;sslKeystorepassword=<password of keystore and key>;trustanyserver=true;
This issue applies to Versions 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
When configuring the trusted user to integrate Discoverer with BI Publisher, the username must contain only single-byte, ASCII characters. BI Publisher cannot access Discoverer connections created with a username that contains multibyte characters.
This issue applies to Versions 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
For data models based on Discoverer worksheets, BI Publisher references the Discoverer workbook and worksheet by name. If the workbook or worksheet name is changed in Discoverer, the BI Publisher report cannot run until you update the BI Publisher report's data model to point to the newly named Discoverer workbook or worksheet.
This issue applies to Versions 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
Parameters defined for BI Publisher reports allow for users to enter values directly if the parameter is not associated with a list of values (LOV). When a BI Publisher parameter is associated with an LOV, a user can only select values from the list. In Discoverer, parameter values can be either entered directly or selected from an LOV through a control called a combo-box. BI Publisher does not provide a combo-box. For BI Publisher reports based on Discoverer worksheets that have parameters associated with an LOV, users can select parameter values only from the LOV. Users cannot enter values for these parameters directly.
This issue applies to Version 10.1.3.4.1 and 10.1.3.4.2.
The privileges assigned to the BI Publisher Superuser account are limited to tasks on the Admin page. The intention of the Superuser is to allow access to the system in the event of a failed or misconfigured external security model.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1 and 10.1.3.4.2.
The RTF template feature that enables you to specify the ending page of the report (odd or even) is supported only for PDF output. This limitation is not noted in the Oracle Business Intelligence Publisher Report Designer's Guide chapter "Creating an RTF Template."
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If the XML data file is larger than 5MB, then do not use the Analyzer for Excel in native mode. Instead, use the Client Access Disabled mode. This mode is set as a report property. For information about enabling this mode, see the topic "Using the Report Editor" in the Oracle Business Intelligence Publisher Report Designer's Guide.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
If you are deploying BI Publisher to WebLogic Server 10.3, then you must include the following additional setting to the startup script (startWebLogic.sh) for the domain that contains the BI Publisher server:
-Dtoplink.xml.platform=oracle.toplink.platform.xml.jaxp.JAXPPlatform
This setting is required to enable BI Publisher to find the TopLink JAR files to create the Scheduler tables.
This issue applies to Versions 10.1.3.4, 10.1.3.4.1, 10.1.3.4.2 and to IBM WebSphere 6.1 deployments only.
When trying to log in to BI Publisher, if you encounter an "HTTP 500 Internal Server Error" with the exception:
SystemErr.log: java.lang.VerifyError: class loading constraint violated (class: oracle/xml/parser/v2/XMLNode method: xdkSetQxName(Loracle/xml/util/QxName;)V) at pc: 0
then you might need to modify the WebSphere class loader configuration properties.
Perform the following steps to ensure the correct configuration:
Log in to the WebSphere administrative console. From the Applications menu, select Enterprise Applications.
Select the "xmlpserver" application name from the list.
Choose "Class loading and update detection".
Under Class Loader > General Properties, set the following properties as shown:
| Property | Setting |
|---|---|
|
Polling interval for updated files |
0 seconds |
|
Class loader order |
Classes loaded with application class loader first |
|
WAR class loader policy |
Single class loader for application |
Apply this change and save the new configuration.
Restart the xmlpserver application.
Refer to the IBM WebSphere 6.1 documentation for more details: http://publib.boulder.ibm.com/infocenter/wasinfo/v6r1/index.jsp?topic=/com.ibm.websphere.base.doc/info/aes/ae/trun_classload_entapp.html .
This issue applies to all 10g releases that support PowerPoint output.
When you select PowerPoint output in BI Publisher the formatting engine generates an MHTML file that can be opened in Microsoft PowerPoint. This is supported in Microsoft PowerPoint 2003 and 2007. Microsoft Office PowerPoint 2010 no longer supports the MHTML format. Attempting to open the PowerPoint output from BI Publisher in PowerPoint 2010 causes an error.To work around this issue, open the BI Publisher report in PowerPoint 2003 or 2007. The report can then be saved as PPTX, if desired.
Note that in Release 11g BI Publisher supports both MHTML PowerPoint output and PPTX output.
This issue applies to Versions 10.1.3.3.2, 10.1.3.3.3, 10.1.3.4, 10.1.3.4.1, and 10.1.3.4.2.
BI Publisher does not support sharing the same database schema with different BI Publisher instances, except in a cluster environment. In this case, you can share the same database schema with multiple cluster nodes that share the same BI Publisher repository. To enable this configuration, you must check the cluster checkbox in Scheduler configuration page. If each cluster node runs on a different server, then you must synchronize the system clocks of the servers. For more information, see the white paper "Oracle BI Publisher Enterprise Cluster Deployment," available on Oracle Technology Network.
This issue applies to all versions of BI Publisher.
When designing an RTF template, the formatting achieved using a soft return in Microsoft Word is not supported by BI Publisher. Soft returns in the RTF template might cause unexpected results in the output. To work around this issue, always use hard carriage returns in a template.
This issue applies to all 10g versions of BI Publisher. The workaround is available as of Version 10.1.3.4.2.
The calendar date picker that enables you to select a date parameter value in the report viewer and the scheduler does not display the correct first day of the week for some locales. For example, a user with French as the selected locale will see Dimanche (DIM) as the first day of the week rather than Lunedi (LUN).
To resolve this issue, the new property AUTO_FIRST_DAY_OF_WEEK is supported in the 10.1.3.4.2 release. Set this property in the xmlp-server-config-file as follows:
Navigate to the xmlp-server-config file. The config file is located:
<BIP repository location>/Admin/Configuration/xmlp-server-config.xml
Set the AUTO_FIRST_DAY_OF_WEEK property to "true" as follows:
<xmlpConfig xmlns="http://xmlns.oracle.com/oxp/xmlp"> ... <property name="AUTO_FIRST_DAY_OF_WEEK" value="true"/> ... </xmlpConfig>
Restart the BI Publisher server.
This issue applies to all versions of release 10g.
Some characters might appear garbled in chart titles for HTML, RTF, Excel, and PowerPoint format output. These characters might be multibyte characters or Arabic, Hebrew, or Thai characters.
To work around this issue, install the corresponding language pack. To install a language pack on Windows OS:
Go to the Control Panel and select Regional and Language Options.
Click the Languages tab.
To support multibyte characters (for example, Simplified Chinese, Korean, or Japanese) enable "Install files for East Asian languages." To support Arabic, Hebrew, or Thai characters, enable "Install files for complex script and right-to-left languages (including Thai)."
This issue applies to all versions of release 10g.
The BI Publisher bursting engine processing logic does not support the use of attributes in the XML data. To work around this issue, do not use attributes in XML data intended as input to the bursting engine.
Two new features in release 10.1.3.4.2 are not documented in the Oracle Business Intelligence Publisher New Features Guide Release 10.1.3.4.2. These features are:
Use the following Web service APIs to check scheduled job information.
JobInfo[] getScheduledReportInfo(String scheduledJobID, String username, String password)
JobInfo.getStatus() returns the same job status reported in the Report Schedules page of the BI Publisher user interface. There are three possible statuses:
"Scheduled" - The job has not executed.
"Done" - The job does not execute any reports. These jobs are deleted from the Report Schedules table in the BI Publisher user interface.
"Suspended" - The job is suspended from report executions.
JobStatus getScheduledReportStatus(String scheduledJobID, String username, String password)
JobStatus.getJobStatus() returns the status of the last report job. There are four possible statuses:
"Running" - The last report job is still running and has not yet completed.
"Completed" - The last report job has completed.
"Error" - The last report job finished with an error.
"Unknown" - The job has not executed any report jobs yet.
JobHistoryInfo[] getScheduledReportHistoryInfo(String scheduledJobID,String username, String password, String viewByFilter, boolean DownloadReport)
JobHistoryInfo.getStatus() returns the status of any report job instance that has been executed by the job. JobStatus.getJobStatus() API (listed above) only returns the status of the last report job. The possible statuses are:
"Running" - The last report job is still running and has not yet completed.
"Completed" - The last report job has completed.
"Error" - The last report job finished with an error.
Use the following new settings to improve performance and scalability of user authentications during user logins and Web service authentication against the BI Server.
Enable User Role Cache - Default is not enabled
User Role Cache Refresh Interval - Default value is 1
User Role Cache Refresh Interval Unit - Default value is Hour
When User Role Cache is enabled, user roles are saved into memory after the first login after refresh. Roles saved in memory are then used from the second login onwards by the same user. This reduces the load off of the BI Server to fetch all user roles, especially when it is configured to use an external security such as LDAP or database.
The new settings are available when you select the Oracle BI Server security model from the Admin Security Configuration page.
To set the report runtime property "Disable External References" to "False", you must explicitly set the report property to "False." If you set the property to null at the report level and set the server-level property to "False", while expecting the report to inherit the server setting, BI Publisher still treats the setting as "True" (which is the default).
To work around this issue, do not set the report-level property to null; ensure that you set the report-level setting to"False".
|
 Copyright © 2009, 2012, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
