Known Issues

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

Topics:

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

Publisher Reports Issues and Workarounds

This section describes issues and workarounds for Publisher reports.

Topics:

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

Unable to Configure the Publisher Job Schedule Using Calendar

You can’t use Calendar to set the start and end dates of a Publisher job.

To work around this issue, manually enter the start and end dates by typing the date and time in the date fields. For example, Oct 30, 2025 3:07:51 AM.

Applies to: 26(A,B), 25(C,D)

Scheduled Jobs Using Inactive Template Fail

If your job is using an inactive template, your job might fail.

To run the job, edit the template and make the template active.

Applies to: 26(A,B), 25D

Publisher Report Link in Dashboard Throws Error

The Publisher report link in the dashboard throws "414 URL too long" error.

To work around this issue, embed the report in the dashboard instead of adding a link to the report.

Applies to: 26(A,B), 25D