Known Issues for Oracle IoT Production Monitoring Cloud Service
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.
Oracle IoT Production Monitoring Cloud Service supports the following the minimum requirements for web browsers:
|Microsoft Internet Explorer||11 and later|
|Google Chrome||29 and later|
|Mozilla Firefox||24 and later|
|Apple Safari||7 and later|
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.
Modifying Routing Task Names Created by the Simulator Leads to New Factory Creation Failure
- Routing tasks created by the simulator.
- Device references for a machine type.
- Device simulator.
- Device models used by the simulation model.
Workaround: You can modify the entities back to their original values, and the simulator should be able to create a new factory for the model.
Factory Creation Fails If You Have Duplicate Routing Task Names for a Product
IOT-62019: The routing task names must be unique for each product ID in the factory. Also the routing task names must be unique within the same routing.
Factory Creation Fails If You Have Unassociated Routing Tasks in the Simulated Factory Model
IOT-62069: Your factory simulation model must not have any routing tasks without assigned machines. If you create routing tasks without associated machines, you get an exception when trying to create a factory using the model.
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.
Re-Create Old Custom Code Metrics in 18.4.5
IOT-56700: The new ability to use dynamic data links in Oracle Internet of Things Cloud Service implies that the existing links in user-defined code are not backward compatible. You can now point to generic application objects, as opposed to primitive or complex application objects. Simplified APIs or methods let you access data from snapshots, sensors, core attributes, and metrics. See examples provided with the custom code scaffolding template that is generated when creating custom code metrics.
Python Custom Code Metrics/KPIs May Fail to Publish in 18.4.5
IOT-56700: Python custom code re-publish may fail in 18.4.5.
Some Factory Details Cannot Be Reset
- 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.
Rules Can Become Invalid if Associated Sensor Attribute Is Deleted
IOT-56782: Rule threshold predicates may contain sensor IDs and metric IDs. When a sensor attribute is deleted, the corresponding rules become invalid.
Metrics Computed Across Entities Cannot Be Used in Rules
IOT-46248: You can create computed metrics across entities, but you cannot use these as rule conditions. Rules currently do not support aggregated evaluation on an entity type.
Rules Cannot Be Based on Business Object Attributes Alone
IOT-47891: You can create a rule based on a regular entity attribute, such as state or factory. However, you must add at least one message, sensor, alert, or location condition for the rule to be successfully triggered.
Map View Factory Metrics May Count Factories Without Geolocation
IOT-47782: As the factories imported from Oracle Manufacturing Cloud do not have geolocations associated with them, you might see these factories included in the Factory Metrics ribbon after integrating with Oracle Manufacturing Cloud.
Workaround: Zoom in or out in the Map view to update the number of factories shown in the Factory Metrics ribbon.
Importing the Production Monitoring Application Fails
IOT-44598: If you export the Production Monitoring application from the Management Console in Oracle Internet of Things Cloud Service and then you import the exported file, it fails.
Deleting Device Models Isn’t Supported
IOT-44710: Don’t delete device models that you are using in Oracle Internet of Things Cloud Service. If you delete them, the deployment of the application may fail.
Oracle Cloud Known Issues for Oracle IoT Production Monitoring Cloud Service, Release 20.2.3
Copyright © 2017, 2020, Oracle and/or its affiliates.
This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial computer software" or “commercial computer software documentation” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, reproduction, duplication, release, display, disclosure, modification, preparation of derivative works, and/or adaptation of i) Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs), ii) Oracle computer documentation and/or iii) other Oracle data, is subject to the rights and limitations specified in the license contained in the applicable contract. The terms governing the U.S. Government’s use of Oracle cloud services are defined by the applicable contract for such services. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.
Intel and Intel Inside are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD, Epyc, and the AMD logo are trademarks or registered trademarks of Advanced Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information about content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services unless otherwise set forth in an applicable agreement between you and Oracle. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services, except as set forth in an applicable agreement between you and Oracle.