Using OMBPlus to collectively change schemas for tables in mappings
Ideally all configuration properties for OWB mappings need not be changed half way into a project. With a large number of mappings, this can be a time consuming job. Once again, OMBPlus can be a big help here.
The example below shows how to collectively change the schema name for a set of mappings to a new one. This example assumes that mapping names are named after their target table, and that the mappings are preceded by a 8 letter prefix (e.g. “map_stg_” for a staging mapping).
OMBCONNECT user/password@fully-qualified-connect-string USE REPOS 'repository'
OMBCC 'your_project'
OMBCC 'your_module'
set mapList [OMBLIST MAPPINGS 'your_mappings']
foreach mapName $mapList {
set operName [string range '$mapName' 9 end]
set Val [OMBRETRIEVE MAPPING '$mapName' OPERATOR '$operName' GET PROPERTIES(SCHEMA)]
puts [concat $mapName " " $operName " " $Val]
if {$Val == "old_schema"} {
OMBALTER MAPPING '$mapName' \
MODIFY OPERATOR '$operName' SET PROPERTIES (SCHEMA) VALUES ('new_schema')
puts [concat $mapName ": changed SCHEMA from [old_schema] to [new_schema]" ]
}
}
OMBCOMMIT
OMBDISCONNECT
Comments: (0)
Blogs
- 26 Jul
- 10 Jun
- 02 Jun
- 26 Mar
- 25 Feb
-
05 Nov
Some tips & tricks on migrating SOA Suite 10g to 11g – Part 2
- 04 Nov
- 02 Nov
- 25 Oct
- 20 Oct
- Best practices 2 - Web Services
- Fault handling in Oracle SOA Suite 11g - Part II
- Fault handling in Oracle SOA Suite 11g
- Migrating Web Services from JDeveloper 10g to 11g
- Migrating EJB 3 applications from OC4J to WebLogic
- Best practices for BPM, SOA and EDA
- Some tips & tricks on migrating SOA Suite 10g to 11g - Part 2
- Logging messages in Oracle SOA Suite 11g using OWSM
Loading ...