Known Issues

Learn now about the issues you may encounter when using Oracle Transactional Business Intelligence, and how to work around them.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Renamed Users Can't Access Their Custom Reports

Users might find that if their administrator has renamed their account, then they can’t access reports they created in My Folders using the previous user name.

The system considers the renamed user as a new user without the specific permissions granted to the previous user name.

To work around this issue as an administrator:

  1. Ask the user to log into the renamed account and to copy the content in the My Folders area of that account to the Shared Folders/Custom folder as a backup.
  2. Contact Oracle Support to request that they move the custom reports that were created under the previous user name to the account for the renamed user.

Applies to: 22A, 22B, 22C, 22D

BI Composer Unavailable in SSL Configuration

If your system is running with an SSL configuration, then you can't use BI Composer functionality.

This issue has no workaround.

Applies to: 22A, 22B, 22C, 22D

Can't Move Catalog Content from a 22A or 22B Environment to a 21D Environment

After your environment is upgraded to 22A or 22B, if you archive the catalog content in 22A or 22B, you can’t unarchive the 22A or 22B catalog content in a 21D environment.

This is a one-time limitation for the 22A or 22B upgrade. After your environment is upgraded to 22A or 22B, archiving and unarchiving content between environments will work as expected.

If you want to use the Archive and Unarchive actions to move the catalog content from stage to production environments, before you move the catalog content, confirm that Oracle has upgraded both stage and production environments to 22A or 22B.

There is a workaround only to move Publisher catalog objects between 22A or 22B environment and 21D environment. Navigate to the Publisher Catalog page using the Publisher URL (/xmlpserver), and use the Download and Upload actions to move Publisher data models and reports (not Excel reports for 22A) between 22A or 22B environment and 21D environment. If your Publisher reports contain XLS templates, see Unable to Unarchive or Download Publisher Reports with Excel Templates.

Applies to: 22A, 22B

Change in getAccounts() API

The getAccounts() API has changed to allow only full name search.

The getAccounts() API fails if you use the asterisk character (*) in the query.

Specify the full name of the user when you use the getAccounts() API for searching user accounts (for example, LDAP users or application roles).

Applies to: 22A, 22B, 22C, 22D

Unable to Delete the Custom Folder After Upgrade

When your system is upgraded to Release 22A or 22B, you can't delete the Shared Folders/Custom folder that's included with Oracle Transactional Business Intelligence.

This issue has no workaround

Applies to: 22A, 22B

Unable to Rename the Custom Folder After Upgrade

When your system is upgraded to Release 22A or 22B and you attempt to rename the Shared Folders/Custom folder that's included with Oracle Transactional Business Intelligence, you see that the folder is copied instead of being renamed.

This issue has no workaround

Applies to: 22A, 22B

Update Agent Notifications and Publisher Configuration in a Test Environment After Environment Refresh (P2T)

During environment refresh (P2T), the agent notifications and Publisher configuration are copied from the production environment to the test environment. The agent notifications and Publisher configuration used in production might not match what’s needed in the test environment.

To work around this issue, see Doc ID 2861677.1.

Applies to: 22A, 22B

Issues When You Search the Catalog If You've Been Assigned More Than 1024 Application Roles

If you've been assigned more than 1024 application roles, you might be unable to search the catalog.

To work around this issue, check the application roles assigned to you. Some application roles might inherit other roles. Contact your security administrator to remove those roles that you don't need.

Applies to: 22A, 22B, 22C

Archiving and Unarchiving Dashboards Loses Links for Analyses

When you archive a dashboard and unarchive it on another environment, you might notice that some or all links below analyses on that dashboard are missing.

To work around this issue, ensure that the catalog folders and objects on the destination environment match the structure on the original environment.

Applies to: 22A, 22B, 22C, 22D

Prompt Value Reset to All Column Values

You can create prompts and make every prompt dependent on all other prompts.

When you then select a value in a prompt, the query for each prompt is recreated. You might find that the previously selected value of some prompts is reset to "All Column Values," and the query returns no results. To work around this issue, don't make all prompts dependent on each other.

Applies to: 22A, 22B, 22C, 22D

MonthName Function Returns Month Number

In Oracle Transactional Business Intelligence, the MonthName function returns the numeric value for a month, for example 7 for July or 11 for November, instead of the month name.

To work around this issue, use custom format strings to apply formatting.

Applies to: 22A, 22B, 22C, 22D

Issues While Searching for Subject Areas During Analysis Creation

When you search for a subject area to use for creating an analysis, you might find that the search takes a long time and might not return any results.

To work around this issue, use the browser's search to locate the subject area.

Applies to: 22A, 22B, 22C, 22D

Issues with Publisher Web Services

The Publisher web services framework changed.

The new Publisher web services framework:

  • Strictly validates the values passed and enforces the types. For example, for Boolean elements, specify the values as true or false only in lowercase.
  • Doesn’t allow a value in the SOAPAction header. Replace the values with an empty string in the SOAPAction header.
  • Changed the web service response for error messages. The web service response:
    • Returns null instead of an empty string.
    • Doesn’t contain the exception type (AccessDeniedException, InvalidParametersException, or OperationFailedException) in the SOAP response.
  • Changed the Publisher web service response for error messages in the following WSDLs:
    • /v2/CatalogService?wsdl
    • /v2/DataSourceConfigService?wsdl
    • /v2/DeliveryServerConfigService?wsdl
    • /v2/PluginService?wsdl
    • /PublicReportService?wsdl
    • /PublicReportService_v11?wsdl
    • /v2/ReportService?wsdl
    • /v2/RuntimePropertiesConfigService?wsdl
    • /v2/ScheduleService?wsdl
    • /v2/SecurityService?wsdl

To work around this issue, correct your client APIs and error handling.

Applies to: 22A, 22B

XML Response Change in Publisher Web Services Calls

The ns2 namespace prefix has been removed from the XML response in Publisher web services calls.

The XML response itself remains the same and completes without error. However, if you’re using this prefix in your parsing of the web services response (for example, searching for ns2 with a string API), then you might experience a failure in that code that exists outside of the Publisher web services. If you’re using a standard XML parser, you won’t encounter an issue; if you’re using a string parser, you might encounter an issue.

See these code examples of the difference between OTBI Release 21D and 22A to work around this issue.

Response in OTBI Release 21D:

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Header/>
   <env:Body>
      <ns2:runReportResponse xmlns:ns2="http://xmlns.oracle.com/oxp/service/PublicReportService">
         <ns2:runReportReturn>
            <ns2:reportBytes>JVBERi0xLjYNCjUgMCBvYmoNCjw8DQovVHlwZSAvUGFnZQ0KL1BhcmVudCAzIDAgUg0KL1Jlc291cmNlcyA0ID==</ns2:reportBytes>
            <ns2:reportContentType>application/pdf</ns2:reportContentType>
            <ns2:reportFileID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
            <ns2:reportLocale xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
            <ns2:metaDataList xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         </ns2:runReportReturn>
      </ns2:runReportResponse>
   </env:Body>
</env:Envelope>

Response in OTBI Release 22A:

<env:Envelope xmlns:env="http://www.w3.org/2003/05/soap-envelope">
   <env:Header/>
   <env:Body>
      <runReportResponse xmlns="http://xmlns.oracle.com/oxp/service/PublicReportService">
         <runReportReturn>
            <reportBytes xmime:contentType="application/octet-stream" xmlns:xmime="http://www.w3.org/2005/05/xmlmime">JVBERi0xLjYNCjUgMCBvYmoNCjw8DQovVHlwZSAvWE9iamVjdA0KL1N1YnR5cGUgL0ltYWdlDQovRmlsdGVyIC9GbGF0ZURlY29kZQ0KL0xlbmd0aCAyNzM3DQovV2lkdGggNDMyDQovSGVpZ2h0IDcxDQovQml0c1BlckNvbXBvbmVudCA4DQovQ29sb3JTcGFjZSAvRGV2aWNlUkdCDQo+Pg0Kc3RyZWFtDQp4nO1d</reportBytes>
            <reportContentType>application/pdf</reportContentType>
            <reportFileID xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
            <reportLocale xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
            <metaDataList xsi:nil="true" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"/>
         </runReportReturn>
      </runReportResponse>
   </env:Body>
</env:Envelope>

Applies to: 22A

ScheduleReport() Requests Fail

