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

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"*

Scheduler doesn't create Jobs

Hello folks!
We have scheduled some reports with BI Publisher Scheduler in our Development Enviroment and works very fine. But when we passed that reports to Prod Enviroment, BI Publisher scheduler doesn't create any Job (verified in Report Job History and XMLP/QRTZ tables in Database Schema that isn't any Job created). There isn't any error, exception or message, only scheduler doesn't create Jobs.
Any idea, solution or way to find any trail about that problem?
Thanks for your preciated time spent in our issue.
Best Regards,
Martín

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

How to stop a running job in 10g Scheduler?

The following is a duplicate post. I posted the following to the general database forum before seeing that otn has a new scheduler forum:
I am not able to find in the Admin Guide a method to stop a currently running instance of a job in the 10g scheduler.
In 9i, I run the following script calling DBMS_JOB.broken and DBMS_JOB.remove to shut down currently running jobs:
DECLARE
jobid NUMBER;
CURSOR c1
IS
SELECT job
FROM dba_jobs
WHERE priv_user = 'ME';
BEGIN
OPEN c1;
LOOP
FETCH c1
INTO jobid;
EXIT WHEN c1%NOTFOUND;
DBMS_JOB.broken (jobid, TRUE);
COMMIT;
DBMS_JOB.remove (jobid);
COMMIT;
END LOOP;
CLOSE c1;
END;
How may I create similar code to shut down currently running jobs using DBMS_SCHEDULER in 10g? According to the Admin Guide, disabling jobs with the force option will still allow the job to finish.
How can I terminate a running job in 10g?

You can stop a currently running job using the STOP_JOB api.
STOP_JOB Procedure
This procedure stops currently running jobs or all jobs in a job class. Any instance of the job will be stopped. After stopping the job, the state of a one-time job will be set to SUCCEEDED whereas the state of a repeating job will be set to SCHEDULED or COMPLETED depending on whether the next run of the job is scheduled.
Syntax
DBMS_SCHEDULER.STOP_JOB (
job_name IN VARCHAR2
force IN BOOLEAN DEFAULT FALSE);
Parameters
Table 83-44 STOP_JOB Procedure Parameters
Parameter Description
job_name
The name of the job or job class. Can be a comma-delimited list. For a job class, the SYS schema should be specified.
If the name of a job class is specified, the jobs that belong to that job class are stopped. The job class is not affected by this call.
force
If force is set to FALSE, the Scheduler tries to gracefully stop the job using an interrupt mechanism. This method gives control back to the slave process, which can update the status of the job in the job queue to stopped. If this fails, an error is returned.
If force is set to TRUE, the Scheduler will immediately terminate the job slave. Oracle recommends that STOP_JOB with force set to TRUE be used only after a STOP_JOB with force set to FALSE has failed.
Use of the force option requires the MANAGE SCHEDULER system privilege.
Setting force to TRUE is not supported for jobs of type executable.
Usage Notes
STOP_JOB without the force option requires that you be the owner of the job or have ALTER privileges on that job. You can also stop a job if you have the CREATE ANY JOB or MANAGE SCHEDULER privilege.
STOP_JOB with the force option requires that have the MANAGE SCHEDULER privilege.

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

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().

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

If your Scheduled Delivery apps stopped printing

These instructions apply to the Photosmart D110a and Officejet 6500A, 7500A, 8500A printers, but other printer models may be similar.
The Solutions below can be used to restore scheduled delivery printing that has failed. Some situations to which they may apply are:
-Scheduled Delivery apps unexpectedly stopped printing.
-Print jobs show Pending, Failed and/or Canceled on ePrintCenter History.
-Communication error when selecting Apps on the printer front panel.
-Communication error when Print Now of a scheduled app is attempted.
-Communication error caused by no internet connection, printer turned off for extended period of time, out of paper, out of ink.
If your Scheduled Delivery apps unexpectedly stopped printing, do the following:
Solution 1
Check the Scheduled Delivery Bulletin Board for the current status. If that doesn’t solve your problem, continue to Solution 2 below.
Solution 2
Photosmart D110a:
     a. Press the wireless button on the front; it should have a solid blue light. Flashing indicates NO wireless connection.
     b. On the front panel scroll down to Web Services Settings and press OK.
     c. On the front panel scroll down to Print Info Page and press OK.
Officejet 6500A, 7500A, 8500A:
     a. On the front panel, arrow to the right to the “Setup” icon and select.
     b. On the front panel, select Web Services Setup.
     c. On the front panel, select Printer Email Address.
