Comments on: OMBPlus – Create mapping with operators

By: Zsolt Numan

Zsolt Numan — Wed, 25 Jun 2008 12:27:41 +0000

Hi Fred
This blog is a big help for me.

I’v just started to deal with OMB and need exactly the kind of script you’v been
working on: retrieve all properties for each mapping
Could you share that with me?
It saved me a lot of time.

Thanks&Regards
Zsolt

By: Fred Haeckl

Fred Haeckl — Fri, 09 Mar 2007 20:38:54 +0000

I found the answer to my question looking at some other OMBRETRIEVE examples. As previously stated, I was using OMBRETRIEVE MAPPING ‘X’ GET OPERATORS which gave me all the operators. I found that you can specify what type of OPERATOR you are looking for (OMBRETRIEVE MAPPING ‘X’ GET TABLE OPERATORS) will only return the TABLE operators. OMBPLUS will return blank if there are none, w/o raising an error. So… based on the list of acceptable OPERATORS —
ADVANCED_QUEUE, AGGREGATOR, CONSTANT, CUBE, DATA_GENERATOR,DEDUPLICATOR, DIMENSION, EXPRESSION, EXTERNAL_PROCESS, EXTERNAL_TABLE, FILTER, FLAT_FILE, INPUT_PARAMETER, JOINER, KEY_LOOKUP,MATCHMERGE, MATERIALIZED_VIEW, NAME_AND_ADDRESS, OUTPUT_PARAMETER, PIVOT, POSTMAPPING_PROCESS, PREMAPPING_PROCESS,
SEQUENCE, SET_OPERATION, SORTER, SPLITTER, TABLE, TRANSFORMATION,UNPIVOT, VIEW.
I can create a loop of each operator type, then another loop for each property of each operator and retrieve all my properties for each mapping.

Thanks – Fred

By: Fred Haeckl

Fred Haeckl — Thu, 08 Mar 2007 17:11:43 +0000

I’m trying to create a script that lists the values of each property for each operator. The code above for flat file is a great start, and for each operator type, I can get this list of properties. The problem I’m having now is that OMBRETRIEVE MAPPING ‘X’ GET OPERATORS tells me the name of the operator, but not the type. Is there a OPERATOR property that tells me what type of operator it is? If I try to pull a property such as ‘RECORD_TYPE_START_POSITION’ for a TABLE OPERATOR, I receive an error.

Any suggestions?

Thanks – Fred

By: Fred Haeckl

Fred Haeckl — Sat, 16 Dec 2006 18:37:35 +0000

Thanks for the response. I have the documentation, but that’s just it. The start_position is not even mentioned in the documentation for flat_files.
The way I found the correct property name was through the OWB UI.
Thanks again – Fred

By: Ilona Tielke

Ilona Tielke — Fri, 08 Dec 2006 10:46:50 +0000

Fred, Unfortunatly, there is no option to get a list op Properties in OMBPLus. So, you'll need to keep using the doc's on OMBPlus. Depending on your OWB version, the code of OMBplus could be slidely different. For START_POSITION, which you were looking for, it is the same in OWB 10G R1 an OWB 10G R2. I created some kind of summarize script which shows the different properties of a Flat_file. The script can be made more dynamic by using prompt to ask for a specific FLAT_FILE name but I leave that to you. What is does is that you first need to create a list with property names which you have to lookup first in the documentation. But then after placing those into your script you have a summary of all properties. See below script for an example.

set ff_prop_list { DATA_FILE_NAME IS_DELIMITED CHARACTERSET RECORD_DELIMITER RECORD_LENGTH RECORD_TYPE_COLUMN_NUMBER RECORD_TYPE_START_POSITION RECORD_TYPE_END_POSITION NUMBER_OF_RECORDS_TO_SKIP FIELD_DELIMITER FIELD_LEFT_ENCLOSURE NUMBER_OF_PHYSICAL_RECORDS_PER_LOGICAL CONTINUE_IF_ENDS_WITH CONTINUE_IF_STARTS_WITH }

set record_prop_list { RECORD_TYPE_VALUE }

set field_prop_list { DATATYPE LENGTH PRECISION SCALE START_POSITION SQL_DATATYPE SQL_LENGTH SQL_PRECISION SQL_SCALE MASK NULL_IF DEFAULT_IF }

foreach ff_prop $ff_prop_list {
 set v_result  [ OMBRETRIEVE FLAT_FILE 'T999_KODE_DEF_TXT' GET PROPERTIES($ff_prop) ];
 puts -nonewline "Flat File property: $ff_prop is: $v_result \n" 
}