You might encounter an issue only if you've upgraded from an earlier version and had removed the <item></item> tags from the scheduleReport requests.

The <item></item> tags are allowed in the scheduleReport request. Edit your scheduleReport requests to add the <item></item> tags required in sections such as the deliveryChannels and parameterNameValues sections.

For example, if you had removed the <item></item> tags from the parameterNameValues section of the scheduleReport requests:

<sch:scheduleReport>
         <scheduleRequest>
             <reportRequest>
               <attributeCalendar>GREGORIAN</attributeCalendar>
               <attributeFormat>XML</attributeFormat>
                <parameterNameValues>
                  <listOfParamNameValues>
                      <name>lLookupType</name>
                      <values>
                        1972 SIC
                      </values>
                 </listOfParamNameValues>
                 <listOfParamNameValues>
                    <name>lLookupCode</name>
                    <values>
                      0212
                    </values>
                 </listOfParamNameValues>
               </parameterNameValues>
               <reportAbsolutePath>/Custom/XYZ/FndLookupsRptWithParam.xdo</reportAbsolutePath>
            </reportRequest>
            <userJobName>LMCFndLookupsParamTest4</userJobName>
         </scheduleRequest>
      </sch:scheduleReport>

Change the code similar to the following to add the <item></item> tags:

<sch:scheduleReport>
         <scheduleRequest>
             <reportRequest>
               <attributeCalendar>GREGORIAN</attributeCalendar>
               <attributeFormat>XML</attributeFormat>
                <parameterNameValues>
                  <item>
                    <name>lLookupType</name>
                    <values>
                      <item>1972 SIC</item>
                    </values>
                  </item>
                  <item>
                    <name>lLookupCode</name>
                    <values>
                      <item>0212</item>
                    </values>
                  </item>
                 </parameterNameValues>
               <reportAbsolutePath>/Custom/XYZ/FndLookupsRptWithParam.xdo</reportAbsolutePath>
            </reportRequest>
            <userJobName>LMCFndLookupsParamTest1</userJobName>
         </scheduleRequest>
      </sch:scheduleReport>

Applies to: 22A, 22B, 22C, 22D

getReportData() Requests Fail

You might encounter an issue only if you've upgraded from an earlier version and had removed the <item></item> tags from the getReportData requests.

The <item></item> tags are allowed in the getReportData request. Edit your getReportData requests to add the <item></item> tags required in the reportValues section.

For example, if you renamed <item></item> tags to ValidateReportParameters in the reportValues section, the getReportData request might not return the correct response.

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:rep="http://xmlns.oracle.com/oxp/service/report"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <soapenv:Header/>
   <soapenv:Body>
      <rep:getReportData
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
         <reportPath
xsi:type="xsd:string">/Custom/Technical/Interface/I_P2P_004/ARI_APIH_IMPORTSET
_PARAM.xdo</reportPath>
         <reportValues xsi:type="rep:ArrayOfParamNameValue"
soapenc:arrayType="rep:ParamNameValue[1]">
          <ValidateReportParameters>
          <name>BATCH_NAME</name>
          <value>5011181</value>
          </ValidateReportParameters>
         </reportValues>
         <userName xsi:type="xsd:string">USERNAME</userName>
         <passwd xsi:type="xsd:string">PASSWORD</passwd>
         <format xsi:type="xsd:string">CSV</format>
         <template xsi:type="xsd:string"/>
      </rep:getReportData>
   </soapenv:Body>
</soapenv:Envelope>

Change the code similar to the following to add the <item></item> tags:

<soapenv:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:rep="http://xmlns.oracle.com/oxp/service/report"
xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/">
   <soapenv:Header/>
   <soapenv:Body>
      <rep:getReportData
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
         <reportPath
xsi:type="xsd:string">/Custom/Technical/Interface/I_P2P_004/ARI_APIH_IMPORTSET
_PARAM.xdo</reportPath>
         <reportValues xsi:type="rep:ArrayOfParamNameValue"
soapenc:arrayType="rep:ParamNameValue[1]">
          <item>
          <name>BATCH_NAME</name>
          <value>5011181</value>
          </item>
         </reportValues>
         <userName xsi:type="xsd:string">USERNAME</userName>
         <passwd xsi:type="xsd:string">PASSWORD</passwd>
         <format xsi:type="xsd:string">CSV</format>
         <template xsi:type="xsd:string"/>
      </rep:getReportData>
   </soapenv:Body>