Then follow these steps for all printers:
A page prints, titled Welcome to Web-Enabled, Mobile Printing from HP. This may take a few minutes; please be patient.
If you have Pending scheduled print jobs, they should print soon.
Your problem should now be fixed and automatic Scheduled Delivery should resume. Some jobs may have been lost as a result of the disruption that has occurred.
If your scheduled prints have not resumed in 24 hours, proceed to Solution 3.
Solution 3
Note: The following solution will restore your printer to its default apps, All scheduled print apps and jobs will be lost.
Remove/re-enable Web Services:
      Photosmart D110a:
       a. Press the wireless button on the front; it should have a solid blue light. Flashing indicates NO wireless connection.
       b. On the front panel scroll down to Web Services Settings and press OK.
       c. Scroll down to Remove Web Services and press OK, then OK again.
       d. Enable Web Services appears. Press OK, accept terms by pressing OK again, and enable by pressing OK.
      Officejet 6500A, 7500A, 8500A:
      On the front panel-
       a. Arrow to the right to the Setup icon and select.
       b. Select Web Services Setup.
       c. Scroll down to Restore Factory Settings and press Yes, then OK.
       d. Select the Apps icon and follow the prompts to Enable Web Services.
      Officejet 8600A:
      On the front panel-
       a.  On the main screen, upper left, press the “page with blue circles” icon.
       b.  Web Services Summary opens. At the bottom left, press Settings.
       c. Scroll down to the bottom. Press Remove Web Services. Yes.
       d. Press the Apps icon and follow the prompts to Enable Web Services.
2.   The printer should connect and print your Welcome Page with your printer ID and instructions to register the printer at the ePrintCenter. The printer ID expires after 24 hrs so be sure to register as soon as possible. Repeat above if needed.
3.   After registering the printer on EPrintCenter:
       a. Select Get APPS at the top of the webpage.
       b. Browse to Universal Crossword or other scheduled delivery app.
       c. Select icon and Add to Printer.
       d. Select Setup to schedule delivery.
You then should receive your scheduled delivery prints on the following day that the publication is available. (Please note that if it is 10 am when you install the print app and you select a delivery time of 11 am you will have to wait until the following day at 11 am to receive a scheduled delivery print. You can perform a Print Now to receive the current publication.)
If these steps don't solve your problem, post a reply to this message or create a new Forum post with a specific question, including Scheduled Delivery in the title field followed by the issue. Example: Scheduled Delivery .......(insert issue here).......
I work on behalf of HP.

mry,
You should post your question in the Ask a Question box on the Post Install Printing Issues Forum at this location:
http://h30434.www3.hp.com/t5/Post-Install-Printing-Issues-New/bd-p/PostPrint
You can copy your original message and paste it there.
Include a Subject something like this: <Model of your printer>: Copy issue
I work on behalf of HP.

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

Jobs Scheduled But Never Run or EM jobs remain in 'running' status

Hi All,
Please I need help on this: I have job scheduled through Oracle Enterprise Manager (OEM) but each time our Windows server is shutdown for patches update the job I scheduled failed and in the status column it shows that the job is still running ( Note: I do know how to stop/delete this job) BUT I will like to know if there's anything I need to do so that each time our server is shutdown the scheduled job will not fail to run.
Thanks
Wale

Jobs Scheduled But Never Run or EM jobs remain in 'running' status what is the output of user_jobs and user_jobs_running views when this happens? especially last_date, last_sec, failures, broken columns.

BI Publisher Scheduling Problem

Hi Experts,
Our BI Publisher is currently integrated with siebel, whenever i tried generating 35k records bip report via manual generation in siebel, it completed successfully, however when i tried generating it via bip scheduling it fails. Do you have any idea why this is happening? note that if i generate less number of records bip scheduler successfully generated the report. Hope you could help me on this.
Thanks in Advance!

hope this helps
if u have meta link u can check this document (ID 1359304.1) regarding this error
and now recent is a bug .[ID 1430802.1] so it is a bug u were hitting
Symptoms
Siebel BI Publisher Scheduled Report jobs that use large data set (mostly over 10000 rows) fail with XDO error on the BI Publisher Server:
[111511_135636875][oracle.apps.xdo.servlet.scheduler.XDOJob][EXCEPTION] [ID:904]
Exception occurred while processing the document.
oracle.apps.xdo.servlet.scheduler.ProcessingException: oracle.apps.xdo.servlet.d
ata.DataException: Requested data type does not match with existing data type
at oracle.apps.xdo.servlet.scheduler.XDOJob.generateReport(XDOJob.java:9
83)
at oracle.apps.xdo.servlet.scheduler.XDOJob.execute(XDOJob.java:418)
at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.j
ava:520)
Caused by: oracle.apps.xdo.servlet.data.DataException: Requested data type does
not match with existing data type
Cause
The issue occurs when a Siebel BIP Report based on an Integration Component that has more than 20 Integration Component Fields and processing over 20000-30000 records is run as a Scheduled Job on the BI Publisher server. This behavior can be reproduced with out-of-box reports also, provided the Integration Component has more than 20 fields.
A Product Bug:13398030 has been logged to request a fix in the future release of Siebel CRM.
Solution
Workaround
The report can be run in interactive/ real-time mode rather than running as a scheduled job.
NOTE: Please implement the solution as documented in the Document 1064043.1 to be able to run large data volume reports.
For document 1064043.1 this is the link https://support.oracle.com/epmos/faces/ui/km/DocumentDisplay.jspx?_afrLoop=560666563922074&id=1064043.1&_afrWindowMode=0&_adf.ctrl-state=j5m2csomr_120
Permanent Solution
The fix for this issue will be released in the Siebel CRM 8.1.1.9 Fix Pack.
Edited by: Avinash_Varma on Mar 18, 2013 12:38 PM

