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 customer access to and use of Oracle support services will be pursuant to the terms and conditions specified in their Oracle order for the applicable services.

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, copy the content from the user's My Folders area to the Shared Folders/Custom folder as a backup.

  • Before renaming a user account, ask the user to copy the reports from their My Folders to the Shared Folders/Custom folder as a backup.
  • If a user was renamed before taking a backup of their My Folders, perform the following:
    1. Ask the user to log into the renamed account.
    2. You as an administrator navigate to the Admin view to see the user's old account, and then copy the content from the user's My Folders area of the old account to the Shared Folders/Custom folder which the user can access.
    3. Ask the user to copy content from the Shared Folders/Custom folder to My Folders in the renamed account.

Applies to: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

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: 25(A,B,C)

Publisher Report Fails with ORA-17090 Error

If a Publisher report uses a data model that’s created with a procedure call having a bind variable in the comments, the report likely fails with this error message:

"java.sql.SQLException: ORA-17090: Operation not allowed: Ordinal binding and Named binding cannot be combined!" https://docs.oracle.com/error-help/db/ora-17090/

To work around this issue, make one of these edits in the procedure call:

  • Remove the comments containing the bind variable.
  • Remove the colon character (:) from the commented line.
  • Move the commented line to the bottom of the PL/SQL block just before the end (END;).

Applies to: 25B

Change in the XML Response of ScheduleReportWSSService Web Service

Because the XML response of the ScheduleReportWSSService web service includes the ns3 string, you might encounter an issue.

When using a standard XML parser, you won't encounter an issue. When using a string parser, you might encounter an issue.

Response in 25A:

<env:Envelope xmlns:env=http://www.w3.org/2003/05/soap-envelope>
   <env:Header/>
   <env:Body>
      <ns0:scheduleReportResponse xmlns:ns0=http://xmlns.oracle.com/oxp/service/ScheduleReportService>
         <ns0:scheduleReport>198682</ns0:scheduleReport>
      </ns0:scheduleReportResponse>
   </env:Body>
</env:Envelope>

Response in 25B:

<env:Envelope xmlns:env=http://www.w3.org/2003/05/soap-envelope>
   <env:Header/>
   <env:Body>
      <ns0:scheduleReportResponse xmlns:ns0=http://xmlns.oracle.com/oxp/service/ScheduleReportService>
         <ns3:scheduleReport xmlns:ns3=http://xmlns.oracle.com/oxp/service/ScheduleReportService>92047</ns3:scheduleReport>
      </ns0:scheduleReportResponse>
   </env:Body>
</env:Envelope>

Oracle recommends that you use an XML parser instead of a string parser.

Applies to: 25(B,C)

JRF Web Service Methods Sometimes Don’t Work

In 25B and later releases, the JRF web service methods won’t work if you pass Boolean values that aren’t in lower case.

Oracle recommends that you pass Boolean values in lower case to the JRF web service methods.

Applies to: 25(B,C)

Unable to View the List of Scheduled Jobs in Publisher

In 25B, the Manage Report Jobs page or the Manage Report Job History page might not list the scheduled jobs.

To work around this issue, add more filters for the search criteria to list the scheduled jobs in the Manage Report Jobs page or the Report Job History page.

Applies to: 25B