RE: warehouse builder's dependance on oem job system.
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 with the right runtime parameters in OWB. btw when use the method (forgot that name for passing parameters ) "=" u need now worry about parameter position. -Mandar -Original Message-From: Chris Stephens [mailto:[EMAIL PROTECTED]]Sent: Friday, December 13, 2002 8:38 AMTo: Multiple recipients of list ORACLE-LSubject: 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 and of the same # for every job? or is there some way to determine the order and position they should be when executing the package? thank you so much for your help. -Original Message- From: Mandar A. Ghosalkar [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 8:19 PM To: Multiple recipients of list ORACLE-L Subject: RE: warehouse builder's dependance on oem job system. 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 parList_i]] set p_bulk_size [lindex $parList [incr parList_i]] set p_purge_group [lindex $parList [incr parList_i]] set p_percentage [lindex $parList [incr parList_i]] and then the package.main is called try the following. i would recommend testing this on the test server before putting it on prod :-) sqlexec C40_ADMIN_CUSTOMER_MAP.Main(p_operating_mode = 3, p_audit_level = 2, p_max_errors = 50, p_commit_frequency = 1000, p_bulk_size = 50, p_job = 'wb'); -Mandar Original Message- Sent: Thursday, December 12, 2002 1:09 PM To: Multiple recipients of list ORACLE-L here is the tcl that was generated: "-r" "3,2,50,1000,50,wb,10" "-c" "WE8MSWIN1252" the package that is generated is quite long. i have absolutely no idea how to read the tcl. if you could point me somewhere, i could try and figure it out myself. any help is appreciated. attached is the package code if you are willing to take a look... (for some reason my computer associates .pls extensions with real audio) -Original Message- Sent: Tuesday, December 10, 2002 1:11 PM To: Multiple recipients of list ORACLE-L 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 parameters for the owb-oem job. You could paste the tcl and the parameters here to help u more. -Mandar -Original Message- Sent: Tuesday, December 10, 2002 9:31 AM To: Multiple recipients of list ORACLE-L 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mandar A. Ghosalkar INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB
RE: warehouse builder's dependance on oem job system.
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 and of the same # for every job? or is there some way to determine the order and position they should be when executing the package? thank you so much for your help. -Original Message- From: Mandar A. Ghosalkar [mailto:[EMAIL PROTECTED]] Sent: Thursday, December 12, 2002 8:19 PM To: Multiple recipients of list ORACLE-L Subject: RE: warehouse builder's dependance on oem job system. 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 parList_i]] set p_bulk_size [lindex $parList [incr parList_i]] set p_purge_group [lindex $parList [incr parList_i]] set p_percentage [lindex $parList [incr parList_i]] and then the package.main is called try the following. i would recommend testing this on the test server before putting it on prod :-) sqlexec C40_ADMIN_CUSTOMER_MAP.Main(p_operating_mode = 3, p_audit_level = 2, p_max_errors = 50, p_commit_frequency = 1000, p_bulk_size = 50, p_job = 'wb'); -Mandar Original Message- Sent: Thursday, December 12, 2002 1:09 PM To: Multiple recipients of list ORACLE-L here is the tcl that was generated: -r 3,2,50,1000,50,wb,10 -c WE8MSWIN1252 the package that is generated is quite long. i have absolutely no idea how to read the tcl. if you could point me somewhere, i could try and figure it out myself. any help is appreciated. attached is the package code if you are willing to take a look... (for some reason my computer associates .pls extensions with real audio) -Original Message- Sent: Tuesday, December 10, 2002 1:11 PM To: Multiple recipients of list ORACLE-L 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 parameters for the owb-oem job. You could paste the tcl and the parameters here to help u more. -Mandar -Original Message- Sent: Tuesday, December 10, 2002 9:31 AM To: Multiple recipients of list ORACLE-L 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mandar A. Ghosalkar INET: [EMAIL PROTECTED] Fat City Network Services -- 858-538-5051 http://www.fatcity.com San Diego, California -- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
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 via cron for months without any issues, other than the fact that we can't multitask. Mandar A. Ghosalkar wrote: 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 parList_i]] set p_bulk_size [lindex $parList [incr parList_i]] set p_purge_group [lindex $parList [incr parList_i]] set p_percentage [lindex $parList [incr parList_i]] and then the package.main is called try the following. i would recommend testing this on the test server before putting it on prod :-) sqlexec C40_ADMIN_CUSTOMER_MAP.Main(p_operating_mode = 3, p_audit_level = 2, p_max_errors = 50, p_commit_frequency = 1000, p_bulk_size = 50, p_job = 'wb'); -Mandar Original Message- Sent: Thursday, December 12, 2002 1:09 PM To: Multiple recipients of list ORACLE-L here is the tcl that was generated: -r 3,2,50,1000,50,wb,10 -c WE8MSWIN1252 the package that is generated is quite long. i have absolutely no idea how to read the tcl. if you could point me somewhere, i could try and figure it out myself. any help is appreciated. attached is the package code if you are willing to take a look... (for some reason my computer associates .pls extensions with real audio) -Original Message- Sent: Tuesday, December 10, 2002 1:11 PM To: Multiple recipients of list ORACLE-L 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 parameters for the owb-oem job. You could paste the tcl and the parameters here to help u more. -Mandar -Original Message- Sent: Tuesday, December 10, 2002 9:31 AM To: Multiple recipients of list ORACLE-L 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mandar A. Ghosalkar INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it. - Tom Lehrer. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
RE: warehouse builder's dependance on oem job system.
true they hv default values, but i think the Chris's runtime parameters are diff than his default values. ill try to give another look at it come monday. -Original Message- From: Scott Canaan [mailto:[EMAIL PROTECTED]] Sent: Friday, December 13, 2002 10:39 AM To: Multiple recipients 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 via cron for months without any issues, other than the fact that we can't multitask. Mandar A. Ghosalkar wrote: 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 parList_i]] set p_bulk_size [lindex $parList [incr parList_i]] set p_purge_group [lindex $parList [incr parList_i]] set p_percentage [lindex $parList [incr parList_i]] and then the package.main is called try the following. i would recommend testing this on the test server before putting it on prod :-) sqlexec C40_ADMIN_CUSTOMER_MAP.Main(p_operating_mode = 3, p_audit_level = 2, p_max_errors = 50, p_commit_frequency = 1000, p_bulk_size = 50, p_job = 'wb'); -Mandar Original Message- Sent: Thursday, December 12, 2002 1:09 PM To: Multiple recipients of list ORACLE-L here is the tcl that was generated: -r 3,2,50,1000,50,wb,10 -c WE8MSWIN1252 the package that is generated is quite long. i have absolutely no idea how to read the tcl. if you could point me somewhere, i could try and figure it out myself. any help is appreciated. attached is the package code if you are willing to take a look... (for some reason my computer associates .pls extensions with real audio) -Original Message- Sent: Tuesday, December 10, 2002 1:11 PM To: Multiple recipients of list ORACLE-L 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 parameters for the owb-oem job. You could paste the tcl and the parameters here to help u more. -Mandar -Original Message- Sent: Tuesday, December 10, 2002 9:31 AM To: Multiple recipients of list ORACLE-L 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mandar A. Ghosalkar INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Scott Canaan ([EMAIL PROTECTED]) (585) 475-7886 Life is like a sewer, what you get out of it depends on what you put into it. - Tom Lehrer. -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Scott Canaan INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from
RE: warehouse builder's dependance on oem job system.
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 parList_i]] set p_bulk_size [lindex $parList [incr parList_i]] set p_purge_group [lindex $parList [incr parList_i]] set p_percentage [lindex $parList [incr parList_i]] and then the package.main is called try the following. i would recommend testing this on the test server before putting it on prod :-) sqlexec C40_ADMIN_CUSTOMER_MAP.Main(p_operating_mode = 3, p_audit_level = 2, p_max_errors = 50, p_commit_frequency = 1000, p_bulk_size = 50, p_job = 'wb'); -Mandar Original Message- Sent: Thursday, December 12, 2002 1:09 PM To: Multiple recipients of list ORACLE-L here is the tcl that was generated: -r 3,2,50,1000,50,wb,10 -c WE8MSWIN1252 the package that is generated is quite long. i have absolutely no idea how to read the tcl. if you could point me somewhere, i could try and figure it out myself. any help is appreciated. attached is the package code if you are willing to take a look... (for some reason my computer associates .pls extensions with real audio) -Original Message- Sent: Tuesday, December 10, 2002 1:11 PM To: Multiple recipients of list ORACLE-L 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 parameters for the owb-oem job. You could paste the tcl and the parameters here to help u more. -Mandar -Original Message- Sent: Tuesday, December 10, 2002 9:31 AM To: Multiple recipients of list ORACLE-L 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Mandar A. Ghosalkar INET: [EMAIL PROTECTED] Fat City Network Services-- 858-538-5051 http://www.fatcity.com San Diego, California-- Mailing list and web hosting services - To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
warehouse builder's dependance on oem job system.
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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks
RE: warehouse builder's dependance on oem job system.
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 parameters for the owb-oem job. You could paste the tcl and the parameters here to help u more. -Mandar -Original Message-From: Chris Stephens [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 10, 2002 9:31 AMTo: Multiple recipients of list ORACLE-LSubject: 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks
RE: warehouse builder's dependance on oem job system.
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 scheduling yet, so Id be interested to hear your solution once you find it. Best regards, David B. Wagoner Database Administrator Arsenal Digital Solutions Worldwide, Inc. 8000 Regency Parkway, Suite 100 Cary, NC 27511-8582 Office (919) 466-6723 Mobile (919) 412-8462 Pager [EMAIL PROTECTED] Fax (919) 466-6783 AIM adswDavid http://www.arsenaldigital.com/ *** NOTICE *** This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender by phone or email and delete this e-mail message from your computer. Thank you. -Original Message- From: Chris Stephens [mailto:[EMAIL PROTECTED]] Sent: Tuesday, December 10, 2002 12:31 PM To: Multiple recipients of list ORACLE-L Subject: 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks
RE: warehouse builder's dependance on oem job system.
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-From: Chris Stephens [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 10, 2002 11:31 AMTo: Multiple recipients of list ORACLE-LSubject: 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks
RE: warehouse builder's dependance on oem job system.
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 that though. ...we don't really need owf as of yet. also oracle support provided me with the following note: Note: 91833.1 i'll let you know how it turns out. -Original Message-From: David Wagoner [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 10, 2002 1:15 PMTo: Multiple recipients of list ORACLE-LSubject: RE: 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 scheduling yet, so Id be interested to hear your solution once you find it. Best regards, David B. Wagoner Database Administrator Arsenal Digital Solutions Worldwide, Inc. 8000 Regency Parkway, Suite 100 Cary, NC 27511-8582 Office (919) 466-6723 Mobile (919) 412-8462 Pager [EMAIL PROTECTED] Fax (919) 466-6783 AIM adswDavid http://www.arsenaldigital.com/ *** NOTICE *** This e-mail message is confidential, intended only for the named recipient(s) above and may contain information that is privileged, work product or exempt from disclosure under applicable law. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender by phone or email and delete this e-mail message from your computer. Thank you. -Original Message-From: Chris Stephens [mailto:[EMAIL PROTECTED]]Sent: Tuesday, December 10, 2002 12:31 PMTo: Multiple recipients of list ORACLE-LSubject: 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. for obvious reasons we need to be able to schedule these jobs. the only way (that i know of) to schedule the owb jobs is to deploy them to entreprise manager. the problem is that our oem is VERY unreliable and seems to be related to bugs. we are running oem v9.2 and oracle ee v9.2. when jobs are scheduled through oem, they run sometimes and hang others. this is unexceptable. so my question is: does anyone know of a way to trap the commands that oem sends to the database? the obvious solution would be to just cron execution of the packages owb generates inside the database. this doesn't work though because owb generates funky code that takes parameters, whose values i don't know, for logging purposes. hopefully i explained the situation well enough. any ideas??i'd like to get rid of the dependance on oem. oem sucks
