OMB Plus to set CDC properties of Oracle Module

Hi,
Does anybody know if it is possible to set the CDC properties of an Oracle Module using OMB Plus?
I was thinking in the lines of
OMBALTER ORACLE_MODULE 'MY_CDC_MODULE' SET PROPERTIES (CDC_CODE_TEMPLATE) VALUES ('PUBLIC_PROJECT/BUILT_IN_CT/JCT_10G_CONSISTENT_MINER')
but this does not work, and I can't see any appropriate properties in the documentation.
In addition to setting the CDC template I would like to be able to choose the tables to include in CDC using a script as well. Any help would be appreciated
Roald
Edited by: roheie on Oct 12, 2010 12:17 AM

Hi Oleg,
I think I may need to clarify my question. I am no trying to alter a template mapping, I am trying to alter the properties of the Oracle Module that is the source for the CDC template mappings
What I am trying to do in the script is the same operation as you do in the Design Center when you expand Databases->Oracle and then double click your 'CDC_SOURCE_SYSTEM' (example name) module to get to the properties wizard. In there you can set 'Metadata Location', 'Data Location', 'CDC Code Template', and 'CDC tables'. The first two of these I am already setting in my script, what I am asking is how I can set the last two of these properties
Regards,
Roald

Similar Messages

OMB: unable to set SQLLoader properties in a Mapping (TRAILING_NULLCOLS...)

Hello,
I've created a Mapping from a Flatfile to a table.
Since SQL-Loader is used I have to set several properties (TRALING_NULLCOLS, FILELOCATION, etc)
However, every property I try to set fails by the same error:
OMBALTER MAPPING 'MAP_DIM_UNIT_TEST' \
SET PROPERTIES (TRAILING_NULLCOLS) VALUES ('true')
--> OMB02902: Error setting property TRAILING_NULLCOLS of MAP_DIM_UNIT_TEST: MMM1034: Property TRAILING_NULLCOLS does not exist.Reading and setting these properties on Mappings created by the Design Center was no problem.
What am I missing?
When configuring a Mapping in the Design Center I have to create the "SQL Loader Data Files".
Maybe that's got something to do with it. I have no idea how to do that with OMBPlus.
Any clue?
Regards
uhuebner

Hi
You should set the GENERATION LANGUAGE property to SQLLOADER for the map. The property set is different depending on the type of the map, the UI does some tricks I think and sets up, but the API does not (it does at certain points like generation/validation).
Here are some other snippets you will find useful.....
1. To add a source data file to a mapping:
OMBALTER MAPPING 'LOAD_LOCATIONS' ADD SOURCE_DATA_FILE 'LOCATIONS_APAC'
2. To define the discard file info
OMBALTER MAPPING 'LOAD_LOCATIONS' MODIFY SOURCE_DATA_FILE 'LOCATIONS_APAC' SET PROPERTIES (DISCARD_FILE_LOCATION,DISCARD_FILE_NAME) VALUES ('APAC_FILE_STG_LOC', 'apac_discard.txt')
3. To define the data file info
OMBALTER MAPPING 'LOAD_LOCATIONS' MODIFY SOURCE_DATA_FILE 'LOCATIONS_APAC' SET PROPERTIES (DATA_FILE_LOCATION, DATA_FILE_NAME) VALUES ('APAC_FILE_STG_LOC', 'apac_data.txt')
4. To define the bad file info
OMBALTER MAPPING 'LOAD_LOCATIONS' MODIFY SOURCE_DATA_FILE 'LOCATIONS_APAC' SET PROPERTIES (BAD_FILE_LOCATION,BAD_FILE_NAME) VALUES ('APAC_FILE_STG_LOC', 'apac_bad.txt')
5 To query the files it is not obvious (or consistent with other commands)...
OMBRETRIEVE MAPPING 'SR_AGS_LDR' GET SOURCE_DATA_FILE
Notice the 'GET SOURCE_DATA_FILE' is singular even though it possibly return a list (in most other commands some form of the plural is used ie. GET TABLE OPERATORS).
Cheers
David

Setting RMI properties in app module

Howdy all,
How does one define java system properties, specifically some
RMI properties, to be accessible by an application module? I
tried putting them in the
appmodule_package_AppModuleName.properties
file, but that didn't work. I need to set some basic RMI app
properties so that my app module can act as an RMI client.
I also need to set a security policy file for my app module.
If anyone has any idea how to accomplish these things, let me
know!
Thanks,
Joe

I have solved this by removing the 0 from the static VO

Scripting active configuration deployment location for an oracle module

Hi,
Does anyone know how to script the setting of the active configuration deployment location for an oracle module?
I have executed the following which works fine but I can't figure out how to make it active so the module shows up in the control center to allow deployment.
I can of course do it manually in the design center by right clicking on the module in the design center, selecting 'Configure' and then (strangely) just selecting the location property which then automatically sets the active location and then it shows up in the control center.
OMBALTER ORACLE_MODULE 'MOD_EXT' ADD REFERENCE LOCATION 'MIG_EXT_LOCATION' SET AS DEFAULT
Oracle module MOD_EXT altered.
OMBALTER ORACLE_MODULE 'MOD_EXT' SET REFERENCE METADATA_LOCATION 'MIG_EXT_LOCATION'
Oracle module MOD_EXT altered.
Any ideas?
Regards,
Brad

Hi Brad,
before you set the location you have to set the correct configuration (in case you use more configurations than the default "DEFAULT_CONFIGURATION") as active configuration:
OMBCAC 'MY_CONFIGURATION'
Regards,
Carsten.

Installing OMB Plus in Oracle JDeveloper

Hello
I have JDeveloper 11.1.1.3.0, and I like to enable the IDE for OMBPlus development.
I followed the guide at http://download.oracle.com/docs/cd/B28359_01/owb.111/b31279.pdf (appendix Installing OMB Plus in Oracle JDeveloper)
1. Drop shiphome/owb/lib/int/OMBPlus_jdev.jar in the JDeveloper
installation directory/lib/ext directory.
2. Start JDeveloper.
3. From the Tools menu, select Preferences, OMBPlus, and then OMBPlus
Installation to set the Warehouse Builder installation directory. For example,
c:\oracle\ora81. Do not include the Warehouse Builder directory at the end
of this path.
4. Restart JDeveloper.
Repeat steps 3 and 4 each time you change the Warehouse Builder installation
directory.
However I do not get a OMBPlus menu in the Preferences window.
Can you please help me?
/kasper

