Known Issues for Oracle IoT Production Monitoring Cloud Service
Learn about the issues you may encounter when using Oracle IoT Production Monitoring Cloud Service and how to workaround them.
Topics:
- HTTP Basic Authentication is Deprecated
- Incorrect Documentation Note on Connectors
- Deleting a Metric Does Not Delete Stored Metric Data
- Oracle IoT OPC UA Gateway Fails to Create or Update Machines
- Prefixes Added to Machine Type Sensor Attribute Names in Upgraded Instances
- Support for Internet Explorer is Deprecated
-
On-Schedule Global Metrics Are Not Retrospectively Calculated for Imported Historical Data
-
Blank Screen May Appear After Logging Out of the Application
-
Sample Analytics Cloud Project Contains Oracle IoT Asset Monitoring Cloud Service Artifacts
-
Predictions Based on Global Entity Type Metrics Are No Longer Supported
HTTP Basic Authentication is Deprecated
IOT-112706: HTTP Basic Authentication is deprecated and will be removed in a future release (24.2.1).
Incorrect Documentation Note on Connectors
Bug 35317642: A documentation note in the Using Oracle Internet of Things Production Monitoring Cloud Service Users' guide incorrectly states that Connectors are available for development or test purposes only.
This documentation note should be ignored. Connectors are available to be used in production environments.
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.
Oracle IoT OPC UA Gateway Fails to Create or Update Machines
IOT-78781: Oracle IoT OPC UA Gateway may fail to create or update machines. Data messages for existing machines are not affected.
This happens if you are using late-binding sensor attributes in Oracle IoT Production Monitoring Cloud Service. Late-binding sensor attributes let you define machine type attributes without associating them with device models. You can later associate the sensor attributes with device attributes for individual machines.
Workaround: Upgrade to the latest version of the Oracle IoT Gateway Software for OPC UA available at:
https://www.oracle.com/downloads/cloud/iot-gateway-downloads.html
Prefixes Added to Machine Type Sensor Attribute Names in Upgraded Instances
IOT-79749: Starting in 20.3.3, Oracle IoT Production Monitoring Cloud Service uses late-binding sensor attributes. The sensor attributes for your upgraded machine types are automatically renamed to include the associated device reference attribute name, as a prefix. This avoids potential name conflicts with other sensor attributes using other device references.
Late-binding sensor attributes let you define machine type attributes without associating them with device models. You can later associate the sensor attributes with device attributes for individual machines.
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 All Machines, then these metrics are not retrospectively computed 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.
Duplicate Routing Task Names May Be Present
IOT-62280: If you are using Oracle Fusion Manufacturing Cloud Service integration, then you may see duplicate routing task names in Oracle IoT Production Monitoring Cloud Service work orders.
Workaround: None.
Create a Trend Only after Activating the Sensor
IOT-58813: When creating a trend for a machine type attribute, make sure that the associated sensor has already started sending data. If you create a trend without any existing sensor data for the machine type, the training model fails with the following error: Not enough training data.
Workaround: Create the trend after the sensor data is activated.
Blank Screen May Appear After Logging Out of the Application
IOT-59107: After logging out of the Oracle IoT Production Monitoring Cloud Service application, a blank screen might appear in place of the Oracle Identity Cloud Service screen or log-in screen.
Workaround: Please reload the URL.
Some Factory Details Cannot Be Reset
- Description
- Address
- Manager Contact
Workaround: You can edit these fields to change their current values.
Sample Analytics Cloud Project Contains Oracle IoT Asset Monitoring Cloud Service Artifacts
IOT-57656: The sample Oracle Analytics Cloud project available under Integrations on the Settings page makes use of Oracle IoT Asset Monitoring Cloud Service artifacts.
Predictions Based on Global Entity Type Metrics Are No Longer Supported
IOT-56493: Starting in 18.4.1, predictions cannot be based on global metrics (KPIs) that are defined for entity types. If you have such predictions defined in 18.3.5, these predictions will not work.
Oracle Cloud Known Issues for Oracle IoT Production Monitoring Cloud Service, Release 23.4.1
E83167-35
October 2023
Copyright © 2017, 2023, Oracle and/or its affiliates.