Part No. E10410-09
This document contains the following topics:
These release notes describe known issues and workarounds for Oracle Business Intelligence Publisher releases 10.1.3.3, 10.1.3.3.1, 10.1.3.3.2, and 10.1.3.3.3. For installation information, consult the Oracle Business Intelligence Publisher Installation Guide, which is available on the Oracle Business Intelligence Publisher install media and on the Oracle Business Intelligence Publisher Web site:
These release notes are organized into the following sections:
These release notes are updated periodically as new information becomes available. To ensure that you are reading the latest version of the release notes, check the Oracle Business Intelligence Publisher Web site:
After extended use, the BI Publisher Web UI may 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 may not be able to see
Welcome, <username> Preferences Sign Out Help
To correct this problem, restart the browser.
The Java SE Development Kit (JDK) 5.0 version 1_5_0_7 contains a bug that impacts the performance of BI Publisher.
To correct this problem, upgrade to JDK 5.0 update 11 (1_5_0_11). You can download this update from:
Starting with version 10.1.3.2.1 if the administrator has not correctly configured the BI Publisher scheduler, the Schedules tab and the Schedule buttons will be 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. See the topic: Configuring the Scheduler Database in the Oracle Business Intelligence Publisher Installation Guide.
When performing an advanced install into an existing ORACLE_HOME a runtime error will occur if a space character is in the directory name of the selected ORACLE_HOME. This is a limitation of the Oracle Universal Installer (OUI) version 10.1.0.6.0 used for BI Publisher 10.1.3.3. The directory name is not validated before installation, thereby allowing installation to proceed. However, the runtime error will be encountered, which will require you to cancel the installation.
To work around this issue, choose an ORACLE_HOME directory name that does not include a space character.
If you encounter either of the following errors when using Discoverer Worksheets in your report data model:
500 Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
or Error 501
It is possible that the HTTP server where BI Publisher is running is timing out before the Discoverer Web service returns the data from the worksheet. If that is the case, you can correct this problem by increasing the values of Timeout and KeepAliveTimeout in the file:
For example you can change the following values:
Timeout 1800 KeepAliveTimeout 15
Timeout 7200 KeepAliveTimeout 150
Note the values are in seconds (1800=30 minutes, 7200=2 hours).
If you are running the BI Publisher server on a Linux or Unix machine that does not have an X Server installed reports that contain images may not be properly generated.
Workaround: If you are running Java 1.4.2 or later, start the environment with a headless implementation. Specify the following property at the java command line:
For JDK versions prior to 1.4.2 please see your documentation on how to implement X Host for your environment.
If your report file name contains multibyte characters and you download the report by selecting the Report Actions icon then clicking Download this report, the file names in the generated zip file will be invalid. This is due to a Java bug (details available from the Sun Developer Network). Consequently, the downloaded report zip file cannot be uploaded back to the BI Publisher server. To work around this issue, use only ASCII characters in file names.
Because the encoding of multibyte character file names is dependent on the operating system and locale of the runtime environment, BI Publisher cannot support multibyte characters in file names. To work around this issue, use only ASCII characters in file names.
Oracle BI Publisher does not support column-level time zone settings applied in BI Presentation Services. BI Publisher reports that use BI Answers requests with column-level time zone settings may result in different dates displayed in BI Presentation Services and BI Publisher. This is not an issue for reports without column-level time zone settings as long as the User Time Zone setting for BI Publisher and BI Presentation Services is the same.
If you wish to use external Web Services or HTTP data sources and your 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.
For OC4J, update the <Oracle_Home>\oc4j\bin\oc4j.cmd file. Locate the following line:
rem JVMARGS 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%
and update with the following string:
so the result will be:
rem JVMARGS 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 other application servers, consult your documentation.
If you create an Analyzer template with multibyte characters in the template name and run the report by selecting the View link or button, you will 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, the report will be rendered correctly.
To work around this issue, use only ASCII characters in template names, or turn off the auto-run option for the report.
If SSO is enabled, the Report Editor panel may fail to display correctly if you are also using Internet Explorer 6.0 as your Web browser. To work around this issue, use either Internet Explorer 7.0 or Firefox 2.0.
If you integrate Oracle BI Publisher Enterprise with the E-Business Suite, you may not be able to see the Admin tab after logging in to BI Publisher with an E-Business Suite user who has the appropriate 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 environment 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 environment variable for your Linux OS as "en_US.UTF-8". For more information on setting this variable, see the following notes on Oracle MetaLink:
Note: 264157.1: The Correct NLS_LANG Setting in Unix Environments
Note: 351919.1: Globalization Support : JavaVM, Oracle JDBC Driver, NLS_LANG and OC4J
If you create a report using a Discoverer worksheet as a data source and the report includes parameter names that contain multibyte characters, then when you schedule that report, the report history does not correctly display the parameter names with the multibyte characters.
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.
There is no workaround for this issue.
To install the BI Publisher scheduler schema in Microsoft SQL 2005 server when BI Publisher is hosted on an OC4J container, you must remove the TopLink JAR files located in the <OC4J_Home>\toplink\jlib\* folder. These jar files conflict with the JDBC driver JAR file sqljdbc.jar placed in the WEB-INF/lib folder of BI Publisher Enterprise Server.
If you attempt to access the BI Publisher Web service WSDL on the Oracle 10g platform (10.1.3.0.0), for example:
you will encounter the following exception:
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.
If you are unable to access the WSDL for BI Publisher PublicReportService Web service via the URL, refer to the Oracle Business Intelligence New Features Guide, which includes the WSDL in its entirety.
When viewing the BI Publisher locale selection list, "Croatian" may be listed as "Croatian" rather than the appropriate translation for your currently selected locale.
This issue applies to versions 10.1.3.3.2 and 10.1.3.3.3.
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.
It is strongly recommended that you enable HTTPS on the middle tier hosting the Web services as the trusted username/password that is passed can be intercepted. This also pertains to Web services that are used for communication between BI Publisher and Oracle BI Presentation Services and between Oracle BI Publisher and Oracle BI Discoverer.
If you receive errors when making calls to a Web service that is protected via Secure Sockets Layer (SSL) (that is, uses https://), you may need to export the certificate from the Web server hosting the Web service and import it into the java keystore on the machine running BI Publisher. An example error might be: "SSL received a record that exceeded the maximum permissible length.”
This step should not be required if the server certificate is linked to some certificate authority (such as Verisign) -- the default java keystore can handle that. But if the Web service server is using some self-generated certificate (for example, in a testing environment), then it is required.
If your system is SSO-enabled, you must modify your mod_osso.conf file to disable SSO to allow Web service communication between 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 BI Publisher with Oracle Single Sign-On, see the topic: "Setting Up Oracle Single Sign-On" in the Oracle Business Intelligence Publisher User's Guide.
If you are using Microsoft Internet Explorer 6 or 7 over SSL (that is, https://) you will not be able to open PDF or other binary documents. This is an Internet Explorer issue that results when the header "Cache-Control: No Cache" is present in an HTTP response. For more information see the following Microsoft documents:
Internet Explorer file downloads over SSL do not work with the cache control headers
Prevent caching when you download active documents over SSL
For Oracle Application Server deployments, you can work around this issue by modifying the mod_osso.conf file as follows:
Locate the following entry:
<Location /xmlpserver> require valid-user AuthType Basic </Location>
Modify this entry as follows:
<Location /xmlpserver> require valid-user AuthType Basic OssoSendCacheHeaders off Header unset Pragma Header unset Cache-Control Header unset Vary </Location>
For non-Oracle Application Server deployments, please see the Microsoft documents noted above for possible resolutions that can be implemented in your environment as well as your application server documentation for information on turning off the "Pragma" and "Cache-Control" HTTP header properties.
If you have configured BI Publisher to use an LDAP server, users with multibyte characters in their user name will not be able to see the Admin tab, even when granted the Administration Role. To work around this issue, create a user name with ASCII characters for users needing the Administration role.
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. To delete the folder from the repository: If using a file-based repository, log on to the machine where 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.
If you click the Dashboards link from the BI Publisher application to navigate to the Business Intelligence Dashboards page, you will be prompted to log in again before you can access the Dashboards page.
This issue has no workaround.
If you are using a clustered environment, and you have a CUPS server implemented as a delivery option with no other printers defined, you may not see your 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.
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.
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.
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 caused by 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'?>
<?(round((13683.80 + 516.39)*100) div 100)?>
When you design a PDF template with repeatable fields, the output in portrait mode 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.
BI Publisher's PDF mapping tool used to map 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).
If you are working in multiple languages, to show and input the text on the Template Builder dialogs correctly, you must set your operating system regional settings for the target language. To set the Regional and Language Options:
From the 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 your system regional settings.
If you wish to use both the BI Publisher Analyzer for Excel and the new BI Office Add-in (available with the Oracle Business Intelligence Enterprise Edition), you must install the BI Publisher Analyzer for Excel first. If you install the BI Office Add-in first, you must uninstall it before you can install the BI Publisher for Analyzer for Excel, then reinstall the BI Office Add-in.
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 you will receive the error:
"Unable to find file <filename>.xls, please check file name spelling, and make sure file location is correct."
This is most likely to occur when your file name contains multibyte characters.
To work around this issue, rename your report with a shorter name and do not use multibyte characters in the file name.
Flash templates require Adobe Flash Player 9. Currently the Flash Player 9 is not available for FireFox on Solaris. Until Flash Player 9 is released for this platform, Flash templates cannot be viewed on Solaris. This issue has no workaround.
Reports based that use the BI Publisher data template as the data model may fail with the following error:
Data not defined
This will occur if you define a parameter in your data template that you do not pass a value to via the user interface. For example, if you define a data template with a parameter ("P1" in the example) similar to the following:
<dataTemplate name="prodTemplate" dataSourceRef="demo-hr"> <parameters> <parameter name="P1" dataType="character" defaultValue="Hello"/> </parameters> <dataQuery> <sqlStatement name="prodStmt"> <![CDATA[ select last_name, first_name, salary from employees where salary > 4000 ]]> </sqlStatement> </dataQuery> </dataTemplate>
But you do not define this parameter in BI Publisher's Edit report page, you will get the error.
Note that reports defined this way would not cause an error in 10.1.3.2, but will result in the error in 10.1.3.3.
To work around this issue, define the parameter in BI Publisher's Edit report page.
The BI Publisher Query Builder includes an option to "Check All" when selecting columns from a table. If the table contains more than 20 columns, only the first 20 will be selected.
To work around this issue, you must manually select all columns.
When creating a query for a list of values (LOV), you can choose the "Default Data Source" or select a specific data source. If you select the "Default Data Source," when you run the report it may either fail to run and return the following error:
Parameter name: <parameter> Can not establish database connection (null)
or just display the "Processing...." indicator, and never return any data.
To work around this problem, select a specific data source when creating a query for an LOV.
This issue applies to release 10.1.3.3.2.
BI Publisher's Web service API definition includes the complex type "ScheduleRequest". In 10.1.3.3.2, several elements defined under ScheduleRequest have been changed from type "string" to type "boolean".
Any applications built against BI Publisher Web Services 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, and useUTF8Option.
The updated definition for 10.1.3.3.2 is as follows:
<complexType name="ScheduleRequest"> <sequence> <element name="deliveryRequest" nillable="false" 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="false" 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 release 10.1.3.3.2.
This issue applies to release 10.1.3.3.2.
BI Publisher's Web service API definition includes the complex type "ParamNameValue". In the 10.1.3.3.1 implementation "isMultiValuesAllowed" and "multiValuesAllowed" were redundant. In 10.1.3.3.2 and later "multiValuesAllowed" is removed. The new definition of the ParamNameValue complexType is:
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 BI Publisher Web Services 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 release 10.1.3.3.2.
In release 10.1.3.3.1 PublicReportService Web service API, validateLogin throws exception "SOAPFault thrown" when the user's credential validation fails. Starting with 10.1.3.3.2 when a credential validation fails, validateLogin will return "false" in the validateLoginResponse.
The new features in the 10.1.3.3, 10.1.3.3.1 , 10.1.3.3.2, and 10.1.3.3.3 releases are documented in the Oracle Business Intelligence New Features Guide. Use this document in conjunction with the Oracle Business Intelligence Publisher User's Guide version 10.1.3.2 found in the documentation library. A list of the new features can be found in the New Features section of this document.
In the Oracle Business Intelligence Publisher User's Guide, in the chapter "Using the Admin Functions," section: "Setting Up Data Sources," subsection: "Adding a JDBC Data Source," the format for the JDBC connection string for an Oracle database is incorrectly shown as:
The correct format includes a colon ( : ) after "thin" as follows:
The BI Publisher Certification Guide has been updated. Some databases have been removed from the list of supported databases for the BI Publisher Scheduler Schema. Please refer to the Oracle Business Intelligence Publisher Certification Information:
for more details.
This section describes issues that have been resolved since the initial release of Oracle BI Publisher version 10.1.3.3.
When viewing a report layout that has a chart in Excel output, you may not see the chart and only see a small icon in the place where you expect to see the chart.
To work around this problem, you must unblock security on image URLs as follows:
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>
Note that by relaxing this security policy as described above, any HTTP session can access and view these images without authentication. Although random numbers are used for image file names, it poses some risk to allow someone to write a program to explore dynamic images (charts and graph) used by BI Publisher HTML reports.
On certain platforms, when generating a report in PDF format from the View Report page, the "processing" or "busy" indicator may not appear to indicate that BI Publisher is processing the request, leaving the user unsure if the submit action was successful.
If your data source is concatenated XML from multiple SQL queries, the XML data will not load properly to the Template Builder from the direct connection to the BI Publisher server.
To work around this issue, after building your data model, generate sample data and save it to an accessible directory. Use the Template Builder's load data function (Oracle BI Publisher > Data > 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 User's Guide.
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.
In 10.1.3.3.0 the system parameter CURRENT_SERVER_URL available to be included in RTF layout templates does not return a value. This is fixed in 10.1.3.3.1.
If the administrator changes the name of the BI Publisher "Guest" folder and restarts the server for this change to take effect, users will be prompted to enter credentials the next time they try to access this folder. To work around this issue, do not change the name of the Guest folder.
If you are using an LDAP security model, the privileges of member groups may 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 may not inherit the privilges assigned to XMLP_Admin as expected.
In 10.1.3.3.0 users with the "BI Publisher Developer" role and not "BI Publisher Administrator" role get a 500 Server Internal Error when they attempt to Edit a report. The workaround was to grant "BI Publisher Administrator" role to all users who needed to edit reports.
If you are using the Template Builder for Word on Microsoft Windows XP and have applied the Microsoft Security Update for Windows XP KB936021, you may receive the following error when trying to load XML data:
"Compile error in hidden module Module-starter"
To work around this issue, perform 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.
When using 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"/>
If you are using BI Publisher's bursting feature and your bursting job includes PDF reports to be sent to a printer, the print reports may 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, in 10.1.3.3.1 the bursting engine sets the content type to application/octet-stream for print jobs.
If you use the <?xdofx:chr(n)?> function in an RTF template you may encounter the following error when trying to run or preview the report:
oracle.xdo.parser.v2.XPathException: Extension function error: Method not found 'chr'
The Oracle Business Intelligence New Features Guide contains detailed descriptions of the following new features added after the 10.1.3.2 release of Oracle BI Publisher. These include:
Template Builder Enhancements
Integration with Oracle BI Discoverer
Converting Reports from Oracle Reports to BI Publisher
Support for Digital Signatures in PDF Documents
Support for PostScript Printers
Time Out Value for Web Service Data Sources
Bidirectional Function for eText Data Fields
Oracle BI Publisher Web Services
Support for Document Cache
Support for New Output Types
DataDirect Connect for JDBC Drivers Bundled with BI Publisher Libraries
"Link to this Report" Can Now Be Set as a Report Option
Enhanced Support for Pagination Control in RTF Output
Support for Multiple Cascading Parameters
Support for Vertical Alignment of External Graphics
Support for Multiple Currency Symbol Displays in Report
This guide is included in the documentation library delivered with Oracle BI Publisher.
To reach AT&T Customer Assistants, dial 711 or 1.800.855.2880. An AT&T Customer Assistant will relay information between the customer and Oracle Support Services at 1.800.223.1711. Complete instructions for using the AT&T relay services are available at http://www.consumer.att.com/relay/tty/standard2.html. After the AT&T Customer Assistant contacts Oracle Support Services, an Oracle Support Services engineer will handle technical issues and provide customer support according to the Oracle service request process.
Our goal is to make Oracle products, services, and supporting documentation accessible to all users, including users that are disabled. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Accessibility standards will continue to evolve over time, and Oracle is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For more information, visit the Oracle Accessibility Program Web site at http://www.oracle.com/accessibility/.
Screen readers may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, some screen readers may not always read a line of text that consists solely of a bracket or brace.
This documentation may contain links to Web sites of other companies or organizations that Oracle does not own or control. Oracle neither evaluates nor makes any representations regarding the accessibility of these Web sites.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this software or related documentation is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:
This software is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of this software. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software in dangerous applications.
This software and documentation may provide access to or information on content, products and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third party content, products and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third party content, products or services.
Copyright © 2004, 2008, Oracle. All rights reserved.
Oracle is a registered trademark of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.