kasper,
There is a bug report in support.oracle.com with the exact same symptoms - I could find no documentation about the version of JDev supported by OMBPlus, but I'm strongly guessing that JDev 11 isn't supported. In fact, I guarantee it.
I've cracked open OMBPlus.jar and had a look at the extension manifest - it's for JDev 9.0.x, which isn't available to download any more. Your best bet would probably be to file a support request to see what they have to say.
John

How to set JVM system properties in Oracle Portal ??

Hello Guys,
I want to set javax.net.ssl.trustStore="path to keystore" ,JVM system properties on oracle portal,
Like i want to configure my keystore with oracle portal so that my application can make a success full connection with back end using https.
i read the following note from one of the Oracle tech note,which says that
It is important that this system property is passed as a command line option to Oracle Application Server Containers for J2EE (OC4J). Setting the property in oc4j.properties will not help because the system property is read first before OC4J reads this file. Therefore, it is best to modify the <java-option> line in the OC4J_portal section of ORACLE_HOME/opmn/conf/opmn.xml.
So, i made the required changes to OC4J_portal section of opmn.xml file as below
added value is shown in bold
<data id="java-options" value="-server -Xrs -Djava.security.policy=C:\oracle\OraPortal\j2ee\OC4J_Portal\config\java2.policy -Djava.awt.headless=true -Xmx256m -Djavax.net.ssl.trustStrore=C:\keystore1 -Djavax.net.ssl.trustStrorePassword=password1"/>
Even after making these changes, my application not able to make connection using https.
Could u guys explain me, what things are going wrong or somethings else i need to do to make it work.
Any thoughts would be highly appreciated.
Thanks
<Neeraj Sidhaye/>
http://ExtremePortal.blog.co.uk

Hello Guys,
I want to set javax.net.ssl.trustStore="path to
keystore" ,JVM system properties on oracle
portal,
-Xmx256m -Djavax.net.ssl.trustStrore=C:\keystore1
-Djavax.net.ssl.trustStrorePassword=password1"/>Hi,
if the above is an exact copy of the values you inserted then it looks like you have two typos in the command line parameters.
-Djavax.net.ssl.trustStrore -> trustStore
-Djavax.net.ssl.trustStrorePassword -> trustStorePassword

OMBCREATE LOCATION hangs (OMB*Plus 11.1.0.7)

My try to create a file location in OMBPlus failed.
OMBCONNECT <ConnectString> USE WORKSPACE 'RUNTIME' USE MULTIPLE_USER_MODEConnected.
OMBCONNECT CONTROL_CENTER <ConnectString> USE WORKSPACE 'OWNER.RUNTIME'Control Center connected.
OMBCREATE LOCATION 'LOC_FILE' SET PROPERTIES (TYPE, ROOTPATH) VALUES ('FILE_SYSTEM', '/tmp')Even after several minutes there is no return of the last command !
Info: The location already exist, OMB*Plus is 11.1.0.7
Any ideas how to solve that issue?
Beat

user12086319 wrote:
Hi EdStevens,
Following the instructions in previous post, I can connect with SQL plus (the database is on the same box* as your sqlplus client); I just enter sqlplus in windows console.
In addition, i am still curious about how SQL plus connect to a remote* box. Could you shed more light on that?SQLPlus connects to a remote db the same way any other app does. After all, sqlplus is just another client app.
It's all in the connect string. So say, at a command prompt you enter
$> sqlplus scott/tiger@mydbso in the above example, 'scott' is the user, 'tiger' is the password, and 'mydb' is the tns service name. Of course, the OS passes all that to sqlplus as a command line parameter. Internally, sqlplus makes a call to the tns layer and passes it the connect information it has. TNS will take a look at the tnsnames.ora file and find an entry for 'mydb', and from there it will get the name or ip address of the host server, a port number, and a service name. That information will be passed on down the network stack for routing. (If a name was provided instead of an ip address, the OS network stack will use whatever means are at its disposal - a hosts file, a dns lookup, or whatever, to get an ip address). The request will arrive at the specified host and placed on the specified port. If everything was configured correctly, there will be an oracle listener process monitoring that port. It will pick up the request and see if it recognizes the service name. If it does, it will spawn a user server process on a different port to complete the connection, then get out of the way and continue listening for more requests.
This is how it happens most of the time. There are a lot of other variants, but that's the gist of it.
More information can be found in the fine documentation at tahiti.oracle.com.

How to properly create a calendar using OMB*Plus, to schedule a workflow ?

Hello all,
I want to schedule a workflow when deploying via OMB*Plus.
It looks like I have a syntax error, but this happens even with the example given on
[the OMBCREATE CALENDAR documentation|http://download-uk.oracle.com/docs/cd/B31080_01/doc/owb.102/b28225/omb_4create_1.htm#sthref1427]
My code is:
OMBCREATE CALENDAR 'SCH_DELTA_test2' ADD SCHEDULE \
SET PROPERTIES (REPEAT_EXPRESSION)\
VALUES ('FREQ=WEEKLY;INTERVAL=1;BYDAY=TUE WED THU FRID SAT;BYHOUR=12;BYMINUTE=0;BYSECOND=0') ]
If I copy-paste an example from the doc, the last line becomes :
VALUES ('FREQ=MINUTELY;INTERVAL=20') ]
The result is:
OMB00001: Encountered \' at line: 1, column: 95. Was expecting one of: <INTEGER_LITERAL> ...
<FLOATING_POINT_LITERAL> ...
<QUOTED_STRING> ...
The position line: 1, column: 95 is the opening quote of the last line, just before FREQ=
I can't find any way to get this working. If anyone see something wrong or missing, please advise. Thanks in advance.
Cedric.

Hello Oleg,
I followed your advice, but OMB*Plus doesn't like it, as it seems :
the code:
OMBCREATE CALENDAR 'CAl_SCH_DELTA' ADD SCHEDULE 'SCH_DELTA' SET PROPERTIES (REPEAT_EXPRESSION) VALUES ('FREQ=MINUTELY;INTERVAL=20')
the error:
OMB00001: Encountered SCH_DELTA at line: 1, column: 49. Was expecting one of: <E
OF>
"SET" ...
Regards
Cedric.