How to stop the schedule pakage

Hai Experts,
I have scheduled a package for print process at hourly basis and now i would like to stop the job.so how to do tht.i tried by going to scheduling tab but unable to find to delete the job schedule process .so how to do tht..?
Thanks in advance..
Suri

hai Roberto,
thnks fr u r reply .
but i sm37 i can stop the active jobs only only but my jb is not in active status.so how to proceed and one more thing is i would like to stop my job permanently not for temporary.
as we can see the scheduled /released / active /ready /finished jobs in sm37 but all this we can see when the job have started ..so i want my job to stop permanently.
hope u understand my problem..
Regards,
Suri

Scheduling of process chain with background job

Hello All,
I have scheduled the process chains through background jobs. I have copied the meta chain and created seven background jobs that is from Monday till sunday. The problem is most frequently the job gets cancelled with the message
Process CHAIN, variant PAA1_GS001 is not scheduled waiting for event RSPROCESS 44NRPDWZ7CQUJ92ATDTY6368H.
This is the variant for the next process after the start process. I tried by giving merge active versions, but one day the background job runs fine , but the next day it gets cancelled.
If anyone has faced this issue before kindly let me know.
Regards,
Karthik.

Hi,
It seems to be there may be in probelm in Varients, so create a separate Varient for each PC and then activate the PC and execute.
Thanks
Reddy

BI Publisher Scheduling Error

Hi Experts,
i scheduled some of my BIP reports integrated with siebel. I Notice that if i schedule a report to genreate a 1.5k+ records i always received this kind of error :
oracle.apps.xdo.servlet.scheduler.ProcessingException: oracle.apps.xdo.servlet.data.DataException: Requested data type does not match with existing data type
     at oracle.apps.xdo.servlet.scheduler.XDOJob.generateReport(XDOJob.java:983)
     at oracle.apps.xdo.servlet.scheduler.XDOJob.execute(XDOJob.java:418)
     at org.quartz.core.JobRunShell.run(JobRunShell.java:195)
     at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:520)
Caused by: oracle.apps.xdo.servlet.data.DataException: Requested data type does not match with existing data type
     at oracle.apps.xdo.servlet.data.server.DefaultDataSet.getString(DefaultDataSet.java:178)
     at oracle.apps.xdo.servlet.data.bind.WebServiceBoundValue11.getValue(WebServiceBoundValue11.java:173)
     at oracle.apps.xdo.servlet.ReportContextImplV11.getReportXMLData(ReportContextImplV11.java:413)
     at oracle.apps.xdo.servlet.CoreProcessor.processScheduledRequest(CoreProcessor.java:362)
     at oracle.apps.xdo.servlet.CoreProcessor.generateScheduledDocument(CoreProcessor.java:114)
     at oracle.apps.xdo.servlet.ReportImpl.renderScheduledJob(ReportImpl.java:357)
     at oracle.apps.xdo.servlet.scheduler.XDOJob.generateReport(XDOJob.java:977)
... 3 more
Do you have any idea what can be the solution to solve this issue?

check this link BI Publisher Scheduling Problem

SSIS Package Fails when Scheduled as a SQL Server Agent Job

I have an SSIS package that runs without any problems when executed through BIDS.
However, when I schedule the SSIS as an Agent job, it fails completely or part way through. When it partially runs, the part that it is failing on is a Script Task that moves the source data file to an archive folder (on the same server).
I have tried using my domain account as the owner of the job, then the job fails straight off and I get an error:
Unable to determine if the owner (Domain\MyID) of job JobName has server access (reason: Could not obtain information about Windows NT group/user 'Domain\MyID'
If I change the owner to the 'sa' account , then the job partially runs, but then fails because 'sa' is a SQL account and does not have access to the filesystem.
I have managed to get it to work by using the SQL2008_Local account and granting modify permissions to the affected folders.
My question is - what is the advised way of doing this?
Thanks
Gary

Hi Garyv.King,
When you see a SSIS package fails running in a SQL Agent job, you need to first consider the following conditions:
1. The user account that is used to run the package under SQL Server Agent differs from the original package author.
2. The user account does not have the required permissions to make connections or to access resources outside the SSIS package.
For more detailed information about the issue, please following this KB article:
An SSIS package does not run when you call the SSIS package from a SQL Server Agent job step
http://support.microsoft.com/kb/918760
You can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues.
The following 4 issues are common encountered in the SSIS forum.
1. The package's Protection Level is set to EncryptSensitiveWithUserKey but your SQL Server Agent service account is different from the SSIS package creator.
2. Data source connection issue.
3. File or registry access permission issue.
4. No 64-bit driver issue.
For more information about it, please see:
How do I troubleshoot SSIS packages failed execution in a SQL Agent job:
http://social.technet.microsoft.com/Forums/en-US/sqlintegrationservices/thread/e13c137c-1535-4475-8c2f-c7e6e7d125fc
Thanks,
Eileen

BI Scheduler doesn't stop Publisher scheduled jobs

Similar Messages

Maybe you are looking for