Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at

Access to Oracle Support

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit or visit if you are hearing impaired.

Microsoft Internet Explorer Is No Longer Supported

If you use Internet Explorer 11, then you'll experience significant performance issues.

Oracle no longer supports Internet Explorer and strongly recommends that you use a modern browser. Refer to the Microsoft Support website for information about the latest Microsoft browsers.

Known Issues with Oracle Essbase Database Connections and Data Sources

The Oracle Essbase database connection type and Oracle Essbase data sources have a number of known issues.

  • Searching for a specific column within an Oracle Essbase data source displays a "No Matches Found" message.

  • The Advanced Analytics functions don't work for Oracle Essbase data sources.

  • If you create an Oracle Essbase connection and provide invalid login information, you'll see this incorrect error message: "Failed to save the connection. JDS - Invalid syntax." The error message should state "Failed to save the connection due to an invalid user name and password.”

  • When creating an Oracle Essbase connection, you can choose the Require users to enter their own username and password authentication option, but Oracle Analytics Desktop doesn’t activate this behavior and instead authenticates all users with the user name and password that you specified.

  • Time-based columns are sometimes not imported correctly. A column displaying a date in text can’t be converted to a column of date data type because of format mismatch.

  • Oracle Essbase data sources don’t work in data flows.

  • When working in a workbook, you can’t use match columns to join an Oracle Essbase data source to any other data source included in the workbook.

  • When you import an Oracle Essbase data source, you can’t prepare the data, and you can’t edit the data after import. For example, you can't change a column’s data type or aggregation.

Known Issues with MongoDB Connections and Data Sources

The MongoDB database connection type and MongoDB data sources have a number of known issues.

  • Schema map from MongoDB not refreshed — When you create a connection to a MongoDB data source, the underlying driver automatically creates a normalized schema for the MongoDB database. If collections are added to the schema in the MongoDB database, the driver can't find these additional collections. This issue has no workaround.

Null Values in XLSX File Set to String

If you're adding an XLSX file as a data source and if the spreadsheet’s null values are expressed as hyphens, then Oracle Analytics treats the null values as strings irrespective of the other values in the column.

To work around this issue, remove the hyphens from the column and try to import the XLSX file again.

Custom Formats in Analyses Not Available

In Oracle Analytics Cloud, if you open an analysis that contains a custom format that was created in the Analysis Editor, you see an error message. You might've applied a custom format in the Analysis Editor using the Custom Numeric Format option on the Data Format tab in the Column Properties dialog.

To work around this issue, edit the analysis in the Analysis Editor and remove the custom formatting, or remove the item in the analysis that contains the custom format. Then open the analysis again.

Saving a Data Flow Using the Save As Option

The Save As option doesn't work if you try to save a data flow with a name that already exists (that is, the existing data flow isn't overwritten).

To work around this issue, when you use the Save As option, specify a data flow name that doesn't already exist, or first delete the existing data flow that has the name you want to use.

Content Missing on the Home Page After Upgrading

When you access the Home page in a browser using the https://host:port/dv/ui URL, you might notice that some content isn't displayed.

Disabled or Broken Customizations to the Home page - If you notice that customizations to the Home page are disabled or broken or that specific content sections aren't displayed, enable and re-order sections as follows:

  1. In a browser, access this URL:


  2. In the header, click the context menu and select Customize Home Page.
  3. Ensure that sections aren't set to hidden or disable.
  4. If sections are set to hidden or disabled, place them in the appropriate positions.
  5. Save the changes.

Changes to the Users and Roles Page in Console

In a recent update to Oracle Analytics Cloud, you might have noticed changes to the Users and Roles page in Console.

The Console has now been reverted to a previous update due to reported issues. The changes to the Console will likely be included in a future update that resolves the reported issues.

Concurrent Restore Operations Not Recommended

Any user with administrator permissions can restore a snapshot. Oracle Analytics Cloud doesn't prevent multiple users from starting concurrent restore operations, but this often causes snapshot restore failures.

To avoid such issues, Oracle recommends that you coordinate restore operations with other administrators and wait for one restore operation to finish before starting another one.

Issues When Creating or Restoring Large Snapshots

When you try to create or restore very large snapshots (those with a size of 5GB or larger), you might see an error message similar to the following one: commitImport Operation:importBAR StatusCode:Operation Failed

This error occurs when the system times out during the creation or restore process. If the problem persists, contact Oracle Support.

Issue with Time Series Functions and Double Data Type Time Dimension Keys

You might notice an internal error message when you work with time series functions in analyses. The error occurs because time dimension keys are set to a data type of Double in the Model Administration Tool.

To work around this issue, change the data type of the time dimension keys to INT in the Model Administration Tool. Or go to the database properties and disable the TIME_SERIES_TODATE_SUPPORTED database feature.

Virus Scanner Settings Not Taking Effect

You might find that settings that you make for the virus scanner in the Console don't take effect.

To work around this issue, reapply your system settings:

  1. Click Console, and then click System Settings.
  2. Click Apply.

Wait a few moments for the changes to refresh through the system.

Tables and Columns Not Replicated from Oracle Fusion Cloud B2C Service

You can’t query some columns and tables exposed by data sources from Oracle Fusion Cloud B2C Service due to an issue with the API in Oracle Fusion Cloud B2C Service for extracting bulk data. If you include such tables or columns in your data flow for data replication, the table may fail to replicate and you might see one of several error messages:

This query is not supported: Non-existant column: 'primaryContact'

This query is not supported: no such table: namedIDs