Export mappings through OMB plus

Hi All,
We have developed 125 mappings across 10 modules. I wanted all mappings .Mdl files separately (E.g : we have mapping names are abc and xyz… we need to mdl file abc.mdl and xyz.mdl).
If I export mappings in Design Center mapping wise it will take alot of to complete/get individual scripts (.mdl)
I heard for time consuming and security wise we should use OMB plus.
Any one helps me to export mappings individually through OMB.
Is there any way to pass mapping name should export the mapping with log file?
Thanks and Regards
Venkat

OK, here is a script that you will be able to adapt get you to where you want to go. Bear in mind that it uses a config file to hold some variables, and library file which I shall also attach.
This script isn't exaclty what you are asking, but it's pretty close. The reason I made this script was to be able to create a clone of an existing project through OMB+ becuase in our corporate dev environment I couldn't lock down the repository in exclusive mode to do this in a simple copy/paste. The script uses a bit of a work-around because the MDL files include full path names, meaning if you export from project A it will want to import into project A. So if I want to import them into project B I take the existing project A, rename it to the desired new name (B), do the export (on a per-unit basis as you want), then rename the existing project back to what it was (A), create the new empty project (B) and import the objects now that the naming structures will match. (whew - did you catch all that?)
Anyway, here is the script. It uses standard TCL for a lot of the file stuff (glob etc), and for cycling through the modules and objects using the TCL foreach statement. Don't worry about the functions you don't recognize like exec_omb. They are in the library (coming up next), which just has to be colocated with the script for the script to reference at runtime:
# PVCS Version Information
#/* $Workfile:   create_deployment_mdl.tcl $ $Revision:   2.1 $ */
#/* $Author:   michael.broughton $
#/* $Date:   27 Nov 2008 10:00:04 $ */
# To run this script, start OMB Plus.
# Run this script providing the command (on Windows): source <path>/copy_owb_project.tcl
# e.g. source c:/owb/script/copy_owb_project.tcl
# Get Current Directory and time
set dtstmp     [ clock format [clock seconds] -format {%Y%m%d_%H%M}]
set scrpt      [ file split [file root [info script]]]
set scriptDir [ file dirname [info script]]
set scriptName [ lindex $scrpt [expr [llength $scrpt]-1]]
set cnfg_lib "$scriptDir/ombplus_config.tcl"
set owb_lib "$scriptDir/omb_library.tcl"
# Import Lbraries
#      Assumes that owb_config and omb_library are in the same directory as this
#      script.
#get config file
source $cnfg_lib
#get standard library
source $owb_lib
# Set Logfile
#    This will overwrite anything set in the config file.
set    SPOOLFILE ""
append SPOOLFILE $scriptDir "/log_" $scriptName "_" $dtstmp ".txt"
# PROCEDURES SECTION
proc owb_export_object {PROJECT_NAME MODULE_NAME MDL_PATH LOG_PATH TYPE TYPELIST} {
   set print [OMBCC '$MODULE_NAME']
   set objList [OMBLIST $TYPELIST]
   foreach objName $objList {
        set objExportStatus [OMBEXPORT MDL_FILE '$MDL_PATH/$objName.mdl' PROJECT '$PROJECT_NAME'\
                               COMPONENTS ($TYPE '$MODULE_NAME/$objName')\
                               OUTPUT LOG '$LOG_PATH/$objName.log']
        puts "$objExportStatus"
   set print [OMBCC '..']
   puts "$print"
# MAIN SCRIPT SECTION
log_msg LOG "This script is used to copy a minor version project into a major version project and to create a full project mdl file suitable for deployment. "
log_msg LOG "WARNING: This will overwrite any existing metadata in the major version project. If you have metadata you wish to save, stop now and go take care of that first! "
puts -nonewline "Do you want to continue?(Y/N) "
set EXITEARLY [gets stdin]
if [string match N $EXITEARLY] {
   log_msg LOG "Exiting...."
   return 0
} elseif [string match n $EXITEARLY] {
   log_msg LOG "Exiting...."
   return 0
} else {
   log_msg LOG "Continuing...."
puts -nonewline "Which project do you want to create a deployment file for? "
set CUR_PROJECT_NAME [gets stdin]
puts -nonewline "Under which final project name? "
set NEW_PROJECT_NAME [gets stdin]
puts -nonewline "Local temp directory to use for MDL generation: "
set MDL_PATH [gets stdin]
set LOG_PATH "$MDL_PATH/logs"
#set up the temp directory structure
if [catch { set retstr [file mkdir $MDL_PATH] } errmsg] {
    puts "Cannot create directory $MDL_PATH. due to error: $errmsg"
    puts "Exiting...."
    exit
} else {
   #make the subdirectories
   file mkdir $LOG_PATH
   file mkdir $MDL_PATH/mappings
   file mkdir $MDL_PATH/transforms
   file mkdir $MDL_PATH/tables
   file mkdir $MDL_PATH/views
   file mkdir $MDL_PATH/sequences
# Connect to repos
set print [exec_omb OMBCONNECT $OWB_DEG_USER/$OWB_DEG_PASS@$OWB_DEG_HOST:$OWB_DEG_PORT:$OWB_DEG_SRVC USE REPOSITORY '$OWB_DEG_REPOS']
if [omb_error $print] {
    exit_failure "Unable to connect to repository."
} else {
    log_msg LOG "Connected to Repository"
#    Test given project names
set print [exec_omb OMBCC '$CUR_PROJECT_NAME']
if [omb_error $print] {
   exit_failure "Project $CUR_PROJECT_NAME does not exist. Nothing to copy...."
exec_omb OMBCC '..'
set print [exec_omb OMBCC '$NEW_PROJECT_NAME']
if [omb_error $print] {
   log_msg LOG "Confirmed project $NEW_PROJECT_NAME does not exist..."
} else {
   log_msg LOG "Target project $NEW_PROJECT_NAME already exists. Dropping...."
   exec_omb OMBCC '..'
   set print [exec_omb OMBDROP PROJECT '$NEW_PROJECT_NAME']
   if [omb_error $print] {
       exit_failure "Unable to drop project $NEW_PROJECT_NAME. Exiting...."
   OMBSAVE
#    Begin export.
log_msg LOG "Temporarily renaming current project to new project name"
set print [exec_omb OMBALTER PROJECT '$CUR_PROJECT_NAME' RENAME TO '$NEW_PROJECT_NAME']
if [omb_error $print] {
   exit_failure "This account does not have alter privileges on this project"
OMBSAVE
OMBCC '$NEW_PROJECT_NAME'
set moduleList [OMBLIST ORACLE_MODULES]
foreach moduleName $moduleList {
   owb_export_object $NEW_PROJECT_NAME $moduleName $MDL_PATH/mappings $LOG_PATH MAPPING MAPPINGS
   owb_export_object $NEW_PROJECT_NAME $moduleName $MDL_PATH/transforms $LOG_PATH PROCEDURE PROCEDURES
   owb_export_object $NEW_PROJECT_NAME $moduleName $MDL_PATH/transforms $LOG_PATH FUNCTION FUNCTIONS
   owb_export_object $NEW_PROJECT_NAME $moduleName $MDL_PATH/tables $LOG_PATH TABLE TABLES
   owb_export_object $NEW_PROJECT_NAME $moduleName $MDL_PATH/views $LOG_PATH VIEW VIEWS
   owb_export_object $NEW_PROJECT_NAME $moduleName $MDL_PATH/sequences $LOG_PATH SEQUENCE SEQUENCES
puts "BACKUP PROCESS has been Completed."
OMBCC '..'
log_msg LOG "Renaming back to original project name"
set print [exec_omb OMBALTER PROJECT '$NEW_PROJECT_NAME' RENAME TO '$CUR_PROJECT_NAME']
log_msg LOG "Creating new project..."
set print [exec_omb OMBCREATE PROJECT '$NEW_PROJECT_NAME']
if [omb_error $print] {
   exit_failure "Unable to create project '$NEW_PROJECT_NAME'"
} else {
   log_msg LOG "Created Project '$NEW_PROJECT_NAME'"
   exec_omb OMBSAVE
   exec_omb OMBCC '$NEW_PROJECT_NAME'
log_msg LOG "Creating modules..."
foreach moduleName $moduleList {
    set print [exec_omb OMBCREATE ORACLE_MODULE '$moduleName']
OMBSAVE
log_msg LOG "Importing Tables..."
set mdl_maps [glob $MDL_PATH/tables/*mdl]
foreach mdl_map $mdl_maps {
     puts "importing TABLE module $mdl_map from MDL file"
     set print [OMBIMPORT MDL_FILE '$mdl_map' USE CREATE_MODE MATCH_BY NAMES]
     puts "$print"
OMBSAVE
log_msg LOG "Importing Sequences..."
set mdl_maps [glob $MDL_PATH/sequences/*mdl]
foreach mdl_map $mdl_maps {
     puts "importing SEQUENCE module $mdl_map from MDL file"
     set print [OMBIMPORT MDL_FILE '$mdl_map' USE CREATE_MODE MATCH_BY NAMES]
     puts "$print"
OMBSAVE
log_msg LOG "Importing Views..."
set mdl_maps [glob $MDL_PATH/views/*mdl]
foreach mdl_map $mdl_maps {
     puts "importing VIEW module $mdl_map from MDL file"
     set print [OMBIMPORT MDL_FILE '$mdl_map' USE CREATE_MODE MATCH_BY NAMES]
     puts "$print"
OMBSAVE
log_msg LOG "Importing PlSql..."
set mdl_maps [glob $MDL_PATH/transforms/*mdl]
foreach mdl_map $mdl_maps {
     puts "importing PLSql module $mdl_map from MDL file"
     set print [OMBIMPORT MDL_FILE '$mdl_map' USE CREATE_MODE MATCH_BY NAMES]
     puts "$print"
OMBSAVE
log_msg LOG "Importing Mappings..."
# import mappings from directory of MDL files
set mdl_maps [glob $MDL_PATH/mappings/*mdl]
foreach mdl_map $mdl_maps {
     puts "importing MAPPING module $mdl_map from MDL file"
     set print [OMBIMPORT MDL_FILE '$mdl_map' USE CREATE_MODE MATCH_BY NAMES]
     puts "$print"
OMBSAVE
log_msg LOG "Completed Import..."
log_msg LOG "Exporting complete project file...."
set objExportStatus [OMBEXPORT MDL_FILE '$MDL_PATH/$NEW_PROJECT_NAME.mdl' PROJECT '$NEW_PROJECT_NAME' OUTPUT LOG '$LOG_PATH/$NEW_PROJECT_NAME.log']
puts "$objExportStatus"
log_msg LOG "Cleaning up temp directory..."
file delete -force $MDL_PATH/mappings
file delete -force $MDL_PATH/transforms
file delete -force $MDL_PATH/tables
file delete -force $MDL_PATH/views
file delete -force $MDL_PATH/sequences
file delete -force $LOG_PATH
OMBDISCONNECT And here is my standard helper library:
# PVCS Version Information
#/* $Workfile:   omb_library.tcl $ $Revision:   2.9 $ */
#/* $Author:   michael.broughton $
#/* $Date:   10 Mar 2009 11:04:50 $ */
# Default logging function.
# Accepts inputs: LOGMSG - a text string to output
proc log_msg {LOGTYPE LOGMSG} {
   #logs to screen and file
   global SPOOLFILE
   if {![info exists SPOOLFILE]} {
       puts "LOGFILE UNDEFINED! :-> $LOGTYPE:-> $LOGMSG"
   } else {
       set fout [open "$SPOOLFILE" a+]
       puts $fout "$LOGTYPE:-> $LOGMSG"
       puts "$LOGTYPE:-> $LOGMSG"
       close $fout
proc log_msg_file_only {LOGTYPE LOGMSG} {
    #logs to file only
    global SPOOLFILE
    if {![info exists SPOOLFILE]} {
       puts "LOGFILE UNDEFINED! :-> $LOGTYPE:-> $LOGMSG"
    } else {
       set fout [open "$SPOOLFILE" a+]
       puts $fout "$LOGTYPE:-> $LOGMSG"
       close $fout
proc exit_failure { msg } {
   log_msg ERROR "$msg"
   log_msg ERROR "Rolling Back....."
   exec_omb OMBROLLBACK
   log_msg ERROR "Exiting....."
   # return and also bail from calling function
   return -code 2
proc exec_omb { args } {
   log_msg_file_only OMBCMD "$args"
   # the point of this is simply to return errorMsg or return string, whichever is applicable,
   # to simplify error checking using omb_error{}
   if [catch { set retstr [eval $args] } errmsg] {
      log_msg OMB_ERROR "$errmsg"
      log_msg "" ""
      return $errmsg
   } else {
      log_msg OMB_SUCCESS "$retstr"
      log_msg "" ""
      return $retstr
proc omb_error { retstr } {
   # OMB and Oracle errors may have caused a failure.
   if [string match OMB0* $retstr] {
      return 1
   } elseif [string match ORA-* $retstr] {
      return 1
   } elseif [string match java.* $retstr] {
      return 1
   } elseif [string match Error* $retstr] {
      return 1
   } else {
      return 0
proc ers_omb_connect { OWB_USER OWB_PASS OWB_HOST OWB_PORT OWB_SRVC OWB_REPOS } {
   # Commit anything from previous work, otherwise OMBDISCONNECT will fail out.
   catch { set retstr [ OMBSAVE ] } errmsg
   log_msg LOG "Checking current connection status...."
   #Ensure that we are not already connected.
   if [catch { set discstr [ OMBDISCONNECT ] } errmsg ] {
      set discstr $errmsg
   # Test if message is "OMB01001: Not connected to repository." or "Disconnected."
   # any other message is a showstopper!
   if [string match Disconn* $discstr ] {
      log_msg LOG "Success Disconnecting from previous repository...."
   } else {
      # We expect an OMB01001 error for trying to disconnect when not connected
      if [string match OMB01001* $discstr ] {
          log_msg LOG "Disconnect unneccessary. Not currently connected...."
      } else {
          log_msg ERROR "Error Disconnecting from previous repository....Exiting process."
          exit_failure "$discstr"
   set print [exec_omb OMBCONNECT $OWB_USER/$OWB_PASS@$OWB_HOST:$OWB_PORT:$OWB_SRVC USE REPOSITORY '$OWB_REPOS']
   if [string match *Connected* $print] {
      return $print
   } else {
      return "OMB0-Unknown Error connecting. Validate connection settings and try again"
proc ers_omb_drop_mapping { MAPNAME } {
    set mplst [OMBLIST MAPPINGS]
    if {[string match *$MAPNAME* $mplst]} {
       log_msg LOG "Mapping $MAPNAME Exists."
       log_msg LOG "Un-Deploying: $MAPNAME"
       set print [ exec_omb OMBCREATE TRANSIENT DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ADD ACTION 'MAPPING_DEPLOY' SET PROPERTIES (OPERATION) VALUES ('DROP') SET REFERENCE MAPPING '$MAPNAME' ]
       if [omb_error $print] {
           exit_failure "Unable to create Deployment plan for '$MAPNAME'"
       set print [ exec_omb OMBDEPLOY DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN' ]
       if [omb_error $print] {
           exit_failure "Error on execute of Deployment plan for '$MAPNAME'"
       exec_omb OMBDROP DEPLOYMENT_ACTION_PLAN 'DEPLOY_PLAN'
       exec_omb OMBSAVE
       set print [exec_omb OMBDROP MAPPING '$MAPNAME']
       if [omb_error $print] {
           exit_failure "Failed attempt to drop existing version of this mapping. Exiting."
proc ers_omb_refresh_object { OBJTYPE OBJNAME } {
   # prompts for refresh of object if exists, except for sequence which do not structurally change.
   # VALID FOR SEQUENCES, TABLES, AND VIEWS ONLY
    global ORA_MODULE_NAME
    set l_objtype [string tolower $OBJTYPE]
    set OBJTYPES $OBJTYPE
    append OBJTYPES "S"
    set tblst [OMBLIST $OBJTYPES]
    if {[string match *$OBJNAME* $tblst]} {
         log_msg LOG "$l_objtype $OBJNAME already exists."
         if [string match SEQUENCE $OBJTYPE] {
             # Sequences don't need refreshing!
            log_msg LOG "No need to refresh sequence..."
            return
         puts -nonewline "Do you want to re-import the $l_objtype?(Y/N) "
         set EXITEARLY [gets stdin]
         log_msg_file_only LOG "Do you want to re-import the $l_objtype?(Y/N) $EXITEARLY"
         if {[string match Y $EXITEARLY] || [string match y $EXITEARLY]} {
            log_msg LOG "Re-importing $OBJNAME...."
            exec_omb OMBDROP $OBJTYPE '$OBJNAME'
            exec_omb OMBSAVE
            exec_omb OMBCC '..'
            set print [exec_omb OMBCREATE TRANSIENT IMPORT_ACTION_PLAN 'IMPORT_PLAN' ADD ACTION 'IMPORT_ACTION' SET REF SOURCE $OBJTYPE '$OBJNAME' SET REF TARGET ORACLE_MODULE '$ORA_MODULE_NAME']
            if [omb_error $print] {
                exit_failure "Failed attempt to create import plan this $l_objtype. Exiting."
            set print [exec_omb OMBIMPORT FROM METADATA_LOCATION FOR IMPORT_ACTION_PLAN 'IMPORT_PLAN']
            exec_omb OMBDROP IMPORT_ACTION_PLAN 'IMPORT_PLAN'
            if [omb_error $print] {
                exit_failure "Failed attempt to import this $l_objtype. Exiting."
            } elseif [string match *Failure* $print] {
                #A failure to create second-class objects will not be caught with omb_error()
                log_msg ERROR "An error prevented proper import. I recommend re-trying import through the GUI, and "
                log_msg ERROR "then re-running this script but answering 'N' to re-import for this $l_objtype."
                exit_failure "Failed attempt to import this $l_objtype. Exiting."
            if [string match TABLE $OBJECTTYPE] {
             if [string match I_APLCTN_DTL_DSB_ELGBL_CHLDRN $OBJNAME] {
                set SHDWNAME I_APLCTN_DSB_ELGBL_CHLDRN
             } elseif [string match F_RPTD_ENTLMNT_MNTHLY_SNPSHT $OBJNAME] {
                set SHDWNAME F_RPTD_ENTLMNT_SNPSHT
             } elseif [string match U_PROG_BNFT_PRVSN_ADMS_MAP $OBJNAME] {
                set SHDWNAME U_PROG_BNFT_PRVSN_ADM_MAP
             } elseif [string match U_PROG_BNFT_PRVSN_LGCY_MAP $OBJNAME] {
                set SHDWNAME U_PROG_BNFT_PRVSN_LGC_MAP
             } elseif [string match U_BNFCRY_CMBND_DBL_ENTLMNT $OBJNAME] {
                set SHDWNAME U_BNFCRY_CMBND_DB_ENTLMNT
             } else {
                set SHDWNAME $OBJNAME
                if [catch { set retstr [ OMBALTER TABLE '$OBJNAME' SET PROPERTIES (SHADOW_TABLE_NAME) VALUES ( 'ERR\$_$SHDWNAME')] } errmsg] {
                   log_msg ERROR "Unable to set shadow table name for table $OBJNAME"
                   log_msg ERROR "$errmsg"
            exec_omb OMBCC '$ORA_MODULE_NAME'
         } else {
           log_msg LOG "Skipping $l_objtype re-import...."
    } else {
         log_msg LOG " $l_objtype $OBJNAME Does not exist."
         log_msg LOG "Importing $OBJNAME...."
         exec_omb OMBCC '..'
         set print [exec_omb OMBCREATE TRANSIENT IMPORT_ACTION_PLAN 'IMPORT_PLAN' ADD ACTION 'IMPORT_ACTION' SET REF SOURCE $OBJTYPE '$OBJNAME' SET REF TARGET ORACLE_MODULE '$ORA_MODULE_NAME']
         if [omb_error $print] {
             exit_failure "Failed attempt to create import plan this $l_objtype. Exiting."
         set print [exec_omb OMBIMPORT FROM METADATA_LOCATION FOR IMPORT_ACTION_PLAN 'IMPORT_PLAN']
         exec_omb OMBDROP IMPORT_ACTION_PLAN 'IMPORT_PLAN'
         if [omb_error $print] {
             exit_failure "Failed attempt to import this $l_objtype. Exiting."
         } elseif [string match *Failure* $print] {
             #A failure to create second-class objects will not be caught with omb_error()
             log_msg ERROR "An error prevented proper import. I recommend re-trying import through the GUI, and "
             log_msg ERROR "then re-running this script but answering 'N' to re-import for this $l_objtype."
             exit_failure "Failed attempt to import this $l_objtype. Exiting."
         exec_omb OMBCC '$ORA_MODULE_NAME'
}    And the config file:
# PVCS Version Information
#/* $Workfile:   ombplus_config.tcl $ $Revision:   2.0 $ */
#/* $Author:   gerry.hunt $
#/* $Date:   28 Nov 2008 08:37:12 $ */
# This version of the Config file differs from the standard owb_config.tcl
# used by the deployment script. It requires TWO repository configurations
# (Corporate Design Repository and Deployment location runtime repository)
# and does not require some of the logging / file location info used by the
# install script.
# GLOBAL VARIABLE DECLARATION SECTION
#CORPORATE DESIGN REPOSITORY CONNECTION INFORMATION
# Login info for the design repository owner
set OWB_DEG_USER    michael_broughton
set OWB_DEG_PASS    my_password
set OWB_DEG_HOST    123.4.5.6
set OWB_DEG_PORT    1628
set OWB_DEG_SRVC     ORCL
set OWB_DEG_REPOS   owb_mgr
# RUNTIME CONTROL CENTER AND LOCATION DECLARATION SECTION
set CONTROL_CENTER_NAME        ERS_CTL_DEVR1000_1T
set CONTROL_CENTER_SCHEMA      owb_mgr
set CONTROL_CENTER_PASS        owb_mgr_PWD
#Connection info to ers_etl_app deployment schema
set DATA_LOCATION_NAME         ERS_DEVR1000_1T
set DATA_LOCATION_VERS         10.2
set DATA_LOCATION_USER         ERS_ETL_APP1T
set DATA_LOCATION_PASS         ERS_ETL_APP1T
set DATA_LOCATION_HOST         host001
set DATA_LOCATION_PORT         1554
set DATA_LOCATION_SRVC         orcl
# PROJECT,MUDULE AND DIRECTORY DECLARATION SECTION
set PROJECT_NAME       ERS_DM_R7_0C6_02
set ORA_MODULE_NAME    ERS_ETL_APPDang... that's a lot of stuff. But it should get you well on your way to what you need.
Cheers,
Mike

OMB*Plus error defining CONTROL_FILE_LOCATION property

Hello,
I have built a script which creates a mapping that, simply, maps all fields from a flat file to a stage table. A column called 'CAP_DATE' is added to the table and this column is mapped from a constant. The mapping is under 'STG' module within 'Databases/Oracle' module.
I want to set the CONTROL_FILE_LOCATION mapping property in order to set the location which the .ctl file will be deployed in. The location name is 'PHASE_1B' and it is defined within 'Files' module.
So, when I try to run the following statement (within 'STG' context):
OMBALTER MAPPING '$map_0' SET PROPERTIES (CONTROL_FILE_NAME,CONTROL_FILE_LOCATION) VALUES ('$map_0.tcl','PHASE_1B')
I get the error:
OMB02902: Error setting property CONTROL_FILE_LOCATION of M_ST_NCRM_INTTXT: PUB02106: Invalid value PHASE_1B for property CONTROL_FILE_LOCATION on map M_ST_NCRM_INTTXT: PUB02769 : PHASE_1B is not the name of a valid location for this property.
I think this is because the location I'm trying to assign is in another context and OMB*Plus doesn't find it. Am I right? How can I solve this problem?
Kind regards,
Natividad.

Stas,
I don't think you're doing something wrong... I just did:
OMB+> OMBREDEFINE CLASS_DEFINITION 'PROJECT' \
ADD PROPERTY_DEFINITION 'WHATEVER' \
SET PROPERTIES (TYPE) VALUES ('STRING')OMB+> OMBALTER PROJECT 'MY_PROJECT' \
SET PROPERTIES (UDP_WHATEVER) \
VALUES ('Hello')
which works fine. I think you are hitting a bug. Have to admit, I am running version 9.2.0.4 for this example... but I get the same problem for your scenario. I.e. I filed bug 3686842. Only workaround is to use the UI for now.
Thanks,
Mark.

OMB command to set the location of an ODBC module

I am writing OMB scripts to deploy an OWB project to a production environment.
In the deployment script, I set the location of an Oracle module using the OMB commands :
OMBALTER ORACLE_MODULE '<modulename>' ADD REFERENCE LOCATION '<locationname>' SET AS DEFAULT
OMBALTER ORACLE_MODULE '<modulename>' SET PROPERTIES (DB_LOCATION) VALUES ('<locationname>')
I also have an ODBC module for which I need to assign a location in the same way
What is the OMB syntax to achieve this?
OWB version 10.2.0.4

You can use GATEWAY_MODULE for these. For example ...
OMBALTER GATEWAY_MODULE '<modulename>' SET PROPERTIES (DB_LOCATION) VALUES ('<locationname>')
Cheers
David

Discoverer Plus/Viewer from menu item in Oracle Applications errors.

Starting Discoverer Plus/Viewer from menu item in Oracle Applications R12 errors.
Here is some general config information that is suspected to be the issue.
1. Running Oracle Applications R12 over HTTPS.
2. Running Discoverer Plus/Viewer over HTTP.
3. Calling menu item that calls a function to start Plus/Viewer.
Function Definition called by the menu item is listed blow.
Properties Tab: Type=SSWA jsp function Context Dependence=Responsibility
Form Tab: Parameters="mode=DISCO"
Web HTML Tab: HTML Call=OracleOasis.jsp
Fact: Starting Discoverer Plus using a URL works fine in the browser. The login page comes up and I can look in to Plus.
The page that dose a redirection to start the Plus applet or Viewer web page fails with this error in IE 7.
Internet Explorer cannot display the webpage
Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.
Thank you for your time.

Hi,
Check that the ICX system profiles are set correctly for your Discoverer configuration. In particular the ICX: Discoverer Launcher and ICX: Discoverer Viewer Launcher system profiles.
When IE displays an error is the URL displayed in the browser a correct Disco URL?
Rod West

How to stop a scheduled job using OMB*Plus ?

Hello everyone,
I use a OMB*Plus script to deploy a project in various environments. This includes scheduled jobs.
In this context, I need to stop the schedules of the previous versions to avoid a script crash.
I found the OMBSTOP command thad could do, but I need to retrieve the job ID of the schedule I want to stop. And I don't know how to get the Job ID.
I could get it from a previous launch and save it somewhere, but it wouldn't work if the schedule was manually stopped and restarted. Maybe is there a command that lists the running / scheduled jobs and their IDs? I didn't find it.
Thanks in advance for your help.
Cedric.

Frankly, I cannot see where this is available via pure OMB+, however you could back-door it if if you can figure out how to get these values from the public views (I would guess from the "Scheduling Views" section at http://download-east.oracle.com/docs/cd/B31080_01/doc/owb.102/b28225/toc.htm).
Then you could use my SQL library from OMB+ to get these values and stop the schedules before deploying. you can save this file as omb_sql_library.tcl and then just "source /path/to/omb_sql_library.tcl in your own script to make the functions available in your script.
{code}
package require java
# PVCS Version Information
#/* $Workfile: omb_sql_library.tcl $ $Revision: 1.0 $ */
#/* $Author: $
#/* $Date: 03 Apr 2008 13:43:34 $ */
proc oracleConnect { serverName databaseName portNumber username password } {
# import required classes
java::import java.sql.Connection
java::import java.sql.DriverManager
java::import java.sql.ResultSet
java::import java.sql.SQLWarning
java::import java.sql.Statement
java::import java.sql.CallableStatement
java::import java.sql.ResultSetMetaData
java::import java.sql.DatabaseMetaData
java::import java.sql.Types
java::import oracle.jdbc.OracleDatabaseMetaData
# load database driver .
java::call Class forName oracle.jdbc.OracleDriver
# set the connection url.
append url jdbc:oracle:thin
append url :
append url $username
append url /
append url $password
append url "@"
append url $serverName
append url :
append url $portNumber
append url :
append url $databaseName
set oraConnection [ java::call DriverManager getConnection $url ]
set oraDatabaseMetaData [ $oraConnection getMetaData ]
set oraDatabaseVersion [ $oraDatabaseMetaData getDatabaseProductVersion ]
puts "Connected to: $url"
puts "$oraDatabaseVersion"
return $oraConnection
proc oracleDisconnect { oraConnect } {
$oraConnect close
proc oraJDBCType { oraType } {
#translation of JDBC types as defined in XOPEN interface
set rv "NUMBER"
switch $oraType {
"0" {set rv "NULL"}
"1" {set rv "CHAR"}
"2" {set rv "NUMBER"}
"3" {set rv "DECIMAL"}
"4" {set rv "INTEGER"}
"5" {set rv "SMALLINT"}
"6" {set rv "FLOAT"}
"7" {set rv "REAL"}
"8" {set rv "DOUBLE"}
"12" {set rv "VARCHAR"}
"16" {set rv "BOOLEAN"}
"91" {set rv "DATE"}
"92" {set rv "TIME"}
"93" {set rv "TIMESTAMP"}
default {set rv "OBJECT"}
return $rv
proc oracleQuery { oraConnect oraQuery } {
set oraStatement [ $oraConnect createStatement ]
set oraResults [ $oraStatement executeQuery $oraQuery ]
# The following metadata dump is not required, but will be a helpfull sort of thing
# if ever want to really build an abstraction layer
set oraResultsMetaData [ $oraResults getMetaData ]
set columnCount [ $oraResultsMetaData getColumnCount ]
set i 1
#puts "ResultSet Metadata:"
while { $i <= $columnCount} {
set fname [ $oraResultsMetaData getColumnName $i]
set ftype [oraJDBCType [ $oraResultsMetaData getColumnType $i]]
#puts "Output Field $i Name: $fname Type: $ftype"
incr i
# end of metadata dump
return $oraResults
# SAMPLE CODE to run a quick query and dump the results. #
#set oraConn [ oracleConnect myserver orcl 1555 scott tiger ]
#set oraRs [ oracleQuery $oraConn "select name, count(*) numlines from user_source group by name" ]
#for each row in the result set
#while {[$oraRs next]} {
#grab the field values
# set procName [$oraRs getString name]
# set procCount [$oraRs getInt numlines]
# puts "Program unit $procName comprises $procCount lines"
#$oraRs close
#oracleDisconnect $oraConn
{code}
So you would want to connect to the control center, query for scheduled jobs, stop them, and then continue on with your deployment. I assume that you also need to pause and check that an scheduled job in mid-run has time to exit before moving ahead. You could do a sleep loop querying against system tables looking for active sessions running mappings and waiting until they are all done or something if you really want to bulletproof the process.
Hope this helps,
Mike

OMB plus Creating Locations Modules And Importing the Metadata?

Hi All,
First of all I would like to thank you all of you in advance for all your time and concern. I have serious of questions and I will ask them in 3 different portions as they are slightly different.
How can I implement the steps below using OMB plus? If you could provided sample script and notation it will be highly appreciated.
-- Creating an Oracle Location for a Schema and Registering it
-- Creating an Module and relating it to the location that was created.
-- Importing the metadata for all the objects in this Schema in to this module.
For example,
You have a schema called ORACLE_SRC. I need to create the location and module for this schema and tie them each other. Then I need to import all the metadata for all the objects in this ORACLE_SRC schema. During this import all the preserve statements should be unchecked. And I need to accomplish all these using OMB plus and TCL scripting.
-- Creating an Non Oracle (SQL server 2005) Location for a database and Registering it
-- Creating an Module and relating it to the location that was created.
-- Importing the metadata for all the objects in this Schema in to this module.
For example,
You have a schema called SQLSERVER_SRC. I need to create the location and module for this schema and tie them each other. Then I need to import all the metadata for all the objects in this SQLSERVER_SRC schema. During this import all the preserve statements should be unchecked. And I need to accomplish all these using OMB plus and TCL scripting.
-- Creating an Flat File Location for a folder structure and Registering it
-- Creating an Module and relating it to the location that was created.
For example,
You have a schema called FLATFILE_SRC. I need to create the location and module for this schema and tie them each other.
Thanks again for all your help and concern!
Kind Regards,
Mike

In addition to the performance issue above I have faced an extremely more important problem. When I have used the same logic for importing Materialized views I am getting an error at the last step of the script. It is exactly the same case also for EXTERNAL_TABLE objects. TABLE and VIEW objects are fine. OMBIMPORT command throw the error message below.
PUB04201: Encountered an internal fatal error during processing of oracle module XXX_DMY_DWPROD_TST: unsupported obj type.
I would like to mention that MATERIALIZED_VIEW is the object name I took from OWB scripting Reference guide. I have tried couple other naming conventions too but it didn't work.
Strange thing is If I were to change MATERIALIZED_VIEW to TABLE it works but the materialized view gets imported into 'Tables' folder under the module.
Please help?
     #IMPORT FOR MATERIALIZED VIEWS STARTS
#pull the names of the object inthe schema
     set MVIEWLIST {}
     set sqlStr "select distinct Mview_Name from all_mviews where owner = upper('$DbNm') order by Mview_Name"
     #execute the query
     set oraRs [oracleQuery $oraConn $sqlStr]
     #Loop through the list of objects
     while {[$oraRs next]} {
          set mvwName [$oraRs getString Mview_Name]
          lappend MVIEWLIST $mvwName
     #and close the query
     $oraRs close
     set listCntr 0
     set listTotal [llength $MVIEWLIST]
     set mviewName [lindex $MVIEWLIST $listCntr]
     #First object
     OMBALTER IMPORT_ACTION_PLAN 'IMPORT_ALL' ADD ACTION 'MAT_VIEWS' SET REF SOURCE MATERIALIZED_VIEW '$mviewName' SET REF TARGET ORACLE_MODULE '$ModNm'
     OMBCOMMIT
     puts "$mviewName is being imported"
     incr listCntr
     while {$listCntr<$listTotal} {
          #Rest of the objects
          set mviewName [lindex $MVIEWLIST $listCntr]
          incr listCntr
          OMBALTER IMPORT_ACTION_PLAN 'IMPORT_ALL' MODIFY ACTION 'MAT_VIEWS' SET REF SOURCE MATERIALIZED_VIEW '$mviewName' SET REF TARGET ORACLE_MODULE '$ModNm'
          OMBCOMMIT
          puts "$mviewName is being imported"
     set listCntr 0
     set listTotal 0
     #IMPORT FOR MATERIALIZED VIEWS ENDS
          OMBIMPORT FROM METADATA_LOCATION FOR IMPORT_ACTION_PLAN 'IMPORT_ALL'
          OMBDROP IMPORT_ACTION_PLAN 'IMPORT_ALL'

Quotes in OMB plus

Hi all,
I'm using OMB plus to add an expresion operator to an mapping .
I have a problem setting the expression property of an output attribute of this operator because the value of the expression has quotes in it.
I used the following command
OMBALTER MAPPING 'SWITCH_OUT' \
ADD EXPRESSION OPERATOR 'LAST_LOAD_DATE' \
ADD ATTRIBUTE 'MAPPING_NAME' OF GROUP 'INGRP1' OF OPERATOR 'LAST_LOAD_DATE' \
ADD ATTRIBUTE 'LOAD_DATE' OF GROUP 'OUTGRP1' OF OPERATOR 'LAST_LOAD_DATE' \
SET PROPERTIES (EXPRESSION) VALUES ('PCK_MANAGEMENT.GET_DATE(INGRP1.MAPPING_NAME,'LAST_LOAD_DATE')')
Can anybody help me?

you should be able to solve this by using an escape-character so in your case you use the '-sign twice and get VALUES 'PCK_MANAGEMENT.GET_DATE(INGRP1.MAPPING_NAME,''LAST_LOAD_DATE'')')

OMB Plus to set CDC properties of Oracle Module

Similar Messages

Maybe you are looking for