Stopping a scheduled job in OWB

I need to re-deploy a scheduled job and cannot do so because the job is running. How do I stop the job from the OWB control center (or elsewhere)?
Thanks,
Dave

Hi,
I don't know if there is an easier way but this should work:
1. run the script list_requests.sql (it should exist inside your owb home at owb\rtp\sql) using the workspace name as parameter
2. the job should be listed on the EXECUTIONS section
3. run the script deactivate_execution (same location as list_requests.sql) passing the audit_id and your workspace as parameteres
Regards,
Bruno

Similar Messages

How to stop a Scheduler Job in Oracle BI Publisher 10g

Hello!
Can someone tell me how can I stop a scheduler job in Oracle BI Publisher 10g?
I scheduled a bursting job to run a report but is running during two days.
I would like to stop it.
Thanks.
Edited by: SFONS on 19-Jan-2012 07:16

Unfortunately there is no way to stop a job once it is being executed. Yes as you read, it is not possible once job has started.
Same thing applies for running queries.
Once queries are sent to the DB BIP loses control over them. The message you see (if any) "Click Here to Cancel" does not stop any query
it is just a message.
I guess you will have to stop/kill the process in your DB
regards
Jorge
p.s If you consider your question answered then please mark my answer as *"Correct"* or *"Helpful"*

How do we stop the scheduled job ?

Hi all,
how do we stop the scheduled job if it is already been scheduled and running in the background.
please send your suggestions,
Rajesh.

Hi Rajesh
Each and every job is associated with a Job Number, you need to specify the exact number to extract the correct details.
Please check table: <b>TBTCO</b> for the same. For more details refer to tables of pattern TBTC*.
Kind Regards
Eswar

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

Scheduling jobs in OWB 10.2

I'm busy with a migration of OWB 10.1 to 10.2 and I had almost everything up and running
except
the scheduled jobs.
In 10.1 my predecessors made scheduled jobs which started in their turn a procedure which then started the process flow with wb_rt_api_exec.
After migration I could not get those jobs going anymore.
After investigation I could see that the procedures (starting the proess flows) ran when started with the runtime rrepository owner as launcher.
Even te jobs ran when they were started with the session credentials (iow the credentials from the logged on user being the runtime repository owner).
I've seen the atricles telling that you need to set the preferred credentials to the runtime repository owner in oem if you want to get it running from there.
Anyhow I could start it by recreating the jobs with the runtime repository owner as the creator.
Doens anybody know why it could run in owb 10.1 with sys as creator and why it nn longer works in 10.2.
I checked the 10.1 installation and I haven't found any priviileges granted to sys that where not granted in the 10.2 installation, so there is no diff.
Any help would be welcome.

Hi,
You cannot schedule direct mapping. You need create Process flow then u need to attach calendar for that. Go to Control Centre Deploy process flow and schedule and further click on start.
Regards,
Ava

BI Scheduler doesn't stop Publisher scheduled jobs

Hi guys!
We are facing the issue that we want to stop all Publisher scheduled jobs, so we went to "report job history" and marked all jobs as "cancelled". That jobs gets the status of "cancelling" but never stops. Any idea? We had restarted coreaplication server but it does not help.
Any workaround to "delete" that jobs?
Thanks for your time! Any help will be appreciated.
Regards,
Ariel

I am also facing same issue with BI Publisher Scheduler but showing below mentioned error while creating new job.
Error
"Job submission failed : Error occurred while scheduling the job. org.quartz.ObjectAlreadyExistsException: Unable to store Job with name: '-1' and group: 'weblogic', because one already exists with this identification."
Cheers.
Vishal

Not sure if my code is correct to stop a scheduled job.

I can do this to create a job and schedule it to run.
BEGIN
-- Job defined entirely by the CREATE JOB procedure.
DBMS_SCHEDULER.create_job (
job_name => 'test_Non_Compliance_email',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN test_app.PRC_NEMAIL(); END;',
start_date => SYSTIMESTAMP,
repeat_interval => 'freq=hourly; byminute=1',
end_date => NULL,
enabled => TRUE,
comments => 'Job defined entirely by the CREATE JOB procedure.');
END;
Can I do this to stop the job from running.
BEGIN
-- Job defined entirely by the CREATE JOB procedure.
DBMS_SCHEDULER.create_job (
job_name => 'test_Non_Compliance_email',
job_type => 'PLSQL_BLOCK',
job_action => 'BEGIN test_app.PRC_NEMAIL(); END;',
start_date => SYSTIMESTAMP,
repeat_interval => 'freq=hourly; byminute=1',
end_date => NULL,
enabled => FALSE,
comments => 'Job defined entirely by the CREATE JOB procedure.');
END;
Thanks
Howard

Second statement will create job in job system which will be disabled. Disabled jobs are ignored by scheduler and it means, your job will not run.
You can also use dbms_scheduler.enable() and dbms_scheduler.disable() to enable and disable jobs. If you disable currently running job, it will not be stopped.
To stop currently running job you can use dbms_scheduler.stop_job().

To stop a scheduled job

Hi ,
I have sheduled a job, that runs daily and now i need to stop that job from running past a particular date.
so, how do i stop the job from running past the date.

Go to SM37 -> Select the "released job" -> Change -> Start condition -> No Start After, Date: XXXXXX Time: XXXXXX
That should stop the job from getting released after the require date and time
Regards
Juan
PS:
@vamshi - Question is not related to delete jobs
@lolla - Question is not related to cancel any running jobs
@manoj - Question is not related to scheduling a job (job is already scheduled)
Please make sure you do not post missleading answers.

