Trouble-shooting imports with InfoSphere Data Architect MetaBroker into InfoSphere Information Server

Technote (troubleshooting)


Problem(Abstract)

Model-related problems can cause imports from InfoSphere Data Architect to fail or to create duplicate objects. This can happen when the import file contains disconnected objects, invalid keys, duplicate relationships, or duplicate objects.

Symptom

If the model in the import file contains disconnected objects and invalid keys, and you import it by using the IBM InfoSphere Data Architect MetaBroker, the import fails.

If the model contains duplicates and your administrative policy is to allow duplicates, the duplicates are imported. Duplicates can cause problem when you use the metadata in suite tools.

Cause

InfoSphere Data Architect does not allow you to create disconnected objects or invalid keys. But if you import a logical or physical model from another source into InfoSphere Data Architect, InfoSphere Data Architect ignores the presence of disconnected objects and invalid keys and does not display them. When you later import the same model from InfoSphere Data Architect into InfoSphere Information Server, the disconnected objects and invalid keys are present in the import file.

InfoSphere Data Architect allows you to use duplicate names for objects and relationships in a model, but gives a warning when you do. If you ignore the warning and import the model, it results in import failure or duplicate assets in the metadata repository.


Resolving the problem

There is a separate resolution for each of the three types of problems.

DISCONNECTED OBJECTS

When you import disconnected objects by using the InfoSphere Data Architect MetaBroker, you get a message similar to the following message:

The following text from the message shows the type of error and the object that caused the error:

LowerBoundConstraintViolationException:LowerBoundConstraintViolationException
[CDIMR0466E] There must be an associated Entity with Attribute RX_PLAN_IDENTIFIER. :{1}

In this example, the error was a lower-bound constraint violation error, which means that the object does not meet the lower-bound requirements for a relationship. The object is the attribute RX_PLAN_IDENTIFIER, which does not have the required relationship to an entity.

To resolve the situation, do one or both of the following steps:

  • To fix the import file, locate the object in the import file and delete the section that contains it, then reimport the file.
    There might be multiple objects of the same name and type. You must find the one that is missing the required relationship. Disconnected objects appear as top-level objects in the import file. Normal objects are defined within the element of the container object, which is the missing object in this case.
    In this example, the import file defines the attribute as follows:

    <LogicalDataModel:Attribute xmi:id="_vQgStW9OEeCJmseJasJvdA" name="RX_PLAN_IDENTIFIER" description="…." label="RX_PLAN_ID" dataType="CHAR(12)" required="true" abbreviation="RX_PLAN_ID"/>

  • If you plan to reimport the file from InfoSphere Data Architect at any time, fix the reference in the original file that you imported into InfoSphere Data Architect. Then reimport the fixed file into InfoSphere Data Architect before you reimport into InfoSphere Information Server.

NOTE: When you delete an disconnected object from a file, also search for and delete any foreign keys that refer to the disconnected object. Otherwise, on reimport you will get invalid key messages, as described in the following section.

INVALID KEYS

When you attempt to import invalid keys by using the InfoSphere Data Architect MetaBroker, you get a message similar to the following message:

The following text from the message shows the problem and where to locate it in the file:

[CDIMR0460E] Failed to load the model:Unresolved reference '_RwisEJfPEeC0FbNdYPSKWA'. (file:/C:/Windows/TEMP/mif_25606588332231269303-2%20RX%20AETNA%20INTEGRATOR%20-%20modified.ldm, 4980, 183).

The message shows the there was an unresolved reference, which is a reference to an invalid object or to an object that does not exist in the import file. In this example, the number 4980 is the line number where the error is located in the import file.

To resolve the situation, do one or both of the following steps:

  • Use the line number to find the error in the import file, and then correct the model in the original file that you imported into InfoSphere Data Architect. Then reimport the fixed file into InfoSphere Data Architect before you reimport into InfoSphere Information Server.
  • If you do not plan to reimport the file from InfoSphere Data Architect, you can fix the error in the import file by specifying a valid object for the unresolved reference and then reimporting by using the IBM InfoSphere Data Architect MetaBroker. However, fixing the file requires an understanding of the syntax of the InfoSphere Data Architect LDM and DBM files.

DUPLICATE RELATIONSHIPS AND DUPLICATE OBJECTS

InfoSphere Data Architect does not enforce unique names when you name objects. You get a warning if you use duplicate names. For example, the sample model below, created in InfoSphere Data Architect, has two entities named "Person", two attributes named "name" and two relationships named "buys".


When you import the model into InfoSphere Information Server the import fails, unless your administrative settings in InfoSphere Metadata Asset Manager allow duplicates. If you allow duplicates, however, duplicates are created that do not reflect the intention of the model. For example, three "Person" entities will be created, because the name attribute is part of the identity of an entity, and thus, two entities will be created for the entity that has two name attributes.

At version 8.7 of InfoSphere Information Server, logical model imports are subject to the following identity rules:

  • Entities must be unique within the same model.
  • Attributes must be unique within the same entity.
  • Relationships must be unique in the context of the child entity, which is also known as the owner entity. Two relationships that have the same name are treated as duplicates if they have the same child entity, regardless of the parent entity.
    In the sample model, the two relationships named "buys" will be seen as duplicates because Person is the child entity for both. If you change the the child entity for the first relationship to Car, the two relationships will have different identities and will not be seen as duplicates when you import them.

NOTE: In version 9.1 of InfoSphere Information Server, the restriction on relationships is relaxed by including the parent entity in the context. Two relationships may have the same name if at least one of the associated entities, parent or child, is different. In the sample model, although the two relationships have the same child entity, Person, they are not considered duplicates in version 9.1 because they have different parent entities.

To resolve the situation, take the following steps:
  1. In InfoSphere Data Architect, ensure that entities are unique within the model to be imported, and that attributes are unique within the same entity.
  2. If you are using version 8.7 of InfoSphere Information Server, ensure that all relationships are unique in the context of the child entity.
  3. Recreate the file to be imported and import the file.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

InfoSphere Information Server
IBM InfoSphere Metadata Asset Manager

Software version:

8.7, 8.7.0.1

Operating system(s):

Windows

Reference #:

1625728

Modified date:

2013-02-21

Translate my page

Machine Translation

Content navigation