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.

SLA Import Failed

Connector Import Failed

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

DM models in sync in terms of extensions.
The SLA Code and SLA Name should be the same for a specific definition, in both source and target environments.
Event type or attributes for a specific definition should be the same in both source and target environments.

Note:
When the Event Type is Both in source environment and Passthru or Transaction in Target environment, the import will fail.
If the same SLA definition is available in both source and target environment, then unpublish the SLA definition in the target environment, for successful import.
Event Name and Event code details should be the same in both source and target environments.
When a SLA definition is in Configured or Available state, in both source and target environment, then it will Configured state, after import.
If Exported SLA is in Draft/Ready for Registration state and SLA is not present in target system, after importing the SLA status is maintained.
If Exported SLA is in Registered/Configured/Available state and is not present in target system, it is set to Ready for Registration, after import. After registration, the header, line mapping and ledger assignment details from the source are also available for the target environment.
If Exported SLA is in Configured/Available state and if the same SLA definition is available in the target system, then
- Ledger Information is also updated
- Create or update the Edds and import the Header and Line Mappings, so that when a SLA is registered respective mappings are used.
  If a SLA is present on the importing system and is set to Registered/Configured status and the attributes are also matching, then update Ledger/Product/Mapping Information and retain status. If the attributes are not matching then Import will fail.
- When an exported SLA is in Configured/Available state, and any extended column is mapped in Header/Line mapping, and if this extended column is not available in the importing system then SLA is imported but the status is set to failed as the dependent mappings are not imported.

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 source.
Solution : Manually update the target date of such Issue with current/future date in the target environment.
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.

Segment Extension Validations

- If few of dimensions selected are already present in target setup, then during import,
  - If overwrite selected as Y, then dimensions which are not extended will be selected
  - If overwrite selected as N, then import fails.
- If all dimensions selected are already present in target setup, the error message - No dimensions to extend. They are extended already as a part of different Action, is displayed.
- If action with same export segment name already exists, and if overwrite selected as N, then the error message - Action with Same name already Present is displayed.
- If issue with same export segment name already exists and if overwrite selected as N,then the error message - Issue with Same name already Present is displayed.
- If action with same export segment name already exists and present under different issue and if overwrite selected as Y, then the error message- Action with Same name already Present in different Issue is displayed.
- If an issue with same export segment name already exists, and overwrite is selected as Y,
  - If the issue is under different category then, the error message - Issue with Same name already Present for different Category type is displayed.
  - If existing issue is closed, then error message,- Cannot update Issue with status closed, is displayed.
  - If the Issue is of same category then, it will update both the issue and action.
- If issue and action with same export segment name already exists, and overwrite selected as Y,
  - If issue is closed. Then, error- Cannot update Issue with status as closed
  - If the issue is doesn't belong to Catalog Extension, then, the error message - Issue with Same name already Present for different Category type, is displayed.
  - If Action type is not Segments, then the error message - Action Name already present for different type is displayed.
  - If status of Action is in Submitted/Published/Closed, then the error message - Cannot update Action which is in Submitted/Published/Closed state., is displayed.

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.