Oracle Cloud Known Issues for Oracle Analytics Cloud E81762-11 February 2018 Known Issues Learn about the issues you may encounter when using Oracle Analytics Cloud and how to work around them. Topics: Documentation Accessibility Supported Browsers Known Patching Issues Data Visualization General Issues and Workarounds Known Essbase Issues Restrictions on Working with Analyses and Dashboards Using Data Sync V2.4 Known Pixel-Perfect Reporting Issues Oracle Business Intelligence Mobile Issues and Workarounds Ignore the BI Mobile App Designer Option on the Administration Page 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 customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/ lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired. 1
Supported Browsers Here are the minimum requirements for web browsers that Oracle Analytics Cloud supports. Web Browser Microsoft Internet Explorer Microsoft Edge Google Chrome Mozilla Firefox Apple Safari Version 11 and later 38 and later 54 and later 45 and later 10 and later Known Patching Issues Learn about the issues you may encounter when patching Analytics Cloud and how to work around them. Topics: Error When You Attempt to Patch Your Service Backup Fails When You Attempt to Patch Your Service Error When You Attempt to Patch Your Service You must wait 24 hours after a patch is released before applying a patch. If you apply a patch too soon, patching fails with this message: ERROR: INFO:Persisting version file Wait 24 hours after the patch is released, and apply the patch again. Backup Fails When You Attempt to Patch Your Service Your system is automatically backed up whenever you apply a patch. Sometimes, even though patch precheck tests pass, patching doesn't complete properly because your system doesn't have enough resources to perform the backup step. If this happens to you, the message ERROR:Failed to backup pod is displayed and your service might become unresponsive. 1. If your service isn t responding, restart your service. See Starting, Stopping and Restarting Services. 2. Scale up your service so you have enough resources to back up and patch your service. See Scaling Services Up and Down. 2
Data Visualization General Issues and Workarounds Some features and functions of Data Visualization don t work as expected. Topics: Known Issues with Essbase Database Connections and Data Sources Data Blending Auto Option Behavior Change Null Values in XLSX File Set to String Error Importing a Project Error Importing XLSX Files Generated from Microsoft Access Error Creating a Data Set from a Microsoft Access Database Containing Spaces Bidirectional Languages Aren't Supported Error Message About Invalid or Missing Data Model When Editing a Data Flow Unable to Restore Backup After Rollback to Release 17.4.1 Known Issues with Essbase Database Connections and Data Sources The Essbase database connection type and Essbase data sources have a number of known issues. Searching for a specific column within an Essbase data source displays a "No Matches Found" message. Data Visualization displays an "Error Loading Data" message when you click an Essbase data source column from the BI Ask search results. The Advanced Analytics functions don't work for Essbase data sources. Loading an Essbase data source that fetches its metadata and outline from a cube on a remote server can take a long time. It can seem like the Data Visualization s user interface isn't responding, and it might take several minutes to display the cube that you want to use to create a visualization. If you create an Essbase connection and provide invalid login information, Data Visualization incorrectly displays the 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 Essbase connection, you can choose the Require users to enter their own username and password authentication option, but Data Visualization doesn t activate this behavior and instead authenticates all users with the user name and password that you specified. 3
If you change the application or cube an Essbase data source is using, the changes in the data aren't reflected in any data visualization projects that use the data source. When you try to perform interactions such as adding filters on a measure, you ll see the message: "Error: Input MDX query expression is too large to process, consider rewriting the query". This is because a size limitation exists for some interactions. 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. Essbase data sources don t work in data flows. When working in a data visualization project, you can t use match columns to join an Essbase data source to any other data source included in the project. When you import an 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. 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. 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 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. Error Importing a Project When you import a project, you might see an error message that states that something went wrong and you can't import the.dva file. This message is displayed for various reasons including: A file in the archive is larger than the maximum upload size (100 MB). One or more data sources use a connection with the same name as a connection you re trying to import. Delete these data sources. Incompatible Data Visualization versions. 4
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 headerless 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. Error Creating a Data Set from a Microsoft Access Database Containing Spaces If you're creating a data set from a Microsoft Access database and the database contains schema, table, or column names with spaces (for example, Asset Category rather than AssetCategory), then you get an error and the creation of the data source fails. Perform the following procedure to work around this issue. 1. Open the database in Microsoft Access. 2. Remove the offending spaces. 3. Save the database. 4. Build the data source again. Bidirectional Languages Aren't Supported Data Visualization doesn t support bi-directional languages, such as Arabic and Hebrew. This issue has no workaround. Error Message About Invalid or Missing Data Model When Editing a Data Flow You might see an error message that the data model is invalid or missing while editing a data flow in Oracle Analytics Cloud. You might see this error in this situation: 5
1. You create a data flow with the Apply Model step in Oracle Data Visualization Desktop. 2. You import that data flow into Oracle Analytics Cloud using a DVA file. 3. You edit the data flow in Oracle Analytics Cloud. Even though an error message is displayed in the data flow, the imported machine learning model is still valid and can continue to be used. To work around this issue, navigate to the Apply Model step, reselect the same model by clicking the model name, and save the data flow in Oracle Analytics Cloud. Unable to Restore Backup After Rollback to Release 17.4.1 In the current release, you can roll back to use Release 17.4.1. If you rollback, then try to restore a backup for 17.4.1, the backup fails. To work around this issue, don't roll back and try to restore to Release 17.4.1. Known Essbase Issues Some Essbase features and functions don t work as expected in Oracle Analytics Cloud. Topics: Multiple Sheets for One Dimension Aren t Supported in Cube Designer Wizard Can t Launch Scenarios Using the Chrome Browser Enabling a Cube for Scenario Management May Fail if You Haven t Built All Dimensions Can t Move a Member to Another Parent Security Certificate and Private Key File Ownership Changes After Restart Details from Drill Through Report Missing After Upgrade Partitions Aren t Migrated when You Import Applications with Scripts Changing Member Properties from Dynamic Calculation to Store Displays Error Message Some Cube Designer Features Aren t Supported or Exported Analyze Runs Slowly on Large Unstructured Sheets Converting a Middle-Generation Column to an Attribute Causes Incorrect Assignments Corrupted boot.properties File Export Doesn t Always Preserve Scenario Changes 6
Can't Import Data When Migrating Scenario-Enabled Applications Can t Launch Scenarios Using the Firefox Browser Multiple Sheets for One Dimension Aren t Supported in Cube Designer Wizard You can t create more than one sheet for a single dimension in Cube Designer Wizard. When you create a duplicate sheet in an application workbook with a different name, such as Dim.Scenario and Dim.Scenario2, and then select From Sheet, Cube Designer returns errors. First, you see the message "Error parsing Dimension sheets. Exception: An item with the same key has already been added". Then, when you click OK, you see an MS Net framework Unhandled Exception error. The workaround is to avoid creating multiple sheets for one dimension. Can t Launch Scenarios Using the Chrome Browser You can't launch scenarios using the Chrome browser. You can launch scenarios using Internet Explorer or Firefox. Instead of using a browser, open the spreadsheet manually in Microsoft Excel, and navigate to the correct sandbox. Enabling a Cube for Scenario Management May Fail if You Haven t Built All Dimensions If you enable a cube for scenario management before you build all dimensions, you might see an error message similar to: CELLPROPERTIES NOT SLOWEST MOVING DENSE DIM ERROR. You should build all dimensions before enabling the cube for scenario management to preserve the required dimension order for scenario-enabled cubes. 1. Create all dimensions (dense and sparse). 2. Enable the cube for scenario management. 3. Load data into the application. Can t Move a Member to Another Parent You can t use the dimension build setting "allow moves" to move a member to another parent, regardless of the uniqueness that s defined at the generation level. Security Certificate and Private Key File Ownership Changes After Restart 7
After you restart the Oracle Analytics Cloud service, you'll notice that the ownership of these security certificate and private key files changes to the root: /bi/data/httpd/security/private/apache.key /bi/data/httpd/security/certs/apache.crt To work around this issue, log in at the root and edit the following file using an editor such as vi: vi /etc/init.d/essbase Add the following lines after line number 40: chown -R oracle:oracle /bi/data runuser -l oracle -c "/bi/data/httpd/proxy-ctl start " > /u01/data/autostart.log Details from Drill Through Report Missing After Upgrade After you upgrade Oracle Analytics Cloud - Essbase from Release 17.4.1 to 17.4.5, or from 17.4.5 to 18.1.3, you might notice that some content (such as selected report columns and data source details) isn't visible. This issue has no workaround. Partitions Aren t Migrated when You Import Applications with Scripts When you migrate applications from previous releases using the scripts that are included with the service, partitions aren t migrated. To work around this issue, re-create the partitions on the instance of the target data service. Partitions are migrated correctly when you export and import them within the current release. Changing Member Properties from Dynamic Calculation to Store Displays Error Message When you use Hierarchy Viewer to change the properties of a member from dynamic calculation to store, you see an error message. This issue has no workaround. Some Cube Designer Features Aren t Supported or Exported For application workbooks in Cube Designer, you can t use partitions, security filters, drill-through, and associations, and they re not exported to tabular data. Analyze Runs Slowly on Large Unstructured Sheets 8
In Cube Designer, when you run Transform Data on unstructured sheets whose size exceeds 300MB, the analyze process runs slowly. This issue has no workaround. Converting a Middle-Generation Column to an Attribute Causes Incorrect Assignments When you run Transform Data in Cube Designer on a hierarchy of levels, if you try to convert a second generation column to an attribute of the first column, then the generation below the converted generation (now the third generation) isn t assigned correctly. It isn't now under the first generation, even though the second generation is now an attribute. This issue has no workaround. Corrupted boot.properties File The boot.properties file could become corrupted if a user inserts service credentials while the RDBMS is down. You can correct the boot.properties file as follows: 1. Connect to the source instance using Secure Shell (SSH) client software. 2. Switch to the user root: $cd /sudo su 3. Stop the service session: $ /etc/init.d/essbase stop 4. Login at the root as user oracle: $ sudo su oracle 5. Execute boot.properties.jar: $ /u01/app/java/latest/bin/java -jar /bi/app/public/bin/bootproperties.jar 6. Restart the service in Oracle Analytics Cloud, My Services. Export Doesn t Always Preserve Scenario Changes If you apply scenario changes to the base after you export and re-import the cube, then some scenario changes might be lost. To work around this issue during migration, apply changes to the base, or discard the changes, before you export and re-import the cube. Can't Import Data When Migrating Scenario-Enabled Applications When migrating scenario-enabled applications from 12.2.1.1.108 to 12.2.1.1.109, you can t import the exported 12.2.1.1.108 data because of changes in file format for importing cell status dimension members. 9
To work around this issue, remove the cell status dimension members (EssValue, EssStatus, and EssTID) from the exported data. You can do this manually, or use a script such as sed or awk. This issue applies to application workbook, MaxL, and LCM exports. Can t Launch Scenarios Using the Firefox Browser Launching Smart View from the Scenarios page in the service fails on Firefox. To work around this issue, install the Oracle Smart View for Office Add-on: 1. Click the Firefox Tools menu, and select Add-ons. 2. In Extensions, locate Smart View for Office, and click Enable. Restrictions on Working with Analyses and Dashboards Some features are disabled for security reasons. On the Properties menu for sections, you might see a Condition option. On the Action Link Properties dialog, you might see a Conditionally option. These options aren t operative in this release. Using Data Sync V2.4 To load data using Data Sync, we recommend that you deploy Data Sync V2.4. If you deploy Data Sync V2.2 or V2.3, you must use the Oracle (Thin) connection type for the target connection. Known Pixel-Perfect Reporting Issues Some Pixel-Perfect Reporting features and functions don t work as expected in Oracle Analytics Cloud. Topics: Bar Charts Showing Time on the X-Axis Don t Display Axis Labels Correctly Bar Charts Showing Time on the X-Axis Don t Display Axis Labels Correctly 10
If a report using the BI 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: http://docs.oracle.com/cd/e52471_01/bi.1111/e52669/toc.htm Ignore the BI Mobile App Designer Option on the Administration Page Administrators should ignore the BI Mobile App Designer option on the Administration page. The Administration page includes an option for managing BI Mobile App Designer. This option was included on the page in error and isn't functional. This option will be removed in a future release. Oracle Cloud Known Issues for Oracle Analytics Cloud, E81762-11 Copyright 2017, 2018, Oracle and/or its affiliates. All rights reserved. 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. 11
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 thirdparty content, products, or services, except as set forth in an applicable agreement between you and Oracle. 12