</soapenv:Envelope>

Applies to: 22A, 22B, 22C, 22D

Message Tag Missing in getScheduledReportStatusReturn() Response

The getScheduledReportStatusReturn() service response doesn't include the <message> XML tag.

To work around this issue, change the client code to handle the missing <message> XML tag.

Applies to: 22A

Certain Users Can’t Edit, Schedule, or Run Publisher Reports

If you used an earlier version of OTBI, you might find that in the current version, certain users can’t view the content in My Folders, edit, schedule, or run Publisher reports.

This is likely because those users inherited the BI System role through a custom application role. Because the BI System role is reserved for internal use only, you should never associate it with any custom application role.

To work around this issue, go to the Security Console and remove the BI System role assigned to the custom application roles.

Applies to: 22A

Unable to Unarchive or Download Publisher Reports with Excel Templates

You can’t use the Unarchive or Download actions to move the Publisher reports that use an Excel template from a 21D environment to a 22A environment.

When you archive a report with an Excel template in 21D, the 0B .png file created causes issues when you download the archive in 22A.

To work around this issue, remove the 0B .png file from the archive, and then upload the archive in 22A.

Applies to: 22A

Issue Delivering Publisher Reports to a Remote Directory

You might encounter failures when scheduled jobs attempt to deliver Publisher reports to a remote directory on a secure FTP (SFTP) server.

This is likely because the remote directory path name includes the backslash character (\).

To work around this issue, use the forward slash character (/) instead of the backslash character (\) in the directory path name.

Applies to: 22A

Publisher Limits the Number of Rows in a Sample Data View

When you view data in the data model editor of Publisher, the number of rows in the sample XML data is limited so that you can quickly test and model your data, and then create templates.

In a data model, when you use count (*) to get the count of rows in a table, you get the count of rows in the sample data instead of the actual count of rows in the table.

To work around this issue, generate the report to view all the records.

Applies to: 22A

Publisher Reports Fail for Multiple Groupings

Publisher reports fail if the template specifies multiple grouping of data based on multiple fields.

To work around this issue, edit the template to have only one group based on one field. Search and edit all the for-each-group elements in the template.

Applies to: 22A

Can’t Find Publisher Report Files After Bursting to UCM

You might find that the Publisher bursting job successfully delivered to UCM, but you can’t find the report files in the UCM custom specific folder.

To work around this issue, don’t search for the report files in the UCM custom specific folder. Instead, use the UCM Search feature or do a Quick Search using the Content ID in the top-right corner of UCM. If you use integrations to pull reports from UCM and you need to download files from UCM, use the search web service request without specifying the folder name but passing only the UCM Content ID.

Applies to: 22A, 22B

Some Publisher Reports With Parameters Fail to Run

When you run reports that use parameters, if the parameter values end with a space, you might get “Invalid Parameters Requested” error.

To work around this issue, make sure the parameter values don’t contain extra spaces.

Applies to: 22A, 22B, 22C, 22D

Publisher Reports Might Contain Incorrect Number of Records

Publisher reports might contain additional records because the data joins aren't applied.

To work around this issue, recreate data joins in the data model.

Applies to: 22A

Unable to Apply Changes to the Provisioned JDBC Connection in Publisher

In Publisher, you can't assign roles or save changes to the provisioned Oracle BI EE JDBC connection because the Apply button is disabled.

This issue has no workaround.

Applies to: 22A, 22B

Unable to Schedule Publisher Jobs When Language Is French

You can't schedule jobs in Publisher when the language for the system is French.

This issue has no workaround.

Applies to: 22A, 22B

Publisher Job Delivery to SFTP Fails

Scheduled jobs fail to deliver reports to SFTP because the PGP key files are missing in the 22A or 22B environment.

To work around this issue, check if the PGP key files are missing and reupload the PGP key files in the 22A or 22B environment.

Applies to: 22A, 22B

Publisher Reports Using xdo_user_timezone System Variable Fail

Publisher reports fail because the xdo_user_timezone system variable incorrectly returns a null value.

