To use UOID or to use NAME...?

I've seen quite some people struggle with this, and in some cases people seem to get weird results from these export/import sessions if they use UOID...

Here is a little bit of what can happen and when to use UOID and when to use Name matching on MDL import.

I hear a lot of people doing the following to work on object design (typically mappings):

  1. Create a mapping, test it etc.
  2. Need to change that original mapping so we:
    1. Copy the mapping
    2. Modify the copy
    3. Test the copy
    4. Delete the original
    5. Rename the copy to the original
  3. Deploy as if it was the original
In OWB deployment for mappings kind of works, however you will probably see that the Control Center thinks this mapping is new... this is because it uses UOID to determine status... and because you created a new object (with the old name) the UOID is different. This is also the issue with MDL of course. If you export this and then import on UOID you get 2 originally named mappings (and probably an error) with different UOID... This is a mess...

So if you do the above, do use NAME matching at all time.

I would however say, do the following in your design to make this a lot simpler and more elegant within the tool:
  1. Create a mapping, test it etc.
  2. Need to change that original mapping so we:
    1. Take a snapshot of this mapping
    2. Modify the original (a new version)
    3. Test the original new version
  3. Deploy the original new version

First of all the control center will know this has been deployed so it will say "replace" as action... second you can use MDL to import using UOID mode. Now the advantages are:
  1. You can compare the snapshot with the new version and it will tell you all differences
  2. You can always restore the snapshot and you have a smaller list of mappings in your project (plus you don't rely on naming to identify current mappings)
  3. You can rename the mapping and OWB in both deployment and in import will understand you did a rename, not create a new object!
I know this is a little different from what most people are used to so you could change the original set of steps as well. But instead of modifying the copy, you always modify the original. Not as many benefits, but the UOID will still nicely work...

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

ETL, CDC, Real-Time DI and Data Quality for the Oracle Database from the inside.

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today