OAC
Known issues for 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 associations aren't captured or defined in OAC and ADW:- Compute - Network Security Groups (NSG)
- Compute - Route Tables
- Compute - Security Lists
- Workaround
- No workaround is available.