This issue has no workaround.

Applies to: 22A, 22B, 22C

Deep Links Don’t Work in Publisher Reports

The deep links in Publisher reports don’t work, because the hyperlinks defined in the XPT template aren’t generated properly in the reports.

To work around this issue, use the to_char() method in the query to convert the field that generates the dynamic URL to a String type.

Applies to: 22A, 22B, 22C

UCM Security Groups Aren't Listed For Scheduling Jobs

When you schedule an ESS job to deliver reports to Oracle WebCenter Content server (UCM), the security groups aren't available for selection.

This issue has no workaround.

Applies to: 22A, 22B

XPT Report Error Message When Editing

You see an error message when you create or edit an XPT report, if the parameter name in the data model of the report contains special characters.

When you try to create a report, you see an error message similar to Failed to load datasource...xdo, readBusinessViewXML error: Error: undefined:key=Error.Failed to load url.

When you edit an existing report, you see an error message similar to Unable to retrieve metadata from Data model error.

To work around this issue, edit the data model to remove the special characters from the display label of the parameter.

Applies to: 22A, 22B

Publisher Report Delivery to SFTP Fails

Report delivery to SFTP fails with an error message similar to: "Delivery to SFTP completed with failure. The public key algorithm for this private key is not supported" .

To work around this issue, edit the SSH private key file to add a line at the end of the file and re-upload the edited private key file for SFTP delivery.

  1. Using a text editor, open the SSH private key file in the local file system for edit, add a line at the end of the file (after the last line, -----END RSA PRIVATE KEY-----), and then save the file.
  2. In Publisher administration, navigate to the System Maintenance page and use Upload Center to upload the edited SSH private key file as an SSH Private Key file.
  3. Navigate to the SFTP delivery configuration page. From the Private Key drop-down list in the Security section, select the edited private key file you uploaded, then click Test Connection to verify that the connection works with the modified private key file.

Share Report Link Displays Incorrect Report URL

In the Report Viewer, if you click Share Report Link, the URL for the current report contains additional characters.

If you try to open the report using the share report link, you see an error message similar to the following:

Unauthorized Access: Either you do not have the privilege, or you have not signed in.

To work around this issue, ensure that the URL doesn't contain the additional –sTkn parameter. Use the following format to build and share the URL for the report, and See Access Reports via a URL.

http://<server:port>/xmlpserver/<ReportDirectory>/<ReportName>.xdo

where

  • server:port is the name of the server and port number where Publisher is running.
  • xmlpserver is a required static string (the name of the application).
  • ReportDirectory is the folder path of the report. When the report is under Shared Folders, don’t include Shared Folders in the path. If the report is under My Folders, include the ~username as the first node in the path.
  • ReportName.xdo is the name of the report with the .xdo extension. If the name contains spaces, replace the space with a "+" character.

Applies to: 22A, 22B

downloadReportDataChunk() Method of PublicReportService Fails

The downloadReportDataChunk() method of PublicReportService intermittently fails to fetch the report output data.

You might get an error message similar to oracle.xdo.servlet.scheduler.ProcessingException: DMS-50752: At least one of the parameters for "Noun()" is null or empty.

To work around this issue, replace the downloadReportDataChunk() method of PublicReportService with the downloadReportDataChunk() method of V2 ReportService.

Applies to: 22A, 22B, 22C, 22D

Data Model Based on a CSV File Doesn’t Display Data

When you have a dataset that’s based on a CSV file and you update the alias and display names of columns, data is shown on the Data tab if you update ten or fewer columns. However, as soon as you update the eleventh column, the Data tab shows no data.

This issue has no workaround.

Applies to: 22A, 22B, 22C, 22D

Incorrect Number Formatting in Scheduled Reports

The comma separator format (#,##0) specified in the RTF template for numbers isn't applied correctly in the outputs generated by jobs scheduled using the Publisher user interface.

To work around this issue, use one of the following methods to generate output:

  • Instead of scheduling the report, run the Publisher report online using the /analytics or /xmlpserver URL, and then from the Actions menu, select Export to export the output.
  • Create a custom ESS job to run the Publisher report and generate the output.
  • Use the Publisher web services to run the Publisher report and generate the output.

Applies to: 22C, 22D