1. Administration Guide
  2. Known Limitations for Oracle Analytics

Known Limitations for Oracle Analytics

General Limitations

  • Due to a BI server cache issue, when a business intelligence application in OTM is assigned to a user, it is not accessible in Analytics. To work around, go to Transportation Intelligence > Administration > Maintenance and Troubleshooting section and run Reload Files and Metadata. The Admin user should only have to run this only once to avoid this issue.

Oracle Analytics Cloud Limitations

  • Unable to embed Oracle Analytics Cloud page (Data Visualization, Analytics, and Business Intelligence Publisher) into Oracle Transportation Management workbench.
    As a workaround, do the following configuration in Oracle Identity Cloud Service (IDCS) to allow Workbench to embed Analytics and Data Visualization content:
    1. On Identity and Access Management (IAM), as an administrator:
    2. Navigate to the Security tab under Domains.
    3. Under Session Settings section, click Edit session settings.
    4. Enable Allow cross-origin resource sharing (CORS).
    5. Add the Oracle Analytics Cloud host domain in the Allowed CORS domain names field, and click Save Changes.
    Note: This alternative works for latest versions of browsers like Chrome, Edge, and Firefox. However, it is not compatible with Safari. Also, embedding Workbench doesn't work in browser incognito mode.
    Note: If a Workbench doesn't work in your browser, turn off cross site tracking your browser setting.
  • When adding a user via the User Manager page, the checkbox "OBIEE Non-SSO User" is applicable only for Oracle Analytics Server. To access Analytics or use Web Service in Oracle Analytics Cloud, a user should have the single sign-on privilege. This can be achieved by following these steps:
    1. Create a user in Oracle Transportation Manager > User Manager with the required Business Intelligence Roles assigned.
    2. From the User Manager page, execute the action Synchronize User. It should be executed to map the user to the Identity Cloud Service (IDCS) group. Set up Oracle Identity Cloud Service (IDCS) user synchronization. For more details, refer to the section Getting Started with Oracle Analytics Cloud > Configuring Oracle Analytics Cloud for Generating Reports in the Administration Guide.
    3. Use the IDCS username and password of this user created in the Web Service SOAP request.
  • Uploading an RTF file that is more than 30 MB in size is not supported.
  • In Oracle Analytics Cloud, the following report formats aren't supported while generating reports from Oracle Analytics Publisher and Oracle Transportation Management:
    • Excel (html): Web page
    • Excel (mhtml): Single File Web Page
    • Excel (.xls): Excel 97-2003 Workbook
    Any report in OTM or BI Publisher using these report formats will need to be updated to work.
  • In Oracle Analytics Cloud, custom Java scripts which are used for action link in ad hoc queries, are no longer provided. These scripts were used to navigate to Oracle Transportation Management from Analytics Reports. Due to this, default "browser invoke" scripts are not available for Oracle Analytics Cloud. Refer to the Oracle Analytics Cloud Action Links section to configure the actions.
  • Mail settings in Oracle Analytics Cloud are not configured for Analytics reports due to unavailability of API from Oracle Analytics Cloud. Hence, the user will not be able to send Analytics reports via email.
    Note: This works fine for Business Intelligence Publisher (BIP) reports as SMTP mail settings are configured for BIP.
  • BI Publisher report jobs are migrated from OAS to OAC but job history isn't migrated. Customer will not be able to see the history of report jobs which were run in OAS BI Publisher.
  • You must reconfigure Printer Configuration (User/password) in OAC BI Publisher. These configurations in OAS will not be migrated to OAC.

Oracle Analytics Server Limitations

  • OAS 5.9 : ANALYTICS DASHBOARD DOES NOT OPEN CORRECTLY WHEN ACCESSED FIRST TIME AFTER LOG IN - OSM: If you sign in to OTM as "user b" after logging out of OTM as "user a" without closing the browser after logging out, the first click on any Analytics dashboard menu link redirects to the default My Dashboard instead of selected dashboard. (Issue # 32767978)

    Workaround

    1st Option:

    Click the same dashboard link a second time to open the correct dashboard.

    2nd Option:

    Close the browser after logging out as "user a" before logging in as "user b".

  • MIGRATED OAS AGENTS ARE NOT WORKING: Agents are getting disabled after customers are migrated to a new version. Also, if the active OAS (Oracle Analytics Server) agents are moved/copied from one location to another in Catalog, the status of the copied agent are "Suspended". Trying to run that agent throws the following error: "Cannot run this job. The job is suspended." (Issue # 35477667)

    Workaround

    To make the agents active again, you have to save the agent again from UI. After saving, it will move to status "Not suspended", and it can be triggered or used for scheduling.