Known Issues

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

Topics:

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.

General Issues and Workarounds

Some features and functions don’t work as expected.

Topics:

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

Analyses and Dashboards Issues and Workarounds

This section describes issues and workarounds for analyses and dashboards.

Topics

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

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, scroll to the end of the the subject area list and then use the browser's search to locate the subject area.

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

Issues While Hovering Over a 3D Pie Graph

When interacting with a 3D pie graph in an analysis, if you continue to mouse over different segments of the pie graph the prior segments appear to be selected. This causes the graph to become disorganized.

To work around this issue, refresh the browser window to redraw the graph or convert the pie graph to 2D.

Applies to: 23B

Unable to Add Map Data

On the Manage Map Data administration page, when you attempt to add map data, you see messages such as these: "Unable to communicate with Oracle FMW Mapviewer Server" or "Could not connect to MapViewer."

This issue has no workaround.

Applies to: 23B

Publisher Reports Issues and Workarounds

This section describes issues and workarounds for Publisher reports.

Topics:

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

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: 24(A,B), 23(A,B,C,D)

Dynamic Date Overwrites User Input Date in Recurring Job

If you edit a Publisher scheduled job to change the value of a date parameter that uses a dynamic date function as the default value set in the data model, the default value of the date parameter incorrectly overwrites the updated input value.

This issue has no workaround.

Applies to: 24(A,B), 23(B,C,D)

Publisher Jobs Can't Generate Output for Shared Reports

When you schedule a Publisher job for a shared report, the job might fail because you don't have the permission to run the shared report.

This issue occurs when the Webservice optimization property is set to true.

To work around this issue, in the Publisher administration page, the administrator must set the Webservice optimization property to false.

Applies to: 23D

Publisher Generates Reports Only in English

Even though you’ve set the default language to a non-English language, Publisher generates the reports only in English.

This issue occurs when the Webservice optimization property is set to true.

To work around this issue, in the Publisher administration page, the administrator must set the Webservice optimization property to false.

Applies to: 23D

Excel Output of a Publisher Job Contains Junk Characters

If you specify Excel (.xls) as the output format for a Publisher job for a shared report, when you download the Excel output from the Report Job History page, you see junk characters in the Excel file.

To work around this issue, schedule a new job or republish the report to deliver the Excel file to an Email, FTP, or Content Server, and then download the Excel file from the specified destination.

Applies to: 23D

Publisher Reports Can’t Be Downloaded from the Firefox Browser

Using the /analytics URL in the Firefox browser, you can't download the report output from the Report Job History page.

To work around this issue, use the /xmlpserver URL in the the Firefox browser to download the report output from the Report Job History page or use the Chrome or Edge browser.

Applies to: 23D

Publisher Reports Downloaded as CSV Files Have a Size of Zero Kilobytes

If you have a Publisher report that you attempt to download as a large CSV file from the Report Job History page, the size of the file is shown as 0KB (zero kilobytes).

To work around this issue, send a large report to the Content Server or FTP Server, and then download as a CSV file from one of those servers.

Applies to: 23D, 24A

Unable to Download the HTML Output from an Oracle Enterprise Scheduler (ESS) Job for Publisher

You can't open the HTML output downloaded in a .zip file from an ESS job, if the report has images and the Embed images and charts in HTML for offline viewing property of the report is set to false.

To work around this issue, perform any of these tasks in Publisher:

  • Set the Embed images and charts in HTML for offline viewing property of the report to true.
  • In the Report Job History page, download the report output, or click Send to deliver the output to an email address or FTP server, or republish the report.

Applies to: 23D

Uploaded PGP Keys Aren't Displayed in the PGP Keys Page

In the PGP Keys page under Security Center, the PGP Keys uploaded earlier aren't displayed because of an issue in the user interface.

The administrator can’t perform these tasks:

  • View the uploaded PGP keys in the PGP Keys page.
  • Configure the SFTP, FTP, or Oracle WebCenter Content server with a PGP key.

This issue has no workaround. Don't try to upload the PGP keys again. The existing PGP keys are usable as long as you don't try to re-upload the PGP keys. If you have an urgent requirement to configure the PGP keys, contact Oracle Support.

Applies to: 24A

Custom Content Server (UCM) Connection Not Working

The custom Content Server connections that were working earlier aren't working now.

In 24A, the URI of the provisioned FA_UCM_PROVISIONED Oracle WebCenter Content Server changed from http to https for Oracle Fusion Cloud Applications environment converted to the new Oracle Cloud Console.

To work around this issue, edit the URI of the custom connection to make sure that it's similar to the URI of the provisioned FA_UCM_PROVISIONED Content Server.

Applies to: 24(A,B)

Can't Create, Run, or Edit Publisher Reports Built Using Analysis

After you upgrade to 24A and convert to the new Oracle Cloud Console, you can't create, run, or edit Publisher reports built using data from an analysis in OTBI.

To work around this issue, as a Publisher administrator or report author:

  1. Login to Oracle Fusion Cloud Service.
  2. Navigate to Report & Analytics under Tools, and click Browse Catalog.
  3. Open the analysis that you want to use as a dataset in the data model, and edit the analysis.
  4. On the Advanced tab, from the SQL Issued section, copy the entire Logical SQL, and then exit the analysis.
  5. Create a data model, perform these steps, and save the data model:
    1. Create a new dataset of type SQL Query, and then select Oracle BI EE as the data source.
    2. In the SQL Query field, enter the Logical SQL that you copied earlier.
  6. Use the new data model you created instead of the older data model that was built using an Analysis.

Applies to: 24A

Can't Open Analyses or Dashboards in OTBI When Using the Arabic Language

When you have the browser language set to Arabic, you see error message nQSError:77031 when you try to open analyses or dashboards from OTBI.

This issue has no workaround.

Applies to: 24A

Special Characters Don't Print Correctly in Checks

In 24A, after the open source fonts replaced the Monotype fonts, some MICR special characters don't print correctly.

To work around this issue, see My Oracle Support Document ID 3008727.1 for instructions to download and use the new oraMICR V2 font for printing checks.

Applies to: 24(A,B)

Can't Scan the Barcode Generated in Publisher Reports

In 24A, Publisher uses a new set of barcode fonts to generate barcodes. The barcode generation functionality remains the same for the new barcode fonts, but the barcode images generated might be smaller in size compared to the images generated in 23D. Some of the scanners might not read the barcodes generated in the PDF output.

To work around this issue, edit the template to increase the barcode field font size, and then test again with your scanner.

Applies to: 24(A,B)