My Oracle Support Banner

DMW 2.5 Transformation Ending with Warnings Because the CDR$SKEY Column is not Mapped From Source Table (Doc ID 2719826.1)

Last updated on OCTOBER 23, 2020

Applies to:

Oracle Health Sciences Data Management Workbench - Version 2.5.2 and later
Information in this document applies to any platform.

Goal

The purpose of this document is to explain the reason behind the Transformation logfile to end in Warnings which do not exist prior to DMW 2.5.

Customer have started seeing Warnings in transformation logfile which are all are due to the CDR$KEY lineage as seen below. This prevents all like tables using CDR$KEY to set transformation to “Warning” and not “Success”

Started Context Post processing :: 09-25-2020 19:53:51
Context doPostProcess Started: Target table: <TARGET_TABLE_NAME>
. Collect mapping data for context lineage.
. Started context lineage entries for INSERTED data records :: 25-SEP-2020 19:53:51

WARNING *** WARNING *** WARNING
Lineage tracing and discrepancy propagation is incomplete or unavailable for target table <TARGET_TABLE> because the CDR$SKEY column is not mapped from source table: <SOURCE_TABLE>
WARNING *** WARNING *** WARNING

. Started context lineage entries for UPDATED data records :: 25-SEP-2020 19:53:51

WARNING *** WARNING *** WARNING
Lineage tracing and discrepancy propagation is incomplete or unavailable for target table <TARGET_TABLE because the CDR$SKEY column is not mapped from source table: <SOURCE_TABLE>
WARNING *** WARNING *** WARNING
 

Solution

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
Goal
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.