Different Harvested Versions from the Same Oracle Database Model Produces Different Lineage on Views in OEMM
Last updated on MAY 02, 2017
Applies to:Oracle Enterprise Metadata Management - Version 12.1.3 and later
Information in this document applies to any platform.
On Oracle Enterprise Metadata Management (OEMM) 220.127.116.11, the Trace Lineage on the same database view object produces different results when the trace Lineage is done from different imported versions, even when there are no changes on the database objects.
Consider the screenshot below.
The image shows the same Oracle model harvested multiple times. Under the Oracle Model, OEMM store a different harvest version for each successful harvest from the Oracle Database. On the left side of the screenshot it shows a the "Trace Lineage" based on the "2017-02-08 17:55:12" version. On the left side, the "Trace Lineage" based on the "2017-02-15 07:30:38" version. Assuming that there was no changes on the database objects, the linage produced should be the same, which is not occurring.
This issue can be observed when the same Oracle Model is harvested multiple times. OEMM will store a version for each successful harvest from the model.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms