Skip Ribbon Commands
Skip to main content
Navigate Up
Sign In

Quick Launch

Average Rating:

facebook Twitter
Print Bookmark Alert me when this article is updated


HOW TO: Import Unique and Referential Constraints of entity tables as "Entity Constraints" using EDM Client of DSG Data Archive

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, all the actions performed would be based on the 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 would be required to import the primary and referential constraints of the entity tables using 'Import Entity Constraints' option in 'File Archive Tab'. Once the constraints are imported, 'Validate Entity' operation can be performed to make sure if all the constraints are available for tables within Entity.

Import Primary, Unique and Referential Constraints of Entity Tables as Entity Constraints

If the Entity is imported from some other Data Archive environment using 'Export/Import' operation and if the Entity constraints are not available in 'File Archive' tab of the entity, then execute the steps in KB 242680 to get the Entity constraints.
If the Entity is created in the same environment and if no Import Entity operations are performed in Data Archive environment, containing the Entity, then execute the following steps, for importing table constraints into Entity as Entity Constraints:
  • 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, into which table constraints have to be imported . 
  • Once navigated to the PFV, expand the Application Module under the PFV and select the required entity.
  • Once entity is selected, Right click the entity and select 'Import Entity Constraints' option.


  • On choosing 'Import Entity Constraints' option, a new pop-up window  would be opened and it would  display all the available Primary, Unique and Referential constraints for the tables in selected entity.


  • Select the required Unique, Primary and Referential constraints of Entity Tables. As a default action, all the displayed constraints can be selected for import.
  • Once the required constraints are selected, use 'Down' arrow to move to 'Selected' section.
  • After moving required constraints to 'Selected' section, click on 'Finish' button to complete 'Import Entity Constraints' operation.


  • Once the constraints gets imported successfully, Save the changes to Entity.
  • Once the changes are saved, switch to 'Entity Constraints' tab on the right
  • In the 'Entity Constraints' tab, all the 'Imported Entity Constraints' would be displayed.
Once the required constraints are confirmed to be imported, 'Validate Entity' operation can be performed to make sure, if all the constraints are available for tables within Entity. 'Validate Entity' option would be available on selecting the Entity and right-clicking it under 'File Archive' Tab. For more instructions on validating Entity, follow the steps mentioned in KB 485485
More Information
All the Entity development activities should be made in Data Archive 'Development' environment. i.e. importing metadata for new application (tables and views) , creation of new entities, importing entity constraints, adding/removing tables in the entity, adding/removing table constraints, etc..  Those activities should never be done in other environments like QA/Production, where mostly entities would have been imported from Development environment.


Once the Entity development activities are carried out in Dev environment, it should then be carried over to other required environment through 'Export/Import' operations.


If the 'Export/Import' operations are carried out in Enterprise Data Manager (EDM) of Data Archive along with Entity Development related activities ( like removing tables, importing metadata, adding tables to existing entity, adding constraints etc.. ), then it would lead to corruption of Data Archive repository database schema, also known by 'AMHOME' schema.

Applies To
Product: Data Archive
Problem Type:
User Type: Business Analyst
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
Operating System: Linux; Windows
Other Software:
Last Modified Date:3/31/2016 11:47 PMID:485520
People who viewed this also viewed


Did this KB document help you?

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