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

ERROR: "XML Constraints for the following list of tables are undefined" on 'Validate Entity' operation in EDM client of DSG Data Archive
Problem Description

When performing 'Validate Entity' operation on an Entity using Enterprise Data Manager (EDM) client , operation fails with following message:


XML Constraints for the following list of tables are undefined:: [table_list] 


25_03_16_validate_entity_invalid_entity_output.png



In Data Archive versions before 6.2 HF2 following error would get displayed:

The following XML Entity constraints are not reachable through entity:::<META_TABLE_ID>

validate_entity.JPG



When such entities are used, in Data Discovery operations like 'Search Data Vault' also known as 'Search File Archive' through Data Archive Web UI, to get data from tables, in an archive folder of Informatica Data Vault (IDV), operation would report the following error:

Invalid Entity definition: all entity tables are not reachable from driving table


On performing 'Update Retention Policy' job using such invalid entity entity, to manage retention period on the tables, in an archive folder of Informatica Data Vault (IDV), operation would display the following message:

A filter cannot be applied because the entity has unrelated tables. Apply a retention policy based on a fixed date
Cause

This issue occurs when there is (are) no referential constraint(s), that uses the Primary Key constraint of Entity Driving Table,  in any of the child tables or if the referential constraints for the child tables, were not imported into existing entity. 


For resolving the issue, it would be required to import the referential constraints corresponding to the table(s) reported in the 'Validate Entity' operation output or create new referential constraint(s) for those table(s), so that they would be reachable from Driving Table.

Solution

To resolve this issue, if all the required referential constraints are already available for the tables in entity, then import them as 'Entity Constraints' through 'File Archive' tab. For instructions on importing Primary and Referential constraints of tables into Entity, follow the steps mentioned in KB 485520


If some referential constraints are not available for the entity tables or if issue is reported, even after importing available constraints as 'Entity Constraints', then execute the following steps on each of the tables reported in the 'Validate Entity' operation message ' XML Constraints for the following list of tables are undefined::  ' , for making the entity valid:
  1. Login to Data Archive WebUI.
  2. Open Accelerators > Enterprise Data Manager to launch EDM.
  3. Open View > Constraints in EDM and click the Constraints tab.
  4. Navigate to the entity, for which issue occurs during validation
  5. In the 'Driving Table' of the entity, create PRIMARY KEY (PK) constraint using one or more columns, if not available already.For instructions on setting Driving Table for an Entity, refer KB 485423
  6. Select a child table in the entity, which got listed in the 'XML Constraints for the following list of tables are undefined' message. If the message contains table id, instead of table name, execute the query mentioned in KB 482225 to get the list of Entity table names, along with its table id. If there are multiple child tables, repeat the steps 7-9 on each of the tables reported in the message.
  7. Navigate to Constraints tab for the table.
  8. Create REFERENTIAL CONSTRAINT using the PK constraint column(s) used in the driving table. edm_referential_constraint.png
  9. Once constraints are created, save the changes.
  10. Once constraints are created for all the tables reported in the message, Open View > File Archive in EDM and switch to the File Archive tab.
  11. Navigate to the entity, for which issue occurs.
  12. Right-click the entity and use the option Import Entity constraints.
  13. In the new window, newly created constraints and the one, which were not present already, will be visible. Select the relevant constraints and Import them.import_entity_constraints.png
  14. Then save the changes in EDM.
  15. Login to AMHOME schema, i.e. the database schema where Data Archive repository is installed.
  16. Run the following query to confirm whether referential constraints in the entity is formed correctly for all the tables, from the driving table:
    SELECT COUNT(*) FROM AM_META_CONSTRAINTS WHERE META_CONSTRAINT_TYPE = 'R' AND META_TABLE_NAME <> R_TABLE_NAME AND PRODUCT_FAMILY_VERSION_ID = ( SELECT PRODUCT_FAMILY_VERSION_ID FROM AM_META_TABLES WHERE META_TABLE_ID = (SELECT ENTITY_DRIVING_TABLE_ID FROM XA_ENTITIES WHERE ENTITY_ID='&ENTITY_ID') ) AND META_TABLE_ID IN (SELECT META_TABLE_ID FROM XA_ENTITY_TABLES WHERE ENTITY_ID='&ENTITY_ID') AND META_CONSTRAINT_ID IN (SELECT DISTINCT META_CONSTRAINT_ID FROM XA_ENTITY_CONSTRAINTS WHERE ENTITY_ID='&ENTITY_ID')
     
    For running the above query in databases, other than ORACLE, substitute "&ENTITY_ID" with the actual value. In Oracle, Entity ID would be requested at the time of execution. Use the below screenshot as a reference for getting entity id. 
    28_03_2016_get_edm_entity_id_screenshot_reference.png 
     
     
    If the above steps were followed correctly and if the entity is valid, count returned must be equal to the number of child tables in the entity.
  17. Once the count is confirmed as equal to the number of child tables in the entity, validate Entity using 'Validate Entity' option, available on 'Right clicking' the entity under 'File Archive Tab'. For more instructions on validating Entity, follow the steps mentioned in KB 485485

Once the Entity is shown as 'Valid', 'Search Data Vault' and 'Update Retention Policy' operations can be performed from Data Archive WebUI, using the same entity without any issues.
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

To define 'Retention Period' based on Entity Driving Table, Open 'Data Discovery > Manage Retention > Entities' 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
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:

Reference
Attachments
Last Modified Date:3/30/2016 1:10 AMID:158278
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)