Scheduling jobs in owb

do schedule a mapping in owb should be use anything else apart from owb.
Cant we directly schedule using owb? rather than using oracle enterprise manager?
if yes,then how do i schedule a mapping ,i linked a schedule to the 'refered calender' column in configure option.
How do i run it ?

Hi,
You cannot schedule direct mapping. You need create Process flow then u need to attach calendar for that. Go to Control Centre Deploy process flow and schedule and further click on start.
Regards,
Ava

To stop all scheduling in Business Objects 4.0

Hi
I just want to stop all the scheduled reports to run in Business Objects
Which process should i stop for it ?
Is it Adaptive Job Processor?
This is why i need it
We have migrated our BO from 3.1 to 4.0 in UNIX environment so its a prod parallel environment
and we are going to keep the old production environment running too for a week just to test the new one is fine or no.
But for 4.0 we have new prod environment and new CMS database
Next we are going to get all the data using BO Upgrade Tool
As Unix has complete upgrade it will get all the scheduling info too
Now i don't want the reports to run in our old production environment and new too
So which process should i stop which will only stop the Scheduling and wont impact other part.

Priyanka,
You need to STOP the Adaptive Job Server, this will STOP all scheduling jobs.
Regards,
Ajay

How to delete Scheduled job

Hi all,
I have a problem that i was scheduled a job.
But i need to delete/stop that scheduled job.
I am new to this.
Can u anyone plz give me suggestion.
Thanks in advance
Venkat

IN SM37 select the job and press delete button.
or u can use fm..
try SCMA_DELETE_JOB.

How do I scdule jobs in OWB

I am a new user to OWB and not really sure how to schedule jobs thru OWB.
How do I specify a mapping to run every night at 1 AM ? Is there a Scheduler in OWB ?
Thanks,
Anna

If your environment does not use OEM, you can easily use the Oracle Jobs to run your OWB mappings or even Process Flows.
Check out the run_my_owb_stuff from
http://www.oracle.com/technology/sample_code/products/warehouse/index.html
You can easily create a stored procedure from this example and schedule the execution with dbms_jobs (or use what ever GUI you got to submit Oracle Jobs, e.g. Toad)
Hope this helps,
Borkur

Executing Scheduled jobs via Control Centre

Hello Forum,
We have a question on the scheduled jobs in OWB. We have some process flows that are attached to some (corresponding) schedules. Now in the Control Centre, we have two options to get the scheduled jobs executed:
1. We can have the scheduled jobs deployed, but not started, in which case the scheduled jobs would run as our Repository Owner (say OWB).
2. We can have the scheduled jobs deployed AND started, in which case the scheduled jobs would run as OWF (Oracle Workflow User).
(Just to clarify - by "starting" a scheduled job we mean that we make use of the "Start" option available in the right-click menu for every scheduled job that appears under the "Scheduled Jobs" node in the Control Centre.)
We would like to understand what is the advantage/disadvantage of setting up the scheduled jobs (for execution) for the two cases described above.
Any help is much appreciated.
Best Regards,
Piyush
For reference, following is our environment info:
OWB Client Version - 10.2.0.1.31
Repository Version - 10.2.0.1.0
Database Version - 10.2.0.3.0
OWF Version - 2.6.4
-----------------------------------------------------------------------------------------

Hi Sam,
Thanks a lot for your kind inputs. Well the situation that I have at hand is that when I don't "start" the schedules (as in Case 1. described in my earlier post), everything goes fine. However, if I "start" the schedules jobs (as in Case 2. described in my earlier post), the scheduled jobs failed to execute after DB restart. So I feel we are better off by not starting the scheduled jobs so as to make them run as our target workflow user.
Do you think this is the right approach for executing the scheduled jobs?
Best Regards,
Piyush

Schedule jobs

Hi,
i scheduled the job like below.
BEGIN
dbms_scheduler.create_job(
      job_name => 'SUMAARY_REPORT'
     ,job_type => 'PLSQL_BLOCK'
     ,job_action => 'BEGIN END;'
     ,start_date => trunc(sysdate)+4/24
     ,repeat_interval => 'FREQ=DAILY'
     ,enabled => TRUE
     ,comments => 'Demo for job schedule.');
end;But i need to run job for below scenarios.
1)i need to change job schedule time
2)i need to stop particular job for one day
3)manually need to whenever i want run
can some help on this?

DBMS_SCHEDULER.SET_ATTRIBUTE to change an attribute (for example to change the execution time)
DBMS_SCHEDULER.STOP_JOB to stop a scheduled job
DBMS_SCHEDULER.RUN_JOB to run a job immediatly
Link:http://download.oracle.com/docs/cd/B28359_01/appdev.111/b28419/d_sched.htm#CIHEHDHA
Max

Control Center status running scheduled jobs stops when DB is shutdown

I have scheduled jobs in the Control Center of OWB, and the status is "Running" (Green Arrow ->), but everytime we stop and start the database I have to start the schedule job again under Status.
Is there any way to fix this so that when the database stops and restarts somebody does not have to go into the Control Center and restart the jobs that are scheduled?
Thanks

I'm been told that it's a bug in the current version of OWB and to fix this problem we should upgrade to 10.2.0.3.

Stopping a scheduled job in OWB

Similar Messages

Maybe you are looking for