B Troubleshooting a Migrated Oracle BI Instance

This appendix provides procedures to troubleshoot a migrated BI instance from 11g to 12c.

Topics:

  • Configuration Failure with TRANSFORMBAREXCEPTION
    The 12c configuration might fail with a TRANSFORMBAREEXCEPTION error, if any objects in the catalog are older than Release 11.1.1.7. 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 BI 12c 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 BI 12c, then you must set the value of the EVALUATE_SUPPORT_LEVEL parameter appropriately in the 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 Oracle BI 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 the 12c system. To solve this issue, manually validate that the path for each data source points to the appropriate directory on the 12c system.