ODI Job Scheduling via Control-M

Are there any docs/guidelines on how to schedule ODI jobs using BMC Control-M?
Thanks,
Paul Johnson
[VLDB Solutions|http://www.vldbsolutions.com ]

I'm not sure...
but I've worked with Control-M and ODI few years ago.
If I remember well finally I have created bat files which run my scenarios (calling odistartscen tools) and Control-M was scheduling execution of these bat files...
Hope to help.
Brice

Similar Messages

Issues while sending automatic email from job scheduled via sm36

Dear basis guys,
We are on Netweaver 2004s, ERP 6 .
I am scheduling (in SM36) a standard report output as background job, send its output to a pdf device and send this pdf automatically to email address. Everything is working fine except that I am not able to do the following:
1. Cannot change the email title (APR****-spool request no.) and body from "The Mail Attachment Contains the Print File Created by User..."
2. I need to send the email to several people. Cannot use the distribution list with the pdf device. IF I use in sm36 "spool list recipients" instead, the attachment sent as pdf will result truncated. Not all report lines will show.
Could someone help on any of the above?
Thank you in advance for any input.

Dear basis guys,
We are on Netweaver 2004s, ERP 6 .
I am scheduling (in SM36) a standard report output as background job, send its output to a pdf device and send this pdf automatically to email address. Everything is working fine except that I am not able to do the following:
1. Cannot change the email title (APR****-spool request no.) and body from "The Mail Attachment Contains the Print File Created by User..."
2. I need to send the email to several people. Cannot use the distribution list with the pdf device. IF I use in sm36 "spool list recipients" instead, the attachment sent as pdf will result truncated. Not all report lines will show.
Could someone help on any of the above?
Thank you in advance for any input.

Backing up Jobs, Chains and Programs in Oracle Job Scheduler

What is the best way to back up Jobs, Chains and Programs created in the Oracle Job Scheduler via Enterprise Manager - and also the best way to get them from one database to another. I am creating quite a long chain which executes many programs in our test database and wish to back everything up along the way. I will also then need to migrate to the production database.
Thanks for any advice,
Susan

Hi Susan,
Unfortunately there are not too many options.
To backup a job you can use dbms_scheduler.copy_job. I believe EM has a button called "create like" for jobs and programs but I am not sure about chains and this can be used to create backups as well.
A more general purpose solution which should also cover chains is to do a schema-level export using expdp i.e. a dump of an entire schema.
e.g.
SQL> create directory dumpdir as '/tmp';
SQL> grant all on directory dumpdir to public;
# expdp scott/tiger DUMPFILE=scott_backup.dmp directory=dumpdir
You can then import into a SQL text file e.g.
# impdp scott/tiger DIRECTORY=dumpdir DUMPFILE=scott_backup SQLFILE=scott_backup.out
or import into another database (and even another schema) e.g.
# impdp scott/tiger DIRECTORY=dumpdir DUMPFILE=scott_backup
Hope this helps,
Ravi.

Third party Job Scheduling?

Hi P6 Guru.
Our customer is looking for the solution of job scheduling to control the jobs for P6 Web services API programs with other Web services programs outside P6. Some jobs would be triggered by scheduled date&time, some would be triggered by success states of predecessor jobs.
IBM Tivoli workload scheduler(TWS), HP OpenView are what I can image easily for the solution. But I'm wondering it is popular to use such kind of system.
Do you have any experiences or idea about how you or your customers control the job scheduling of running tasks or programs?

AppWorx, now UC4, is one possibility but there is little, if anything, they can do that can not be done through the proper use of the DBMS_SCHEDULER package.
I would suggest that, before you spend or waste money, you look at the docs on DBMS_SCHEDULER and determine that there is something you need that you have not already purchased. Using OEM to schedule jobs is far from giving you access to the full functionality.

How to Schedule Job using Database Control for SQLPLUS script?

Hi All,
I am using Database version 10.2. I would like to schedule a SQLPLUS script job using Database control (Not using Grid Control!). The following is the script.
========================================================
define OEM_FRIENDLY=1
define OWB_BACKGROUND=0
set serveroutput on
set verify off
whenever sqlerror exit failure;
define REPOS_OWNER='&1.'
define LOCATION_NAME='&2.'
define TASK_TYPE='&3.'
define TASK_NAME='&4.'
define SYSTEM_PARAMS='&5.'
define CUSTOM_PARAMS='&6.'
alter session set current_schema = &REPOS_OWNER.;
set role owb_d_&REPOS_OWNER., owb_o_&REPOS_OWNER.;
variable exec_return_code number;
begin
-- Initialize Return Code
:exec_return_code := wb_rt_api_exec.RESULT_FAILURE;
-- Run Task
:exec_return_code := wb_rt_api_exec.run_task('&LOCATION_NAME.',
'&TASK_TYPE.',
'&TASK_NAME.',
'&CUSTOM_PARAMS.',
'&SYSTEM_PARAMS.',
&OEM_FRIENDLY.,
&OWB_BACKGROUND.);
end;
exit :exec_return_code;
===========================================================
Is it possible to schedule SQLPLUS script with 6 different parameters? If yes then how can I schedule for monday to friday or only for Saturday and sundays.
Please provide brief steps.
Thanks for your help in advance.
- Mehul

Let me explain to you about scheduler.
You can schedule a pl/sql stored procedure TEST_S as follows...
Begin
dbms_scheduler.create_job(
job_name=>'MY_JOB',
Job_Type=>'STORED_PROCEDURE',
job_action=>'TEST_S',
start_date=>sysdate,
repeat_interval=>'freq=monthly;BYDAY=MON,TUE,WED,THU,FRI',
end_date=>null');
END;
You can also also execute o/s script like .bat or .sh. For this job type should be EXECUTABLE.
Example of converting a .sql script in .bat script...
insert.sql
insert into dept values(50,'IT','LONDON');
exit
insert.bat
sqlplus scott/tiger @insert.sql
Executing now...
C:\Documents and Settings>insert.bat
C:\Documents and Settings>sqlplus scott/tiger @insert.sql
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Mar 1 08:01:00 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production
With the Partitioning, OLAP and Data Mining options
1 row created.
Disconnected from Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - P
oduction
With the Partitioning, OLAP and Data Mining options
C:\Documents and Settings>
So first read about DBMS_SCHEDULER and do the work in prompt. Then you can go and schedule it even by database control.
Scheduling by database control...
http://www.oracle.com/technology/oramag/oracle/04-jul/o44tech_dba.html
Scheduler
http://download-uk.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_sched.htm#CIHEHDHA
PS: By default each job you created is disable state. Please enable it by enable procedure of DBMS_SCHEDULER package.

Error in tabstrip control progtram while in Background job scheduling

Hi ABAPer's,
I need some help...I developed one tabstriip control program with 3 tabs. while excute it in foregroung it is executing nice..but while i am job scheduling the same program in background it was getting error's like .........
Control Framework: Fatal error - GUI cannot be reached
SET SCREEN not allowed in subscreens (screen: <Report Name> 0100)
so..if any body know the solution ...plz help me...
Thanks & Regards
Srinivas-SAP,

Hi,
please go through the functionality of tabstrips.
basically they are placed on tabstrips.
so they dont have their own ok codes and call screen and set screen ( to best of my knowledge )
can not be used.
if you are using set screen remove them.
even without using set screen if you are gettig the error, please let us know.
regards
Ramchander rao.K

Odi Jobs not getting triggered through Scheduler Agent

Hi Guru's,
i have Scheduled jobs in odi using Scheduler agent but jobs doesn't get triggered even though my scheduler agent is up and running and i have updated scheduled plan also.
Please help me in resolving the issue.
Regards
Vinod

Is your Agent successfully installed ?
What is your OS and where exactly the ODI install ?
If it is in Windows the we need to check the .BAT file if it is in linux then we need to check the .SH file for Agent.
Thanks,
Lony
8763043086

Point/Migrate batch jobs from Sybase(auto scheduled through Control-M application) to SQL Server 2005

Hi,
I am currently working in project where we need to migrate/point batch jobs to SQL server 2005. At this moment they are pointing to Sybase. Batch jobs are in .bat and .exe format. These jobs read in an external file, does some reformatting,
and then loads it into 2 sybase tables. These jobs are auto scheduled through Control-M application.
Any idea please ?
Thanks,
Chirag Patel

Change your post to type 'Question' Chirag
You would need to at least change the connection strings, and how you access SQL Server, but typically code changes are necessary.
You unfortunately don't provide enough details. But it is not as trivial to just 'point' a bunch of jobs to a new target.
Arthur My Blog

How should i execute file transfer via batch job scheduling

Hi guys,
    i want to call unix transfer script via batch job scheduling. Executing the system commands witin ABAP is as below:
         DATA: BEGIN OF ITAB occurs 0,
                     LINE(200),
                    END OF ITAB.
        UNIXCOMM = '/usr/sap/trans/data/*******'
        CALL 'SYSTEM' ID 'COMMAND' FIELD UNIXCOMM
                ID 'TAB'     FIELD itab-sys.
Now i plan to assign application server ('Exec Target') to it and let it implement in the background.
Should i do it via batch job?
Any info is appreciated very much.

Instead of using
CALL 'SYSTEM' u can use FM..
SXPG_COMMAND_EXECUTE .. in which u have to pass a command name which u can create or get from SM49...
In CALL 'SYSTEM' .. u can not catch exceptions.. but in FM given above u can check
SY-SUBRC, STATUS and EXITCODE for successful command execution..
for successful command execution..
sy-subrc = 0
STATUS = 'O' " Capital O
exitcode = 0
For batch scheduling, you can use this FM in a report with one parameter for additional parameter which u need to pass to this FM and create a JOB for that report and schedule it..
I've used it and find it useful even for batch scheduling..
Reward if useful
Regards
Prax

Has anyone built a job scheduling interface for BMC's Control-M product

Has anyone built a job scheduling interface for BMC's Control-M product? If so - how did you notify control-m when the XI job completed successfully versus unsuccessfully?

Have you received any help on this? I would like to know the answer to this question.

Job Schedule Sun thru Thurs only via TVARV using variant

Can someone tell me how to use TVARV to setup my job to run only on Sunday thru Thursday using my variant?

Hi,
Please check the below links.
http://help.sap.com/saphelp_nw04/helpdata/en/c0/9803aae58611d194cc00a0c94260a5/content.htm
Some sample code from seachsap site.
Have you ever wondered where your TVARV variables are being used in your batch jobs? How do you know if they change, and the impact it may have on your interfaces? The program below will provide a listing for you.
The program uses Job Count (job id) as the key versus Job Name as job names can be redundant. The code was written in R/3 v.4.6C, but should work in 3.x versions as well.
Code
PROGRAM: ZCAUS_EXTRACT_REPORT_VARIABLES
AUTHOR: DYLAN HACK
CREATE DATE: 10/09/2002
PURPOSE: This program was developed to extract all jobs based on the
         "Job Status" selection criteria and find the relevant TVARV
         variable entries. Then the report can be downloaded and
         sorted on selection variables. Ultimate purpose is to know
         what jobs are affected by the individual TVARV variables.
         If a job exists but does not have a corresponding entry/use
         of a TVARV variable, it will not get listed.
JOB STATUS LEGEND:
R: job step running.
Y: job step ready (eligible to run, waiting for a work process).
P: job step scheduled.
S: job step released (eligible to run when the start condition of the
   job is fulfilled).
A: job step aborted.
F: job step successfully finished.
Z: system upgrade in progress, only upgrade-related jobs are allowed
   to run. Jobs and job steps with this status are ignored by the
   scheduler.
X: unknown status detected.
REPORT ZCAUS_EXTRACT_REPORT_VARIABLES .
tables: tbtcp, tbtco.
data: var like RSVARVAR occurs 0 with header line,
      begin of report_tmp occurs 0,
        jobname   like tbtcp-jobname,
        jobcount like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname type syrepid,
        variant   type syslset,
      end of report_tmp,
      report like report_tmp occurs 0 with header line,
      begin of listing occurs 0,
        jobname type tbtcp-jobname,
        jobcount like tbtcp-jobcount,
        stepcount type tbtcp-stepcount,
        progname type syrepid,
        variant   type syslset,
        variable type rsvarvar-variable,
      end of listing.
selection-screen begin of block a1 with frame title text-001.
selection-screen begin of block b1 with frame.
select-options: s_status for tbtco-status.
selection-screen end of block b1.
selection-screen begin of block b2 with frame.
selection-screen comment /5(75) com1.
selection-screen comment /5(75) com2.
selection-screen comment /5(75) com3.
selection-screen comment /5(75) com4.
selection-screen comment /5(75) com5.
selection-screen comment /5(75) com6.
selection-screen comment /5(75) com7.
selection-screen comment /5(75) com8.
selection-screen end of block b2.
selection-screen end of block a1.
initialization.
move:
'R: Job Running' to com1,
'Y: Job Ready (Eligible to run, waiting for process)' to com2,
'P: Job Scheduled' to com3,
'S: Job Released (Eligible to run when start condition is trigerred)'
to
com4,
'A: Job Aborted' to com5,
'F: Job Successfully Finished' to com6,
'Z: Upgrade in process, job being ignored' to com7,
'X: Unknown Status Detected' to com8.
start-of-selection.
get all jobs in released status
select jobcount from tbtco into report_tmp-jobcount
    where status in s_status.
    append report_tmp.
endselect.
get all related variants for those jobs that meet the where clause.
loop at report_tmp.
    select jobname jobcount stepcount progname variant
    into corresponding fields of report
    from tbtcp where jobcount = report_tmp-jobcount and
                     variant not like '&%' and
                     variant <> space.
    append report.
    endselect.
endloop.
sort and delete duplicates (if any)
sort report by jobname jobcount stepcount progname variant.
delete adjacent duplicates from report comparing all fields.
get TVARV selection variables
loop at report.
clear var. refresh var.
call FUNCTION 'RS_VARIANT_VARIABLES'
    EXPORTING
       PROGRAM = report-progname
       VARIANT = report-variant
    TABLES
     VAR = var
    EXCEPTIONS
        VARINT_NOT_EXISTENT.
move the data to a listing table
if var-variable <> space.
   loop at var.
    move: report-jobname   to listing-jobname,
          report-jobcount to listing-jobcount,
          report-stepcount to listing-stepcount,
          report-progname to listing-progname,
          report-variant   to listing-variant,
          var-variable     to listing-variable.
    append listing.
   endloop.
endif.
endloop.
sort and delete dups from listing
sort listing by jobname jobcount stepcount progname variant variable.
delete adjacent duplicates from listing comparing all fields.
data: count type i. loop at listing. count = count + 1. endloop.
write out the listing
write: 'Count', count. skip.
write: 2   'Job Name',
       36 'Job #',
       48 'Step',
       54 'Program name',
       95 'Variant',
       110 'Variable'.
loop at listing.
    write: / listing-jobname,
             listing-jobcount,
             listing-stepcount,
             listing-progname,
             listing-variant,
             listing-variable.
endloop.
Thanks,
Ramakrishna

Reporting Agent Job Scheduling problem

hi All,
I am trying to schedule reporting agent job. I have few pre calculated webtemplates in one reporting agent scheduling package. when i try to schedule it and go to "start condition" - I want to put "After Event". I am selecting Event and giving the parameter name. But when i save and go out the job is already scheduled (checked in sm37). so I tried to chk the job condition again and the event i selected is not there !!!!
I want to create after even condition and schedule that parameter via mainframe as our all job schedule through main frame only !!! can some one tell me why its not working with reporting agent ??
I will definately assign the points.

dinesh and SB,
thank you for your reply. understood your point. but what i m asking is when i put "after event" criteria in the start selection... wouldnt it show that always when ever i go to Reporting Agent scheduling Package --> right click --> schedule --> start condition (i meant the event name and parameter should be saved there)
but once i save it and get out from the scheduling package i can see the job has been scheduled but its not showing that its even controlled job !!!
is it possible to use "after event" option in Reproting agent's job ?
I have few queries under one Reporting Agent scheduling package which is added in one process chain - the PC is running once a month - i added RA at the end of the process chain and the variant will be schedule by mainframe once the process chain has completed successfully. now 2nd thing is: i need to run Reporting Agent job every single day. so need to schedule it twice. we schedule everything by main frame. so if i can save "after event" criteria then i can schedule that parameter by mainframe. the problem is the start condition is not saving my after event condition entries or parameter names.
I hope i m clear. pl. guide its kind a urgent.

Job scheduling

Hi Friends,
i have a problem with job scheduling.
two jobs need to be scheduled. (job1 and job2)
i used
job_open.
submit job1 using parameters.
job_close.
then for second job.
job_open.
submit job2 using parameter2.
job_close.
when i go and look in sm37. i see when job1 is running the job2 is in release status.
but what we need is when job1 is running job2 should be in schedule status. it should start only after job1 is completed.
in the job2 job_close i used job1 as the PRED_JOBNAME.
but i when i run the program job2 is in released status , not in schedule mode.
is there any way we can make the job2 in scheduled mode instead of release.
can we use event to control this. if yes please let me know how we can do it.
Thanks

Hi,
As Appana wrote - i'm not sure there's a problem, but why don't u make one job with 2 steps? this way u will be perfectly sure that job2 (2nd step in the new job) will run only after job1 (1st step n the new job)...
Good luck
Igal

Background Job Scheduling

Hi,
I am scheduling a report to run in background.
In this report it is creating background jobs automatically for different company codes.
It submits the 1st background job and waits until it finishes.
Then 2nd job starts in background and continues with other jobs.
At end it finishes all the jobs and closes.
Now my problem is.
1.       Whether is it possible for us to submit all the jobs at 1 time. And execute at same time. Ie., 1st, 2nd job will start at same time.
2.       If possible how can we do that.
What I have written is
loop at companycode.
Create job name.
call fun 'Job_Open'.
submit xxxx user sy-uname via job job_name numer job_count
to sap-spool
spool parameters l_spool_parameter
without spool dynpro
with companycode
with ......
and return.
endloop.
Please help ASAP, urgent.

hi praveen,
Job Scheduling Explained
Definition
Before any background processing can actually begin, background jobs must be defined and scheduled. The scheduled time for when a job runs is one part of the jobs definition. There are several ways to schedule jobs:
From Transaction SM36 (Define Background Job)
With the "start program in the background" option of either Transaction SA38 (ABAP: Execute Program) or Transaction SE38 (the ABAP editor)
Through the background processing systems own programming interface. (Many SAP applications use the internal programming interface to schedule long-running reports for background processing.)
Through an external interface.
Scheduling Background Jobs
Use
You can define and schedule background jobs in two ways from the Job Overview:
·         Directly from Transaction SM36. This is best for users already familiar with background job scheduling.
·         The Job Scheduling Wizard. This is best for users unfamiliar with SAP background job scheduling. To use the Job Wizard, start from Transaction SM36, and either select Goto ® Wizard version or simply use the Job Wizard button.
Procedure
       1.      Call Transaction SM36 or choose CCMS ® Jobs ® Definition.
       2.      Assign a job name. Decide on a name for the job you are defining and enter it in the Job Name field.
       3.      Set the jobs priority, or Job Class:
·         High priority:      Class A
·         Medium priority: Class B
·         Low priority: Class C
       4.      In the Target server field, indicate whether to use system load balancing.
·         For the system to use system load balancing to automatically select the most efficient application server to use at the moment, leave this field empty.
·         To use a particular application server to run the job, enter a specific target server.
       5.      If spool requests generated by this job are to be sent to someone as email, specify the email address. Choose the Spool list recipient button.
       6.      Define when the job is to start by choosing Start Condition and completing the appropriate selections. If the job is to repeat, or be periodic, check the box at the bottom of this screen.
       7.      Define the jobs steps by choosing Step, then specify the ABAP program, external command, or external program to be used for each step.
       8.      Save the fully defined job to submit it to the background processing system.
       9.      When you need to modify, reschedule, or otherwise manipulate a job after you've scheduled it the first time, you'll manage jobs from the Job Overview.
Note: Release the job so that it can run. No job, even those scheduled for immediate processing, can run without first being released.
Specifying Job Start Conditions
Use
When scheduling a background job (either from Transaction SM36, Define Background Job or CCMS ® Jobs ® Definition), you must specify conditions that will trigger the job to start.
Procedure
Choose the Start condition button at the top of the Define Background Job screen.
Choose the button at the top of the Start Time screen for the type of start condition you want to use (Immediate, Date/Time, After job, After event, or At operation mode) and complete the start time definition in the screen that appears.
For the job to repeat, check the Periodic job box at the bottom of the Start Time screen and choose the Period values button below it to define the frequency of repetition (hourly, daily, weekly, monthly, or another specific time-related period). Then choose the Save button in the Period values screen to accept the periodicity and return to the Start Time screen.
Once youve completed specifying the job start conditions, choose the Save button at the bottom of the Start Time screen to return to the Define Background Job screen.
No job can be started until it is released, including jobs scheduled to start immediately. Since releasing jobs can be done only by a system administrator from the job management screen (Transaction SM37) or by other users who have been granted the appropriate Authorizations for Background Processing, no unauthorized user can start a job without explicit permission
Managing Jobs from the Job Overview
Use
The Job Overview, or Job Maintenance, screen is the single, central area for completing a wide range of tasks related to monitoring and managing jobs, including defining jobs; scheduling, rescheduling, and copying existing jobs; rescheduling and editing jobs and job steps; repeating a job; debugging an active job; reviewing information about a job; canceling a job's release status; canceling and deleting jobs; comparing the specifications of several jobs; checking the status of jobs; reviewing job logs; and releasing a job so it can run.
Procedures
To display the Job Overview screen, choose CCMS ® Jobs ® Maintenance or call Transaction SM37. Before entering the Job Overview screen, the system first displays the Select Background Jobs screen. You'll need to complete this Job Selection screen to define the criteria for the jobs you want to manage. Once you've selected jobs to manage, you can choose from a wide range of management tasks:
To copy a single existing job, choose Job ® Copy.
To reschedule or edit job steps or attributes of a single job, choose Job ® Change. A job step is an independent unit of work within a background job. Each job step can execute an ABAP or external program. Other variants or authorizations may be used for each job step. The system allows you to display ABAP programs and variants. You can scan a program for syntax errors. You can also display the authorizations for an authorized user of an ABAP job step.
To repeat a single job, choose Job ® Repeat scheduling.
To debug an active job, choose Job ® Capture: active job. Only a single selection is allowed. If an active job seems to be running incorrectly (e.g., running for an excessively long time), you can interrupt and analyze it in debugging mode in a background process, and then either release it again or stop it altogether.
You will be able to capture a background job only if you are logged on to the SAP server on which the job is running. To find server information in the Job Overview, select and mark the job, then choose Job ® Job details.
To review information about a job, choose Job ® Job details. Details displayed can include:
current job status
periodicity, or the repetition interval
other jobs linked to the current job, either as previous or subsequent jobs
defined job steps
spool requests generated by the current job
To cancel a job's "Released" status, select the job or jobs from the Job Overview list and choose Job ® Release -> Scheduled.
To cancel a job from running but keep the job definition available, select the job or jobs from the Job Overview list and choose Job ® Cancel active job.
To delete a job entirely, select the job or jobs from the Job Overview list and choose Job ® Delete. Jobs with the status of Ready or Running cannot be deleted.
To compare the specifications of more than one job, select the jobs from the Job Overview list and choose Job ® Compare jobs.
To check the status of jobs, select the job or jobs from the Overview Job list and choose Job ® Check status. This allows you to either change the job status back to Planned or cancel the job altogether. This is especially useful when a job has malfunctioned.
To review job logs, select a job or jobs with the status Completed or Canceled from the Job Overview list and
regards
karthik
reward me points if helpfull

Problem in deleting backup job in Grid Control

Hi,
The topology and versions are as follows:
1 windows 2003 server with Oracle Grid Control 10.2.0.4.0.
1 windows 2003 server with Oracle Databases 10.2.0.3.
1 windows 2003 server with Oracle Databases 10.2.0.3 - Data Guard setup
I have tried to stop (and delete) some scheduled fullbackup jobs from Grid Control.
The job has now status SUSPEND. I have tried to stop and delete the job, but I get the message:
All executions of the job were stopped successfully. Currently running steps will not be stopped.
I cannot delete the job and the job is not running.
I have run this procedure in order to delete the job:
DECLARE
jguid RAW;
BEGIN
SELECT job_id
INTO jguid
FROM mgmt_job
WHERE job_name = '<name of your job>'
AND job_owner = '<owner of your job>';
mgmt_job_engine.stop_all_executions_with_id(jguid,TRUE);
COMMIT;
END;
With no effect. The job is still shown in Grid Control with status SUSPEND.
I have restarted all servers and all the components in Grid Control, but the jobs will not disappear from Grid Control although they have been deleted.
I am struggling with this for about 2 days now.
I have search in Metalink and the internet, but I have not found anything that provides a solution.
Any help will be very much appreciated.

hi,
I have in the past used the following from metalink
Do you have a metalink account?
SET verify OFF
SET linesize 255
SET pagesize 128
SET trimout ON
SET trimspool ON
SPOOL jobdump.log
ALTER SESSION SET nls_date_format='MON-DD-YYYY hh:mi:ss pm';
COLUMN status format a15
COLUMN job_name FORMAT a64
COLUMN job_type FORMAT a32
COLUMN job_owner FORMAT a32
COLUMN job_status format 99
COLUMN target_type format a64
COLUMN frequency_code format a20
COLUMN interval format 99999999
VARIABLE JOBID VARCHAR2(64);
PROMPT *********************** JOB INFO ********************************
REM Get the job id
SET serveroutput on
BEGIN
SELECT job_id INTO :JOBID
FROM MGMT_JOB
WHERE job_name='&&jobName'
AND job_owner='&&jobOwner'
AND nested=0;
EXCEPTION
WHEN NO_DATA_FOUND THEN
BEGIN
DBMS_OUTPUT.put_line('JOB NOT FOUND, TRYING NAME ONLY');
SELECT job_id INTO :JOBID
FROM MGMT_JOB
WHERE job_name='&&jobName'
AND nested=0
AND ROWNUM=1;
EXCEPTION
WHEN NO_DATA_FOUND THEN
DBMS_OUTPUT.put_line('JOB NOT FOUND');
END;
END;
SELECT job_name, job_owner, job_type, system_job, job_status, target_type
FROM MGMT_JOB
WHERE job_id=HEXTORAW(:JOBID);
PROMPT *********************** JOB SCHEDULE ****************************
SELECT DECODE(frequency_code,
1, 'Once',
2, 'Interval',
3, 'Daily',
4, 'Day of Week',
5, 'Day of Month',
6, 'Day of Year', frequency_code) "FREQUENCY_CODE",
start_time, end_time, execution_hours, execution_minutes,
interval, months, days, timezone_info, timezone_target_index,
timezone_offset, timezone_region
FROM MGMT_JOB_SCHEDULE s, MGMT_JOB j
WHERE s.schedule_id=j.schedule_id
AND j.job_id=HEXTORAW(:JOBID);
PROMPT ********************** PARAMETERS ********************************
SELECT parameter_name,
decode(parameter_type,
0, 'Scalar',
1, 'Vector',
2, 'Large', parameter_type) "PARAMETER_TYPE",
scalar_value, vector_value
FROM MGMT_JOB_PARAMETER
WHERE job_id=HEXTORAW(:JOBID)
AND execution_id=HEXTORAW('0000000000000000')
ORDER BY parameter_name;
PROMPT ********************** TARGETS ********************************
SELECT target_name, target_type
FROM MGMT_JOB_TARGET jt, MGMT_TARGETS t
WHERE job_id=HEXTORAW(:JOBID)
AND execution_id=HEXTORAW('0000000000000000')
AND jt.target_guid=t.target_guid
ORDER BY target_type, target_name;
PROMPT ********************** FLAT TARGETS ********************************
SELECT target_name, target_type
FROM MGMT_JOB_FLAT_TARGETS jft, MGMT_TARGETS t
WHERE job_id=HEXTORAW(:JOBID)
AND jft.target_guid=t.target_guid
ORDER BY target_type, target_name;
PROMPT ************************ EXECUTIONS *******************************
SELECT execution_id,
DECODE(status,
1, 'SCHEDULED',
2, 'RUNNING',
3, 'FAILED INIT',
4, 'FAILED',
5, 'SUCCEEDED',
6, 'SUSPENDED',
7, 'AGENT DOWN',
8, 'STOPPED',
9, 'SUSPENDED/LOCK',
10, 'SUSPENDED/EVENT',
11, 'SUSPENDED/BLACKOUT',
12, 'STOP PENDING',
13, 'SUSPEND PENDING',
14, 'INACTIVE',
15, 'QUEUED',
16, 'FAILED/RETRIED',
17, 'WAITING',
18, 'SKIPPED', status) "STATUS",
scheduled_time, start_time, end_time
FROM MGMT_JOB_EXEC_SUMMARY e
WHERE job_id=HEXTORAW(:JOBID)
ORDER BY scheduled_time;
UNDEFINE jobName
UNDEFINE jobOwner
UNDEFINE JOBID
SPOOL OFFAlan

ODI Job Scheduling via Control-M

Similar Messages

Maybe you are looking for