foreach record_prop $record_prop_list {
 set v_result  [ OMBRETRIEVE FLAT_FILE 'T999_KODE_DEF_TXT' RECORD 'T999_KODE_DEF_TXT' GET PROPERTIES($record_prop) ];
 puts -nonewline "Record property: $record_prop is: $v_result \n" 
}

set field_list [ OMBRETRIEVE FLAT_FILE 'T999_KODE_DEF_TXT' RECORD 'T999_KODE_DEF_TXT' GET FIELDS ]

foreach field $field_list {
puts "\n==== Field Properties of FIELD: $field ==== \n"
foreach field_prop $field_prop_list {
 set v_result  [ OMBRETRIEVE FLAT_FILE 'T999_KODE_DEF_TXT' RECORD 'T999_KODE_DEF_TXT' FIELD '$field' GET PROPERTIES($field_prop) ];
 puts -nonewline "Field property: $field_prop is: $v_result \n" 
}
}

Regards, Ilona

By: Fred Haeckl

Fred Haeckl — Fri, 08 Dec 2006 04:55:33 +0000

Ilona and Sjoerd,

Great information. I’ve been working with OMBPlus for a while and would like to ask either one of you, do you have a good list of properties for each operator (or an object model for OMBPlus)?
OMBLIST gives you down to the ATTRIBUTE level, but then you have to GET PROPERTIES() by specific name. It doesn’t seem to be in a list that .tcl can take advantage through via foreach syntax

The documentation is a bit cryptic and I stumbled on a property in FLAT_FILE OPERATOR that is not referenced in the help – I think it was START_POS or something like that. I’m on a computer that doesn’t have OWB installed right now. I found it in the property window of OWB MAPPING, but when I looked in OMBPlus documentation, it was not there.

Any help would be appreciated.

Thanks, Fred

By: Ilona Tielke

Ilona Tielke — Thu, 20 Apr 2006 21:27:36 +0000

Hi Sjoerd,

Thanks for your update. In the meanwhile we enhanched the code for creating mappings by adding a preprocess mapping operator to them.

So, here’s the code to that needs to be added to the code above.

ADD PREMAPPING_PROCESS OPERATOR ‘PREM_TRUNCATE_TARGET’ \
SET PROPERTIES ( MAPPING_RUN_CONDITION, ROWBASED_ONLY ) \
VALUES ( ‘ON SUCCESS’, 1 ) \
BOUND TO PROCEDURE ‘TRUNCATE_TARGET_TABLES’

Regards, Ilona

By: Sjoerd Evers

Sjoerd Evers — Thu, 20 Apr 2006 17:28:43 +0000

Nice script that you made in OMBplus. I would like to fill you in on some extra information that you probably already know, but for the other readers of this weblog. For instance the targettables you making with :

ADD TABLE OPERATOR ‘A_$sourceTableName\_CUM’ \
BOUND TO TABLE ‘../$sourcemodule/$sourceTableName\_CUM’ \

, could be expended with setting the properties for the loading type, i.e.

ADD TABLE OPERATOR ‘U_$sourceTableName’ \
SET PROPERTIES ( LOADING_TYPE ) VALUES ( ‘INSERT’ )
BOUND TO TABLE ‘$sourceTableName’ \

would be the default set to insert but if you would like to change it, this can be set to ‘UPDATE’ (not that you want it in this case. Other loadingtype values are possible but it’s tricky because they arent all supported. I dont have OMB running here atm but i do remember i have had problems with setting ‘UPDATE/INSERT’ via OMBplus. This isn’t an issue with this delta mapping because you would like to have all values set to ‘INSERT’, but does get more interesting in building skeleton mapping for the ‘DWH’layer where ‘UPDATE/INSERT’ are no uncommon values.

If you would like to fit in some more text over where it says ‘mapping comment’, its possible to put down there a local variable and declare it before the actual OMBCREATE:

OMBCREATE MAPPING ‘E_$sourceTableName’ SET PROPERTIES (DESCRIPTION ) \
VALUES (‘mapping comment’) \

would become before OMBCREATE:

set nameit “————————————————————–\n”
append nameit ” Mapping : E_$sourceTableName \n”
append nameit ” Developer : by script \n”
append nameit “-Version—————————————————–\n”
append nameit ” Date Who Why\n”
append nameit “-End———————————————————\n”

(then:)

OMBCREATE MAPPING ‘E_$sourceTableName’ SET PROPERTIES (DESCRIPTION ) \
VALUES (‘$nameit’) \