My Oracle Support Banner

Extended Attributes Not Copied Over During Deployment for Non-Serialized Items (Doc ID 1092844.1)

Last updated on MARCH 29, 2019

Applies to:

Oracle Asset Tracking - Version 12.1.2 and later
Information in this document applies to any platform.

Symptoms


Comments
--------
   === ODM Issue Clarification ===

On :  12.1.2 version,

Find when user performs an Install of a non-serialized instance for a new location the Extended Attributes values do not get copied over to the new instance that is created.  

EXPECTED BEHAVIOR
-----------------------
Expect Extended Attributes to get copied over

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Query for any non-serialized product in OAT.
2. Perform a Deployment transaction of Install for the instance and for a new location.
3. When click on 'Apply', a new instance is created and the original instance expired.  
4. Review the new instance and the Extended Attributes are null.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Without the transaction history and extended attribute values, the instances are essentially 'non-traceable' and unidentifiable without the extended attribute values.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.