Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Email
Print Bookmark Alert me when this article is updated

Feedback

HOW TO: Validate an Entity using EDM Client of DSG Data Archive
Solution
Entity in Data Archive (DA) will be a collection of tables, which will be operated together. If any jobs are scheduled in Data Archive product, it would be on entity basis. All the archive job related actions would be performed on all table(s) part of the entity. i.e. At 'Copy to Destination' step of the job, data from all tables in the entity would be copied into provided target. Similarly at 'Delete from Source' step of the job, data residing in the entity tables at source would be deleted.

 

Generally Entity will have a parent table and its child tables grouped together. In such entities, if any jobs are scheduled on the entity, all the actions performed would be based on Parent table. For Instance, if any record from parent table needs to be deleted using archive job, then the referential data in corresponding child tables would also have to be deleted.

 

If operations like 'Update Retention Policy', 'Purge Expired Records', 'Technical View Data Discovery' etc. have to be performed based on tables relationship hierarchy using Data Archive, then it would be required to have all the referential constraints available in the entity. Hence as a pre-requisite before performing any operations on Entities with Relationship constraints in Data Archive, it is recommended to perform 'Validate Entity' operation.


'Validate Entity' option will help to make sure that all referential constraints are available for child tables in the entity and hence to confirm, if all the child tables can be reached from the Parent table of the Entity .

 

Pre-requisites

To perform 'Validate Entity' operation on an Entity, following are the pre-requisites:

  • Mark 'Parent Table' of the entity as 'Driving Table'.
  • Import Primary and Referential constraints of the tables into Entity as Entity Constraints
Validation will begin from the Driving Table and will check if the child tables are reachable from 'Driving Table' using available referential constraints. For more instructions on setting Driving Table for an Entity, refer KB 485423

 
For instructions on importing Primary and Referential constraints of tables into Entity, follow the steps mentioned in KB 485520

Validate Entity

For using 'Validate Entity' option in an Entity, execute the following steps:

 

  • Login to Data Archive Web UI.
  • Launch EDM through 'Accelerators > Enterprise Data Manager' menu in Web UI.
  • Once EDM is launched, open "View --> File Archive" tab.
  • Navigate to the Product Family Version (PFV), containing the entity, for which validation needs to be performed. 
  • Once navigated to the PFV, expand the Application Module under the PFV and select the required entity
  • Once the Entity is selected, ensure  that 'Driving Table' field on the right is set and has the correct Driving Table. For more instructions on setting Driving Table for an Entity, refer KB 485423​
Entity_Driving_Table_Validate.png  
  • After confirming that 'Driving Table' is set to correct table, Right click the entity and select 'Validate Entity' option.
 9_24_03_2016_validate_entity_option.png
 

On choosing 'Validate Entity' option, EDM would perform the task of verifying if all the relationship constraints are imported into Entity. Once the validation completes, result would be shown in a new pop up window.

 

 

If the referential constraints for all the child tables in the entity available within the entity and all the entity then 'Entity is valid' message would be displayed. 



8_24_03_2016_validate_entity_output.png 



If some referential constraints are missing for child tables in the entity or if there is (are) any orphan table(s) within the entity, then 'XML Constraints for the following list of tables are undefined ' will get displayed with the list of tables, for which constraints are not imported into Entity or not available itself.


25_03_16_validate_entity_invalid_entity_output.png 
 
 

To fix the issue and to make the 'Entity Valid', it would be required to import the referential constraints corresponding to the table(s) reported in the message or create new referential constraint(s) for those table(s), so that they would be reachable from Driving Table.


While using such invalid entities, without importing/creating referential constraint(s), in Data Discovery operations like 'Search Data Vault' , 'Invalid Entity definition: all entity tables are not reachable from driving table' error message will be displayed in Data Archive Web UI. Similarly while using the entity in 'Update Retention Policy' job, 'A filter cannot be applied because the entity has unrelated tables. Apply a retention policy based on a fixed date' message will occur. For more information on 'Invalid Entity' errors and to fix that issue, refer KB 158278

More Information
If 'Entity is Valid', relationships among the tables in the entity can be viewed in Graphical Tree Representation. For more information on viewing Relationship Hierarchy in Graphical Tree representation, see KB 485410

To perform search based on Entity Driving Table and to view the corresponding child tables data, Open 'Data Discovery > Search Data Vault', ( also known as 'Search File Archive' in earlier verions ) menu in Data Archive Web UI , if entity has been archived earlier into Informatica Data Vault and entity access role has been assigned to the Data Archive user. For more instructions on creating Entity Access Role and assigning to the Data Archive user, refer KB 147136
Reference
​​
Applies To
Product: Data Archive
Problem Type:
User Type:
Project Phase:
Product Version: Data Archive 5.3.5; Data Archive 6.1; Data Archive 6.1.1; Data Archive 6.2; Data Archive 6.3; Data Archive 6.4
Database:
Operating System: Linux; Windows
Other Software:
Attachments
Last Modified Date:3/29/2016 11:40 PMID:485485
People who viewed this also viewed

Feedback

Did this KB document help you?



What can we do to improve this information (2000 or fewer characters)