ODI 12c Mapping Using "Component Context (Forced)" Generates the C$ Temporary Table on Incorrect Physical Schema (Doc ID 2824699.1)

Last updated on JUNE 07, 2023

Applies to:

Symptoms

An Oracle Data Integrator (ODi) 12c Mapping having the target Datastore "Component Context (Forced)" Logical design option set to a value other than <Execution Context>, uses incorrect Physical Schema during the loading (LKM) phase.

If the source Datastore is on FILE technology, and the target Datastore on some database, the following error is received while deleting / creating the C$ table:

To replicate the behavior:

1. Create a Mapping that has two source Datastores: one FILE, and one Oracle.
   
   Set the target to a Datastore in same Model as the source Oracle Datastore.
   
   Set a Filter on the Oracle source Datstore, and a Join between the two Dataastores.
   
   Set the knowledge modules to be used:
      LKM File to SQL, and
      IKM SQL Control Append
     
2. Leave the "Component Context (Forced)" of the target Datastore to its default value (which is <Execution Context>).
   
   Execute the Mapping, and observe the C$ created on the target (Oracle) Working schema, using <DB SCHEMA>.C$ name / syntax.
   
   This is correct / desired behavior.
      
3. Edit the Mapping, and change the "Component Context (Forced)" of the target Datastore to "Global" (or another Context where the involved Physical Schemas / Logical Schemas have been mapped).
   
   Execute the Mapping, and observe the C$ created on the source ( FILE ) Working schema, using <FILE PATH>.C$ name / syntax.
   
   This is incorrect. The same works just fine in ODI 11g

Changes

Cause