It appears to be related to a single record (with specified globalid).
Have you tried to examine that single record?
Thanks for your response !!!
Nope, not yet !!!
However I have not changed any thing in that existing mapping.
This error is coming in a particular environment with various previous versions of DA as well.
Those DA were successfully deployed in past and also getting deployed in other environment.
Not sure why in one environment/server only this issue is occuring.
Is it related to ODI version (22.214.171.124.0)? some patch required?? or some thing else??
This issue got fixed, sharing the solution with hope it may be useful for others in community with similar issue in future.
ODI had introduced GUID (Global Identifiers) from 12C. In ODI 12c, object uniqueness across multiple work repositories is guaranteed by assigning GUIDs to all objects.
I was importing DA on 12212 using DA imported from 12213.
I upgrdaed the ODI at target and issue resolved.
Thank you for the clarification.
It sounds similar to ESRI's databases. They have object id's which are unique within a table/layer/feature. But they also have globalid's which are unique across the entire database.