Known Issues

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

Topics:

Review Scheduler Diagnostics

The Scheduler diagnostics page provides the runtime status of the scheduler.

The Diagnostics page displays how many scheduled report requests have been received by the JMS queues, how many of them have failed and how many are still running. The JMS status can be viewed at the cluster-instance level enabling you to decide whether to add more instances to scale up by one or more of these JMS processors.

For example, if there're too many requests queued up for the e-mail processor in one instance, you can consider adding another instance and enabling it to handle e-mail processing. Similarly, if there're very large reports being processed and showing in the Report Process queue in running status, then you can add another instance to scale up the Report Process capability.

Also, the Scheduler Diagnostics page reflects the status of each component to show if any component is down. You can see the connection string or JNDI name to the database, which cluster instance associates to which managed server instance, Toplink connection pool configuration, and so on.

If an instance shows a failed status, then you can recover the instance and with the failover mechanism of the JMS set up in the cluster, no jobs submitted are lost. When the server instance is brought back, it is immediately available in the cluster for service. The instance removal and addition reflects dynamically on the diagnostic page.

When an instance is added to the cluster, the Scheduler Diagnostics page immediately recognizes the new instance and displays the status of the new instances and all the threads running on that instance. This provides a powerful monitoring capability to the administrator to trace and resolve issues in any instance or any component of the scheduler.

The Scheduler Diagnostics page provides information on the following components:

  • JMS

  • Cluster

  • Database

The JMS section provides information on the following:

  • JMS Cluster Config: This section provides configuration information for JMS setup:

    • Provider type (Weblogic / ActiveMQ)

    • WebLogic version

    • WebLogic JNDI Factory

    • JNDI URL for JMS

    • Queue names

    • Temporary directory

  • JMS Runtime: This provides runtime status of all JMS queues and topics.

The Cluster section provides details on the cluster instance. Use this information to understand the load on each processor.

The Database section provides information on these components.

  • Database Config — Connection type, JNDI Name, or connection string

  • Toplink Config — Connection pooling, logging level

  • Database Schema

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(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(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(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(B,C,D)

MonthName Function Returns Month Number

In , 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(B,C,D)

Reports Issues and Workarounds

This section describes issues and workarounds for reports.

Topics:

Some 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(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(B,C,D)

Dynamic Date Overwrites User Input Date in Recurring Job

If you edit a 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(B,C,D)

Unable to Configure the Job Schedule Using Calendar

You can’t use Calendar to set the start and end dates of a 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(B,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(B,C,D)

Publisher Report Link in Dashboard Throws Error

The 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(B,C,D)

Custom Reports Might Fail with ORA-00979 Error

Some custom reports that use SQL queries with a GROUP BY clause might fail with the error "ORA-00979: not a GROUP BY expression" because the latest version of Oracle Database enforces stricter validation for GROUP BY usage.

To resolve this issue, review and update the SQL query for the data model of the report. Ensure that each non-aggregated expression in the SELECT list, as well as any applicable expression in the HAVING or ORDER BY clauses, is either included in the GROUP BY clause or used in an aggregate function.

Applies to: 26(B,C,D)