Oracle® Cloud

Known Issues for Oracle Data Visualization Cloud Service


February 2019

Known Issues

Learn about the issues you may encounter when using Oracle Data Visualization Cloud Service and how to workaround them.

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.

Supported Browsers

This topic describes the minimum requirements for web browsers that Oracle Data Visualization Cloud Service supports.

Web Browser Version

Microsoft Internet Explorer

11 and later

Microsoft Edge

38 and later

Google Chrome

54 and later

Mozilla Firefox

45 and later

Apple Safari

10 and later

Known Data Visualization Issues

If you encounter an issue visualizing your data, check here for a workaround.

Issues Importing Data Flows Containing Operators and Multiple Conditions from Oracle Analytics Cloud or Oracle Data Visualization Desktop

In Oracle Analytics Cloud or Oracle Data Visualization Desktop, you can export projects that include data flows containing join conditions with operators and multiple conditions using AND or OR.

Oracle BI Cloud Service and Oracle Data Visualization Cloud Service don’t support these join functionalities. If you import such projects, Oracle BI Cloud Service or Oracle Data Visualization Cloud Service changes the join operator to “equals” and treats multiple join conditions as AND.

Oracle RightNow Cloud Service Has a New Name

Oracle RightNow Cloud Service is renamed to Oracle Service Cloud.

The Data Visualization’s Create New Connection and Add a New Connection dialogs are updated to reflect this name change.

List Visualization Doesn’t Work Properly

If you use the List visualization in your projects, then you might encounter the following issues.

  • If you have a canvas with multiple List visualizations with the Use as Filter setting enabled and the user makes selections in more than one List visualization, Data Visualization can enter into a loop where the List visualizations update each other multiple times. Sometimes this loop is endless. To work around this issue, you can break the endless loop by disabling the Auto Apply Data setting and removing the list visualizations or changing the visualization type.

  • If you added the List visualization from the Finger Pane's Visualizations tab, then you can’t deselect the items in the List visualization. To work around this issue, disable the Use as Filter setting for the List visualization added from the Finger Pane’s Visualization tab, and then you can deselect items in the visualization’s choice list.

  • Cross-visualization marking doesn't correctly mark items in the List visualization. This issue has no workaround.

Data Blending Auto Option Behavior Change

In previous releases of Data Visualization, when using columns from multiple sources, the default blending (Auto) often resulted in an “All Rows – All Rows” blending, whereas the more appropriate option was only one data source set to “All Rows” and the others set to “Matching Rows.”

In the current release of Data Visualization, when a visualization includes columns from multiple data sources and none of the columns are match columns, the data blending option of “Auto” results in only a single data source being set to “All Rows.”

Date Formats in CSV Files

If you add a CSV file as a data source and the CSV file contains dates, then they must be in the YYYY/MM/DD or YYYY-MM-DD format. If you use any other date format, then Data Visualization imports those date formats as a text column. If you try to change the data type to Date when importing the CSV, then you get an error.

Perform the following procedure to work around this problem.
  1. In Data Visualization, delete the incorrectly imported data set.
  2. Import the CSV, but leave the data type as Text.
  3. Create a project and add the data source.
  4. In the Project Editor, go to the Prepare canvas.
  5. Duplicate the column.
  6. Change the formula of the copied column to something like:
    CAST(SUBSTRING(Date,7,4) || '/' || SUBSTRING(Date,,4,2) || '/' || SUBSTRING(Date,,1,2) AS DATE)

    This example assumes the original format was DD/MM/YYYY.

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 Data Visualization treats the null values as string 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.
Error Importing XLSX Files Generated from Microsoft Access

Importing an XLSX file generated from Microsoft Access can sometimes fail. Data Visualization can interpret such XLSX files as header-less or even empty.

Perform the following procedure to work around this issue.
  1. Open the Access-outputted XLSX file in Microsoft Excel.
  2. Select a cell.
  3. Make and reverse a change. For example, select the top left cell, type an X, and then remove the X.
  4. Save the file.
You can now import this modified file successfully into Data Visualization.

Data Visualization Database Support Limitations

Data Visualization doesn’t fully support all of the databases listed in the Create Connection dialog. In some cases, Data Visualization doesn’t support all versions of a specific database.

Data Visualization provides limited support for databases marked with the Beta label.

In the Create New Connection dialog, some of the databases might be marked Beta. The Beta label indicates that the database has been tested, but isn’t fully supported. Data sources created from databases marked as Beta might contain undocumented limitations and you should use them as is.

Data Visualization Supported and Unsupported Data Types

This section contains information about the data types that Data Visualization supports and doesn’t support.

Unsupported Data Types

Some data types aren’t supported.

You'll get an error if your database data source contains data types not supported by Data Visualization.

Supported Base Data Types

When reading from a data source, Data Visualization attempts to map incoming data types to the supported data types.

For example, a database column that contains only date values is formatted as a DATE, a spreadsheet column that contains a mix of numerical and string values is formatted as a VARCHAR, and a data column that contains numerical data with fractional values uses DOUBLE or FLOAT.

In some cases Data Visualization can’t convert a source data type. To work around this data type issue, you can manually convert a data column to a supported type by entering SQL commands. In other cases, Data Visualization can't represent binary and complex data types such as BLOB, JSON, and XML.

Data Visualization supports the following base data types:




Supported Data Types by Database

Data Visualization supports the following data types.

Supported Oracle Data Types



  • CHAR

  • CLOB

  • DATE

  • DEC (p,s)

  • DECIMAL (p,s)




  • INT



  • NUMBER (p,s)

  • NUMERIC (p,s)



  • REAL


  • UROWID (size)






Issues with Predefined Application Roles

Oracle Data Visualization Cloud Service supports three application roles: Administrator, User, and Viewer.

Additional predefined application roles display in the Console but they are not currently used. Specifically, those named Data Loader, and NA.

Oracle Cloud Known Issues for Oracle Data Visualization Cloud Service


Copyright © 2015, 2019, Oracle and/or its affiliates. All rights reserved.

Documentation for Oracle Data Visualization Cloud Service users that describes known software issues and their workarounds for this release of Oracle Data Visualization Cloud Service.

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.