ODI Export / Import of Work Repository Does Not Migrate the Change of Value on SUBMIT_BICC_JOB Option Using Knowledge Module "LKM BICC to ADW External Table" (Doc ID 2994476.1)

Last updated on MARCH 26, 2024

Applies to:

Symptoms

In Oracle Data Integrator (ODI), on a mapping using knowledge module "LKM BICC to ADW External Table", after having changed the value for the option SUBMIT_BICC_JOB , the export  of  ODI work repository from source environment and import into target environment, does not migrate the changes of the option SUBMIT_BICC_JOB in the target environment.

For example:
1. Create sample mapping "MapA" in source work repository and import in Target environment.
   (Note: Both source and target have the same mapping with SUBMIT_BICC_JOB value being set to 'True' on "LKM BICC to ADW External Table")
2. In source environment, on mapping "MapA", On Physical Layer of the mapping, for the knowledge module "LKM BICC to ADW External Table", change the SUBMIT_BICC_JOB value to 'False'.
3. Export source work repository from Designer -> "Export the Work Repository".
4. Login target environment and import from Designer -> "Import the Work Repository".
         Navigate to Project -> Folder -> Mappings and observe that the mapping object "MapA", On Physical Layer of the mapping, for the knowledge module "LKM BICC to ADW External Table", SUBMIT_BICC_JOB value is still 'True'

Note: The above is not observed with Smart Export / Import of the mapping.

Changes

Cause