RE: warehouse builder's dependance on oem job system.

2002-12-16 Thread Mandar A. Ghosalkar
Title: RE: warehouse builder's dependance on oem job system. Chris, if its a plsql job then tcl wrapper script in oem would be same. but your runtime parameters could be diff. As others have mentioned, u could just run package.main, just verify that the package has been configured

RE: warehouse builder's dependance on oem job system.

2002-12-13 Thread Chris Stephens
Title: RE: warehouse builder's dependance on oem job system. wow. thank you. i will be testing this in the afternoon but before i do, i have one more question. we have ~50 jobs we would like to cron instead of submit to oem. so my question is, are these tcl arguments in the same order

Re: warehouse builder's dependance on oem job system.

2002-12-13 Thread Scott Canaan
I run the jobs via cron, without any parameters and we don't have any problems. If you look at the parameter list, you'll find that most (if not all) have default values anyway. I have been running them via cron for months without any issues, other than the fact that we can't multitask.

RE: warehouse builder's dependance on oem job system.

2002-12-13 Thread Mandar A. Ghosalkar
of list ORACLE-L Subject: Re: warehouse builder's dependance on oem job system. I run the jobs via cron, without any parameters and we don't have any problems. If you look at the parameter list, you'll find that most (if not all) have default values anyway. I have been running them

RE: warehouse builder's dependance on oem job system.

2002-12-12 Thread Mandar A. Ghosalkar
Chris, the parameters 3,2,50,1000,50,wb,10 are used inside the oem-owb job tcl script as set p_oper_mode [lindex $parList [incr parList_i]] set p_audit_level [lindex $parList [incr parList_i]] set p_num_errors [lindex $parList [incr parList_i]] set p_commit_frequency [lindex $parList [incr

warehouse builder's dependance on oem job system.

2002-12-10 Thread Chris Stephens
Title: warehouse builder's dependance on oem job system. ok, here's the situation: we are loading our warehouse via etl processes generated by warehouse builder (owb). we went live with this a little over a week ago. up to this point we have been running the jobs manually through owb

RE: warehouse builder's dependance on oem job system.

2002-12-10 Thread Mandar A. Ghosalkar
Title: warehouse builder's dependance on oem job system. Chris, All the owb etl jobs are packages and if you have configured it right, then you could the execute the package_name.main procedure to run the etl process. your best best would be to read the tcl script and the associated

RE: warehouse builder's dependance on oem job system.

2002-12-10 Thread David Wagoner
Title: warehouse builder's dependance on oem job system. You may have implied this in your message, but are you using Oracle Workflow in conjunction with OEM? That is the scheduling method that is taught in the OWB class by Oracle. I am currently learning OWB but have not setup

RE: warehouse builder's dependance on oem job system.

2002-12-10 Thread Chris Stephens
Title: warehouse builder's dependance on oem job system. after reading this over again, i'm not sure i was very clear on this. to paraphrase: does anyone know a way to schedule runs of owb generated code without the use of oem? thank you very much for any help. -Original Message

RE: warehouse builder's dependance on oem job system.

2002-12-10 Thread Chris Stephens
Title: warehouse builder's dependance on oem job system. no we aren't using workflow. last time i checked, that was very buggy too. i.e. the dependancies could not be verified so all the jobs executed regardless of whether or not the conditions of execution were met. i could be wrong about