Custom Validation Check Install Fails If Target Column Is Updated With Different Name And Oracle Name
Last updated on MAY 07, 2018
Applies to:Oracle Health Sciences Data Management Workbench - Version 2.4.7 and later
Information in this document applies to any platform.
A Validation Check ran into a strange issue with few batches failing to install after performing required update due to metadata change.
After diligent research, found out that one column is failing to map during installation.
Another issue noticed is that the target table instance for many VCs do not match the custom program target table definition.
STEPS TO REPRODUCE
1. Create a new Work Area;
2. Go to "Study Configuration"/"Clincal Data Model";
3. Create an input clinical data model SRC1 fom LAB.mdd file;
4. Install model.
5. Load data into the LAB table.
6. Create a Custom Program for use with the Validation Check:
6.1 From LSH, go to DMW_DOMAIN > DMW_UTILS > Custom_AA3 > CustomWA1
6.2 Add a source Table Instance LAB. Add two additional columns:
6.3 Add a target Table Instance VC1 of type Reload with the following columns:
At LSH level, under DMW_DOMAIN > Cardiology > MY_WA > DME_23115172_DEV > DME_WA_23115603_DEV Work Area, PGM_23115623_DEV is 'Non Installable'.
The mappings status for VC1 target table is incomplete.
Under Mapping for VC1, AGE_MEDIA column mapping is incomplete.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms