1. Migrating and Upgrading to Oracle Analytics Server
  2. Troubleshooting Migrated Oracle Analytics Server

D Troubleshooting Migrated Oracle Analytics Server

This appendix provides procedures to troubleshoot a migrated Oracle Analytics Server system.

  • Configuration Failure with TRANSFORMBAREXCEPTION
    The Oracle Analytics Server configuration might fail with a TRANSFORMBAREEXCEPTION error, if any objects in the catalog are older than Release 11.1.1.9. You can confirm the need to update the catalog items by viewing the metrics in Oracle Enterprise Manager Fusion Middleware Control. In the Catalog folder, find a metric called Reads Needing Upgrade with the description "The number of objects read that required upgrading." If the number is large, then you can resolve this issue by updating objects in the catalog using the Administration page in Presentation Services.
  • Multiple Y-Axis Highcharts Graphs Not Displayed
    Multiple Y-axis highchart graphs likely don't render after migration, because the Oracle Analytics Server instance does not include the required JavaScript (.js) files. You must copy the files to the instance manually.
  • Setting the Evaluate Parameter in the NQSConfig.INI File
    The EVALUATE function in your analyses is not enabled by default in Logical SQL queries because it exposes the database to SQL injection attacks. If you encounter any error while generating any views after migrating to Oracle Analytics Server, then you must set the value of the EVALUATE_SUPPORT_LEVEL parameter appropriately in the NQSConfig.INI file.
  • Analysis Query Failure
    After in-place upgrade, analysis queries fail with [nQSError: 60009] error if the database query time in seconds exceeds the value set for the DEFAULT_DB_MAX_EXEC_TIME parameter in the BI_DOMAIN/config/fmwconfig/biconfig/OBIS/NQSConfig.INI file.
  • Error: java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment
    If you have set the value of the DISPLAY variable manually or the system has manipulated it automatically, you can encounter the java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment error. In case you change the value of the DISPLAY variable to a Windows-client system IP, to run the 64-bit Linux installer through a Windows client, reset it to its original value after the installation is complete. If you generate an analysis that contains graphs without resetting the value of the DISPLAY variable, you can get this error.
  • Verifying File Data Sources in Publisher
    While generating reports, if you encounter an error stating oracle.xdo.XDOException: File does not exist or is not readable:..., you might not have copied the supporting XML files to Oracle Analytics Server. To solve this issue, manually validate that the path for each data source points to the appropriate directory on Oracle Analytics Server.
  • Error on checkSoftLimit Failed
    You see the [nQSError: 43119] Query Failed: [nQSError: 46168] Operation RawFile::checkSoftLimit failed, it'll exceed the current limitation. 1073758528 error if the query requires more temporary space to complete than the BI Administrator has allocated.
  • Replacing Custom Links in the Global Header
    After migrating to Oracle Analytics Server, you might notice that links that you had added to the global header in the Oracle Business Intelligence instance are no longer available. The links are missing because the customlinks.xml file isn't migrated from the Oracle Business Intelligence to the Oracle Analytics Server instance. You must manually copy the file to the Oracle Analytics Server instance and enable the Custom Links functionality in the instanceconfig.xml file.
  • Migrating WebLogic Users
    After migrating from 11g to Oracle Analytics Server, you must manually migrate the WebLogic users in to your Oracle Analytics Server domain. You can do this by exporting the security data from a security realm and importing it in to another security realm. Security data includes authentication, authorization, credential map, and role data.
  • View Display Error: Invalid Column Encountered in Orders Outstanding Report
    You might see a View Display Error message that states that an invalid column was encountered when loading the Orders Outstanding Report in Oracle Analytics Server. This error is displayed because the ID of the column that causes the error exists in the XML definition of the report, but not in the subject area table. You must manually edit the XML definition and remove the invalid column.
  • Managing Oracle BI Presentation Catalog
    Catalog objects are stored in database tables rather than the file system.
  • Exporting Oracle BI Analysis from Oracle BI EE 11.1.1.8.x or Earlier Releases to Excel Files
    Settings in the xdo.cfg configuration file specify the format for exporting analyses to Excel spreadsheets.