This query is not supported: Unknown table or column 'filters'

To work around these errors, so you can replicate other tables and columns from Oracle Fusion Cloud B2C Service, exclude the columns or tables mentioned in the error messages:

  1. Uncheck any columns that are referenced in “unknown column” error messages.

  2. Uncheck any tables that are referenced in “unknown table” error messages.

  3. Save and rerun the data replication.

Error Adding Table With Mixed-Case Name or Column Names to a Dataset

Oracle Analytics displays the "Create Dataset Table Failed" error message when you add a database table with a name that uses mixed-case or a table that contains column names with mixed-case to a dataset.

Examples of mixed-case names include Sales, Products, Cust_ID, or Quantity_Sold.

To work around this issue, create a dataset and in the Dataset editor, go to the Connections pane in the Data Panel, and drag and drop the Manual Query option to the Join Diagram. Write the SQL statement, making sure to:
  • Double quote all table and column name identifiers that use mixed case.
  • Alias the mixed case table column name identifiers with uppercase.

For example: select "EfG_Field" as EFG_FIELD, "HiJ_Field" as HIJ_FIELD from "AbCd"

See Add a Table to a Dataset Using a SQL Statement.

MySQL Connections Using Data Direct JDBC Driver TLSv1.3 Not Supported

Oracle Analytics Cloud supports only SSL connections through Data Gateway to MySQL databases no later than version 8.0.12.

Known Pixel-Perfect Reporting Issues

Some Pixel-Perfect Reporting features and functions don’t work as expected in Oracle Analytics Cloud.


Bar Charts Showing Time on the X-Axis Don’t Display Axis Labels Correctly

If a report using the Oracle Analytics Publisher Template (.xpt) includes a bar chart, and if Time is represented along the x-axis, then the x-axis label sometimes doesn’t display properly.

The first label entry is skipped and the first bar data appears glued to the y-axis.
  1. In the data model SQL query for the report, use the TO_CHAR method on the date/time fields to change the data type of the field from Date to String.
  2. Open the report in the Layout Editor.
  3. Select the chart and expand the properties pane.
  4. Turn off the Time Series setting and clear the settings for Day, Month, Year, and Time formats.
  5. Save the layout changes.

Oracle Business Intelligence Mobile Issues and Workarounds

Issues and workarounds for Oracle BI Mobile are described in Oracle Fusion Middleware Release Notes for Oracle Business Intelligence Mobile for Apple iOS and Google Android available at:

“Service is not accessible” Message Reported After Scaling Up

Only Oracle Cloud Infrastructure Classic This topic applies only to Oracle Cloud Infrastructure Classic.

After you scale up an Oracle Analytics Cloud - Classic instance, (for example, from 2 OCPU to 8 OCPU), you might see this error message in the activity log:

Access OAC via http://ip-address/va gives following error. Service is not accessible

To work around this issue, navigate to Analytics Cloud in My Services, click the Manage the service icon for the service that you scaled up, and select Restart. See Start, Stop and Restart Services.

Only IDCS or IAM Identity Domain Users Can Connect to Oracle Analytics Cloud Using the Model Administration Tool

The Model Administration Tool provides an option to connect to Oracle Analytics Cloud.

To use this feature:
  • Oracle Identity Cloud Service (IDCS): If your Oracle Analytics Cloud federates with Oracle Identity Cloud Service you must connect with Oracle Identity Cloud Service user credentials.

  • Oracle Cloud Infrastructure Identity and Access Management (IAM) Identity Domains: If your Oracle Analytics Cloud uses an IAM identity domain for identity management, you must connect with your identity domain user credentials.

If Oracle Analytics Cloud uses an external identity provider such as Active Directory for Single Sign-on (SSO) and you try to connect with your SSO user credentials, you see the message "Connection failed 401: Unauthorized" when you try to connect.

To work around this issue, sign-in with your IDCS or IAM credentials.

User Assistance for the Model Administration Tool

If you want user assistance for the Model Administration Tool, go to the Oracle Help Center page. Don't use the context-sensitive help links available in the tool; this content is out-of-date.

Known Issues in Oracle Analytics Cloud Data Gateway

Some features in Oracle Analytics Cloud Data Gateway don't work as expected.

  • Creating remote connections to data sources other than Oracle requires changing the database type. When specifying a remote connection from the .rpd file to a remote data source, you must initially specify Oracle as the database type while you set up the connection pool to point to Data Gateway. After saving your connection pool, you must change the database type to the appropriate type supported as a remote connection.

Known Issues in Semantic Modeler

Some features in Semantic Modeler don’t work as expected.

  • Order of a subject area's table listing - The Presentation Layer pane displays a subject area's tables in alphabetical order rather than in the order the tables are listed in the Subject Area editor's Tables tab. To work around this issue, use the Subject Area editor's Tables tab to view and change the order of the tables.

  • System data connections aren't compatible with usage tracking - You can't use Semantic Modeler to set up usage tracking. To work around this issue, export the semantic model from Semantic Modeler and then use the Model Administration Tool to configure usage tracking.

  • Lookup tables descriptions aren't displayed in the business model lookup table list - When you're working in the logical layer and click a business model to view its list of lookup tables, the lookup table descriptions aren't displayed. To work around this issue, in the business model tab, click a lookup table name to open the table's tab and view its description.

  • Pasted presentation tables hierarchies contain incorrect display columns - When you cut and paste a presentation table from one subject area to another, Semantic Modeler doesn't refactor the display column in the presentation hierarchy levels. To work around this issue, manually set the display column.