Troubleshooting Object Migration

Custom DQ Import Failed

In case, the migration of Custom DQ definitions doesn't complete, verify the following points. Ensure to complete these requirements before proceeding with the custom DQ migration.

The referenced object not present in target.
Basic definition of custom DQ objects already present in the target are not in sync with that in source. Following basic properties for custom DQ objects should be in sync between source and target:
- Entity, Attribute Name and DQ Type for Custom DQ Rule.
- Base entity /Base group for Custom DQ Group
Custom DQ Objects already present in target are in Approved/Submitted state in target.

Connector Import Failed

When the connector import is not successful, ensure to verify the following details and complete the prerequisites.

The attributes in the entity used in the migrated connector (for both Extract and Insert connector), must be the same in source and target environments.
When a connector with the same name is already available in the target environment, the imported connector will overwrite based on the set overwrite option.
OOTB Extract connector is the only valid OOTB metadata during the import.
When a connector is migrated, all the underlying metadata of EDD and Parameters are also migrated.

Catalog Extension Import Failed

The Catalog extension import might fail due to the following validation checks, during import migration. Correct the error and retry the import.
- The referenced object not present in target
- The object is already present in the target, while creating a Object using Object migration import feature.
- The grain/BT/Dimension being imported is already used by another action in the target.
- The action Name is already present in target
- The issue associated to the action being imported is closed in the target.

Persistent Errors - Catalog Extensions

You cannot proceed with the catalog extension import, if you encounter one of the following scenarios:

Even if one of the objects are present in the target environment, for the imported change request, then the import will fail. It won't partially import the objects which are not present in the target.
During Fact Extension Migration, if in the source, the BT used in fact extension is referencing to a different dimension entity than the target.
During Create Dimension Migration, if another custom dimension exist in the target with different logical name but it has the same BT as Business key of the dimension being migrated.

Possible Reasons for “Issues And Action Details Is Not Found” Error During Catalog Extension /Custom DQ Import

If the target date of the issue associated to the action being imported is expired in the target.
Solution : Manually update the target date of such an issue with the current/future date in the target environment and try importing again.
If the issue associated to the action being imported is closed in the target.

CR Re-import Requests Are Failing Repeatedly for Catalog Extension/Custom DQ Import

If CR re-import requests are failing even after 4 to 6 hours of first import request of that CR and the following error is present in the log file: CR can not be reprocessed as import request is still ongoing for it, contact OFSAA customer support.

CR cannot be reprocessed as its objects are already used

If this error message is displayed in the logs during Catalog Extension/Custom DQ CR import, then created action is moved to Submitted/Approved/Published state.

Solution : Submit the action if it was returned and proceed with re-import.

Unable to Submit the Action because following Custom DQ Rules are not mapped to any DQ Group in the current Action

If the custom DQ import fails and the above error message is displayed, the mapped Group for the erroneous rules might have moved to a different action in the source while editing.

Solution : Migrate the CR consisting the custom DQ Group belonging to the erroneous rules listed in the logs.

Aborting the Import as the Data Quality Rule is in Approved/Submitted state

If this error message is displayed in the logs during Custom DQ CR import, then the Custom DQ Rule/Group being migrated is already present in the target environment but can not be overwritten as it is in Approved/Submitted state.

Solution : Move the Custom DQ Rule/Group to Returned state in target if it is in Submitted state or publish it if it is in Approved state.

Basic Validation has failed for Custom DQ Rule/Group

If this error message is displayed in the logs during Custom DQ CR import then, another Custom DQ Rule/Group present with the same name but with different basic properties, is already present.

Solution :

If Basic Validation has failed for Custom DQ Rule, create a new Custom DQ Rule and then map it to the appropriate group. Unmap the old rule with basic properties that are not matching between source and target and retry migration.
If Basic Validation has failed for Custom DQ Group, create a new Custom DQ Group with a different name and map all the appropriate rules and try migrating this new group instead.

Custom Object Dependency check failed for Custom DQ Rule/Filter: <Rule/Filter Name>. <Referencing Dimension Name> is not an eligible Reference Dimension or <Joining Attribute Name> is not an eligible joining attribute for <Base Entity Name>

If this error message is displayed in the logs during Custom DQ CR import, then for a Dimension Referencing Comparison Custom DQ Rule or in one of the Custom DQ Filter's dimension referencing condition, either Referenced dimension is not related to base entity or joining attribute is not an eligible joining attribute in the base entity for the referenced Dimension.

Solution : A dimension is related to the base entity only when that dimension's business key attribute is present in the base entity or it is sharing definition with an existing attribute of base entity, and such attribute of base entity (which is a business key of a dimension or sharing its definition with a business key of a dimension) is known as Joining Attribute for the Referenced Dimension. Ensure the referencing dimension and joining attribute are as per the above definition.