Known Issues for Oracle IoT Asset Monitoring Cloud Service
Learn about known Oracle IoT Asset Monitoring Cloud Service issues and their recommended workarounds.
Topics:
- HTTP Basic Authentication is Deprecated
- In-Place Duration Metric is Deprecated
- Deleting a Metric Does Not Delete Stored Metric Data
- Metrics, Predictions, Trends, and Anomalies Cannot Share a Common Name for the Same Asset Type
- Running a Test for Group Aggregated Metrics Returns Incorrect Group IDs
- Support for Internet Explorer is Deprecated
- On-Schedule Global Metrics Are Not Retrospectively Calculated for Imported Historical Data
- Role Changes for a User May Not Take Effect Immediately
- Importing a Previously Exported Organization from an Earlier Release Fails
-
False Positives May Appear When Using Metric Anomalies on Slow-Varying Data
HTTP Basic Authentication is Deprecated
IOT-112706: HTTP Basic Authentication is deprecated and will be removed in a future release (24.2.1).
In-Place Duration Metric is Deprecated
IOT-111829: The In Place Duration system metric is deprecated and will be removed in a future release. We recommend that you do not add this metric to your asset dashboards. You can create custom duration-based metrics per your needs.
Deleting a Metric Does Not Delete Stored Metric Data
IOT-104348: When you delete a metric or KPI, the past data corresponding to the stored metric values is not deleted automatically. The amount of stored metric data may be greater if you are using a high Data Life Span value for your custom metrics, or if you have set the data retention value to a non-default, high value for the metric that you are deleting.
Metrics, Predictions, Trends, and Anomalies Cannot Share a Common Name for the Same Asset Type
IOT-91161: You cannot create more than one analytics artifact using the same name for the same asset type. For instance, if you have created a metric for an asset type, you cannot create a prediction, trend, or anomaly with the same name as the metric name for the same asset type.
Running a Test for Group Aggregated Metrics Returns Incorrect Group IDs
IOT-87603: If you are creating a formula-based metric that is aggregated at the group level (On Schedule per Group
), and you try to test the metric in the metric editor using the Run Test option, the test results for the various groups are returned correctly, but the entity GUIDs of the groups are displayed incorrectly.
Support for Internet Explorer is Deprecated
Support for Microsoft Internet Explorer is deprecated.
Workaround: Microsoft Edge browser is supported.
On-Schedule Global Metrics Are Not Retrospectively Calculated for Imported Historical Data
IOT-75550: If you have imported historical data into your instance, and you have metrics of type On Schedule for Entity Type, then these metrics are not computed retrospectively for the imported historical data.
Role Changes for a User May Not Take Effect Immediately
IOT-65612: If you add a role to a user, the role privileges aren't effective immediately in the same session.
Workaround: Sign out from the session, and log in to the application again after 15 minutes, allowing the cache to expire. If this workaround doesn't help, then clear the browser cache and cookies, restart your browser, and log in again.
Importing a Previously Exported Organization from an Earlier Release Fails
IOT-65790: If you try to import a previously exported organization from an earlier release into an Oracle IoT Asset Monitoring Cloud Service OCI instance, the import fails.
Import of exported organizations from previous releases is not supported.
False Positives May Appear When Using Metric Anomalies on Slow-Varying Data
IOT-54678: When creating metric-based anomalies, you may see occasional false positives if the data is slow varying.
Oracle Cloud Known Issues for Oracle IoT Asset Monitoring Cloud Service, 23.4.1
E83166-39
October 2023
Copyright © 2017, 2023, Oracle and/or its affiliates.