How to modify an EXTERNAL_TABLE and MAPPING using OMBplus

Question

I need to implement a QA--> Production migration technique using OMB+ scripting. We are using source safe for keeping the MDL files.
As we have insufficient resources both environments are in the same database as different schemas. Configuration is as below;
Source Schema: DWPROD_TST (test) and DWPROD (production)
Target Schema: DWEXTRACT_TST (test) and DWEXTRACT (production)
Source Flat File Module: DWEXTRACT_TST_INPUT (test) and DWEXTRACT_INPUT (production)
Target Flat File Module: DWEXTRACT_TST_OUTPUT (test) and DWEXTRACT_OUTPUT (production)
All schemas have their own locations and modules defined. Once a mapping is create in TST environment developers should check in the individual
mdl files for the object they used for development. From is point the strategy I have follow is like below as I haven't seen a similar scenario before.
I rename the mdl extensiton .zip. I unzip the file. I take the mdx file extracted and make a text based search/replace for all the test environment modules, locations... etc
replacing them with production environment names. Then I run the OMB+ script below in order to import and deploy this object. This technique works for table and flat file object
with slightly different OMB+ scripts. But I can not make it work for external tables and mappings and the reason that I can guess is the Configuration information of the Data File used
as source for external table and target for the mapping I have developed. I can import the MDX successfully but cant deploy it. When i rigt click the mapping or the external file in OWB GUI
and click on CONFIGURATION I can see that:
For the MAPPING : Flat File Operator/(OperatorName)/Target Data File Location is still pointing to TEST environment even tough I have replaced all the TEST environment information with PRODUCTION.
For the EXTERNAL_TABLE : Data File/(OperatorName)/Data File Location is still pointing to TEST environment even tough I have replaced all the TEST environment information with PRODUCTION.
Is there any way to modify these LOCATION information for a MAPPING and an EXTERNAL TABLE OMB+. I read though all OWB+ scripting Reference but it sucks or I am so dumb.
Or if you have an alternative solution for my problem I will be more then happy to read it.
OMB+ Script for EXTERNAL_TABLE
OMBCONNECT DWPROD/DWPROD@cakir:1521:orcl USE REPOSITORY 'OWBDB_SYS'
OMBIMPORT MDL_FILE 'C:\\tfs\\stage\\externaltables\\XTRCT_XTRNL_INPUT_FILE\\XTRCT_XTRNL_INPUT_FILE.mdx' USE UPDATE_MODE MATCH_BY NAMES OUTPUT LOG TO 'C:\\tfs\\stage\\externaltables\\XTRCT_XTRNL_INPUT_FILE\\XTRCT_XTRNL_INPUT_FILE.log'
OMBCC 'MY_PROJECT'
OMBCONNECT CONTROL_CENTER
OMBCOMMIT
OMBALTER LOCATION 'XTRCT_DWEXTRACT_LOC' SET PROPERTIES (PASSWORD) VALUES ('PASSWORD')
OMBALTER ORACLE_MODULE 'XTRCT_DWEXTRACT' ADD REFERENCE LOCATION 'XTRCT_DWEXTRACT_LOC' SET AS DEFAULT
OMBALTER ORACLE_MODULE 'XTRCT_DWEXTRACT' SET PROPERTIES (DB_LOCATION) VALUES ('XTRCT_DWEXTRACT_LOC')
OMBCOMMIT
OMBREGISTER LOCATION 'XTRCT_DWEXTRACT_LOC'
OMBCOMMIT
OMBREGISTER LOCATION 'DWEXTRACT_INPUT'
OMBCOMMIT
OMBCC 'XTRCT_DWEXTRACT'
OMBALTER EXTERNAL_TABLE 'XTRCT_XTRNL_INPUT_FILE' SET REFERENCE DEFAULT_LOCATION 'DWEXTRACT_INPUT'
OMBCOMMIT
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'TABLE_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('REPLACE') SET REFERENCE EXTERNAL_TABLE 'XTRCT_XTRNL_INPUT_FILE'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
OMBCOMMIT
OMBDISCONNECT
OMB+ Script for the mapping
OMBCONNECT DWPROD/DWPROD@cakir:1521:orcl USE REPOSITORY 'OWBDB_SYS'
OMBIMPORT MDL_FILE 'C:\\tfs\\stage\\mappings\\XTRCT_PROTOTYPE_XTRCTFILE_000\\XTRCT_PROTOTYPE_XTRCTFILE_000.mdx' USE UPDATE_MODE MATCH_BY NAMES OUTPUT LOG TO 'C:\\tfs\\stage\\mappings\\XTRCT_PROTOTYPE_XTRCTFILE_000\\XTRCT_PROTOTYPE_XTRCTFILE_000.log'
OMBCC 'MY_PROJECT'
OMBCONNECT CONTROL_CENTER
OMBCOMMIT
OMBALTER LOCATION 'XTRCT_DWEXTRACT_LOC' SET PROPERTIES (PASSWORD) VALUES ('PASSWORD')
OMBALTER ORACLE_MODULE 'XTRCT_DWEXTRACT' ADD REFERENCE LOCATION 'XTRCT_DWEXTRACT_LOC' SET AS DEFAULT
OMBALTER ORACLE_MODULE 'XTRCT_DWEXTRACT' SET PROPERTIES (DB_LOCATION) VALUES ('XTRCT_DWEXTRACT_LOC')
OMBCOMMIT
OMBALTER LOCATION 'XTRCT_DWPROD_LOC' SET PROPERTIES (PASSWORD) VALUES ('PASSWORD')
OMBALTER ORACLE_MODULE 'XTRCT_DWPROD' ADD REFERENCE LOCATION 'XTRCT_DWPROD_LOC' SET AS DEFAULT
OMBALTER ORACLE_MODULE 'XTRCT_DWPROD' SET PROPERTIES (DB_LOCATION) VALUES ('XTRCT_DWPROD_LOC')
OMBCOMMIT
OMBREGISTER LOCATION 'XTRCT_DWEXTRACT_LOC'
OMBCOMMIT
OMBREGISTER LOCATION 'XTRCT_DWPROD_LOC'
OMBCOMMIT
OMBREGISTER LOCATION 'DWEXTRACT_INPUT'
OMBCOMMIT
OMBREGISTER LOCATION 'DWEXTRACT_OUTPUT'
OMBCOMMIT
OMBCC 'XTRCT_DWEXTRACT'
OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'MAPPING_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('CREATE') SET REFERENCE MAPPING 'XTRCT_PROTOTYPE_XTRCTFILE_000'
OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
OMBCOMMIT
OMBDISCONNECT
Kind Regards,
Emrah
Edited by: cakire82 on Jul 29, 2009 12:57 PM

