Oracle Analytics Cloud (OAC)

Known issues for Oracle Analytics Cloud (OAC) with Resource Analytics

OAC Provisioning fails when the IDCS domain selections home region doesn't match the Resource Analytics instance region

Details: Because of issues related to domain replication and the lack of cross-regional networking, you can't provision OAC with domains that weren't created or homed in the same region as the Resource Analytics instance was created.
Workaround: We're working on a resolution.

The latest data isn't shown in OAC

Details: The data shown on the OAC report, dashboard, or workbook isn't up-to-date. The most likely cause is because the OAC cache, which is sourced to display the report, has stale data.
Workaround: To update the stale data, select refresh data (the database icon). Up-to-date data is pulled from ADW.

Incomplete association of networking components with Compute instances in OAC and ADW

Details

The requirement is to retrieve comprehensive network information for any particular Compute instance. This includes not only the standard networking details (VNIC, subnet, or VCN), but also associations such as route tables and security lists linked to the Compute instance.

The relationships, Compute - VNIC - Subnet - VCN are established and retrievable, but the following association isn't captured or defined in OAC and ADW:

Compute - Security Lists

Thus, OAC and ADW can't provide a complete view of the network associations for the Compute instance.

Workaround

No workaround is available.

OAC shows as active before dashboards are provisioned

Details

An OAC instance might display as Active even though it's still updating with sample dashboards.

Because of OAC's caching, accessing the instance before all dashboards are fully seeded can result in missing dashboards.

Workaround

Wait ten minutes after OAC shows as Active before signing in.