B Troubleshoot Visualization Issues

This topic describes common problems that you might encounter when working with visualizations and explains how to solve them.

When I import a workbook, I get an error stating that the workbook, data source, or connection already exists

When you’re trying to import a workbook, you might receive the following error message:

“There is already a workbook, data source or connection with the same name as something you’re trying to import. Do you want to continue the import and replace the existing content?”

This error message is displayed because one or more of the components exported with the workbook is already on your system. When a workbook is exported, the outputted .DVA file includes the workbook’s associated data sources and connection string. To resolve this error, you can either click OK to replace the components on your system, or you can click Cancel and go into your system and manually delete the components.

This error message is also displayed when the workbook you’re trying to import contains no data. When you export a workbook without data, the workbook’s and data sources’ metadata are included in the .DVA. To resolve this issue, you can click OK to replace the components on your system, or you can click Cancel and go into your system and manually delete the data source or connection that’s causing the error.

When I try to build a connection to Teradata, I get an error and the connection is not saved

When you’re trying to create a connection to Teradata, you might receive the following error message:

“Failed to save the connection. Cannot create a connection since there are some errors. Please fix them and try again.”

This error message is displayed because the version of Teradata that you're using is different from the version supported by Oracle Analytics Desktop. To resolve this issue, update the extdriver.paths configuration file. This configuration file is located here: C:\<your directory>\AppData\Local\OracleAnalyticsDesktop\extdrvier.paths. For example, C:\Users\jsmith\AppData\Local\OracleAnalyticsDesktop\extdriver.paths.

To update the extdriver.paths configuration file, remove the default Teradata version number and replace it with the Teradata version number that you're using. Make sure that you include \bin in the path. For example if you're using Teradata 14.10, then change C:\Program Files\Teradata\Client\15.10\bin to C:\Program Files\Teradata\Client\14.10\bin. See What if I’m using a Teradata version different that the one supported by Oracle Analytics Desktop?

I have issues when I try to refresh data for file-based data sources

Keep in mind the following requirements when you refresh data for Microsoft Excel, CSV, or TXT data sources:

  • To refresh an Excel file, ensure that the newer spreadsheet file contains a sheet with the same name as the original file you uploaded. If a sheet is missing, then you must fix the file to match the sheets in the original uploaded file.
  • If the Excel, CSV, or TXT file that you reload is missing some columns, then you’ll get an error stating that your data reload has failed. If this happens, then you must fix the file to match the columns in the original uploaded file.
  • If the Excel, CSV, or TXT file you used to create the data source was moved or deleted, then the connection path is crossed out in the Data Source dialog. You can reconnect the data source to its original source file, or connect it to a replacement file, by right-clicking the data source in the Display pane and in the Options menu select Reload Data. You can then browse for and select the file to load.
  • If you reloaded an Excel, CSV, or TXT file with new columns, then the new columns are marked as hidden and don’t display in the Data Panel for existing workbooks using the dataset. To unhide these columns, click the Hidden option.

Your Excel spreadsheets must have a specific structure. See About Files for Datasets.

I can’t refresh data from a MongoDB data source

The first time you connect to MongoDB, the MongoDB driver creates a cache file. If the MongoDB schema was renamed and you try to reload a MongoDB data source or use the data source in a workbook, then you might get an error or Oracle Analytics doesn’t respond.

To correct this error, you need to clear the MongoDB cache. To clear the cache, delete the contents of the following directory: C:\<your directory>\AppData\Local\Progress\DataDirect\MongoDB_Schema. For example, C:\Users\jsmith\AppData\Local\Progress\DataDirect\MongoDB_Schema

Where can I find files to help me diagnose a technical issue?

You can generate a diagnostic dump file to help resolve a specific issue. This file contains the following information:
  • Update information

  • Installer logs

  • Application component logs containing status information for Oracle Business Intelligence Presentation Server, Oracle Business Intelligence Server, and other critical components

  • Jetty logs

  • Data Security Standard (DSS) logs

  • Webcat metadata plugin logs

  • Derby logs

  • Server Administration Workbench (SAW) Server logs

  • Oracle Business Intelligence Presentation Server logs

  • Oracle Business Intelligence Server logs

  1. Open the command prompt and change the directory to the Oracle Analytics Desktop installation directory (for example, C:\Program Files\Oracle Analytics Desktop).
  2. Type diagnostic_dump.cmd and then provide a name for the .zip output file (for example, output.zip).
  3. Press Enter to execute the command.

    You can find the diagnostic output .zip file in your installation directory.

I need to find more information about a specific issue

The community forum is another great resource that you can use to find out more information about the problem you’re having.

You can find the forum here: Oracle Community Forum.