Answer 1

If it helps, this is a chunk from a script I have which turned off the parallel loading hint on all targets in a given mapping which was required after we discovered that ANSI cross joins and parallel query do NOT work very well in Oracle 10.
You can see that I OMBRETREIVE all table operators and then use a foreach loop to cycle through them.
log_msg LOG  "Altering: $mapName"
set tablist [OMBRETRIEVE MAPPING '$mapName' GET TABLE OPERATORS ]
foreach tgt_tble $tablist {
    if [catch { set retstr [ OMBALTER MAPPING '$mapName' MODIFY OPERATOR    '$tgt_tble' SET PROPERTIES (LOADING_HINT) VALUES ('NOPARALLEL ("$mapName")')] } errmsg] {
        log_msg ERROR "Unable to set hint for table $tgt_tble of mapping $mapName "
        log_msg ERROR "$errmsg"
    } else {
        set print [ exec_omb OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'MAPPING_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('CREATE') SET REFERENCE MAPPING '$mapName' ]
        if [omb_error $print] {
             log_msg ERROR "Unable to create Deployment plan for '$mapName'"
        } else {
              set print [ exec_omb OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ]
              if [omb_error $print] {
                  log_msg ERROR "Error on execute of Deployment plan for '$mapName'"
        OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
        OMBCOMMIT
}Ignore the exec_omb function as this is just a wrapper I built for OMB+ commands.
As to passing parameters, look into argc and argv:
if { $argc > 0 } {
     set i 1
     foreach arg $argv {
          puts "argument $i is $arg"
          incr i
  } else {
     puts "no command line argument passed"
  }You can also write interactive scripts if you prefer too. From earlier in the script above which turned off the parallel hint:
puts ""
puts -nonewline "Which mapping do you want to set to NOPARALLEL? "
set mapName [gets stdin]I've even done loops to allow the user to perform the operation on multiple mappings, and to use pattern matching to determine which mappings to alter:
set doLoop "1"
while { [string match "1" $doLoop] } {
    puts -nonewline "What mapping to reconfigure (use name of generated plsql package)? "
    flush stdout
    set mapName [ string toupper [gets stdin] ]
    puts -nonewline "What value do you want to set as the maximum allowed errors? "
    flush stdout
    set eValue [gets stdin]
    set mapList [OMBLIST MAPPINGS '.*$mapName.*']
    if { [llength $mapList] == 0 } {
       log_msg ERROR "No mappings matching search string $mapName"
    } else {
        foreach mName $mapList {
             puts -nonewline "Update mapping $mName (y/n)? "
             flush stdout
             set doThisUpdate [string toupper [gets stdin]]
            if { [string match "Y" $doThisUpdate ] } {
                if [catch { set retstr [ OMBALTER MAPPING '$mName' SET PROPERTIES (MAXIMUM_NUMBER_OF_ERRORS) VALUES ( '$eValue')] } errmsg] {
                    log_msg ERROR "Unable to modify max errors on Mapping $mName"
                    log_msg ERROR "$errmsg"
                } else {
                    set print [ exec_omb OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'MAPPING_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('CREATE') SET REFERENCE MAPPING '$mName' ]
                    if [omb_error $print] {
                        log_msg ERROR "Unable to create Deployment plan for '$mName'"
                    } else {
                        set print [ exec_omb OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ]
                        if [omb_error $print] {
                            log_msg ERROR "Error on execute of Deployment plan for '$mName'"
                    exec_omb OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
                    exec_omb OMBCOMMIT
            } else {
                log_msg LOG "Skipping update to mapping $mName"
    puts -nonewline "Do Another? (y/n) "
    flush stdout
    set doAnother [gets stdin]
    if { [string match "Y" [string toupper $doAnother] ] } {
        log_msg LOG "User requests more updates"
    } else {
        set doLoop "0"
}Anyway - there is lots that you can do to parameterize script or make them interactive. Just spend a bit of time working through a couple of TCL tutorials and you'll be well on your way.
+(Note: script chunks have been edited for clarity of the main point I wanted to illustrate and may contain missmatched braces or other syntax problems.)+