Known Issues in This Release

This section provides details for known issues in this release.

Oracle Utilities Operational Device Management Known Issues

The following are known issues in this version of Oracle Utilities Operational Device Management at the time of release:

Name	Reference Number	Description	Workaround (if applicable)
Operational Device Management Asset portal	38016903	The Asset portal used with Operational Device Management was replaced with the Operational Device Management Asset portal, secured by the Operational Device Management Asset Portal (W1ODMAST) application service. This application service was not automatically added to all user groups where access existed to the old Asset portal. To workaround the issue, please add the Operational Device Management Asset Portal (W1ODMAST) application service to any appropriate user groups until a fix can be provided to automatically grant this access.	To access the Operational Device Management Asset portal, add the Operational Device Management Asset Portal (W1ODMAST) application service to the appropriate user groups.

Oracle Utilities Application Framework Known Issues

The following are the known issues in this version of Oracle Utilities Application Framework which may affect Oracle Utilities Operational Device Management at the time of release:

Name	Reference Number	Description	Workaround (if applicable)
Cleanup Request Type search not working properly on Orphan Deletion Type	37628011	When editing an Orphan Deletion Type request type or when adding one after viewing an existing record, if you try to search for a Cleanup Request Type, it is defaulting the value to the Request Type in context. This is likely not the correct one.	You can work around this by finding the Cleanup Request Type code and copying it into your clipboard, and then pasting that value into the input field rather than trying to use the search. Alternatively, for an add scenario, you can leave the page and then use the menu to add the request type (without viewing an existing value first).
JSON Lines extract with concatenation is incorrectly creating '*.tmp' files.	37610732	JSON Lines is a newly supported extract format. The format does not produce a proper JSON Document, but rather a list of JSON documents. It means that the whole document does not need to be surrounded with any characters like {} or []. (Unlike the JSON format, where the final document is a proper JSON object or array). Because of this, when requesting concatenation for a multi-threaded process, the individual threads and the final concatenated file can all have the .jsnl extension. The code was released with the incorrect logic of using a .tmp extension for the individual threads. That logic was needed for the JSON format, but not the JSON Lines format. It will be fixed to use the *.jsnl extension for individual threads.	There is no work around needed, but implementations should not be planning any downstream logic that expects the individual thread files for JSON Lines output to have a "*.tmp" extension.
Unable to convert W3C schema to XML	37580078	The issue can occur while calling the toXML() method of com.splwg.base.messaging.impl.json.JSONToXMLJettisonConverter class while running batches.	As a workaround, copy the 'woodstox-core-6.4.0.jar' and 'stax2-api-4.2.1.jar' jars from weblogic installation directory (<wls-dir>/oracle_common/modules) and add them to standalone/lib and tpw/lib folder and restart the ThreadPoolWorker.
Drop ILM Partition Support For All MOs	37653601	Allow Drop Partition Approval Request Creation If Previous One Is Rejected	Approver user should not perform any rejections. If the Drop Partition Approval Request was created in error, have the Requester user cancel it.