ODI 11g Scheduled job stays in running state

Hello All ,
In ODI operator in the integration process ,there arer 3 scenarios scheduled .
When the first is completed it switches to second ,but the next step/process keep running and never comes to an end,though the corresponding backend activity has been completed(which the scenario is supposed to do).
Which ultimately results into timeout.
Please suggest a solution for this.
Thanks in advance ,
ABHIJEET

Hi,
Actually your syntax is exactly right for running a single run-immediate job.
it looks like the slave running your job may have crashed or terminated unexpectedly. You should do a stop_job (force=>true) on your job and you should look through your job slave trace files j0trc for reasons why your job slave did not finish the job. You can also try grepping your job slave traces for the job name 'TEST_JOB' to find the right trace.
Hope this helps,
Ravi.

Similar Messages

Jobs stays in waiting state but does not ever run in target system

This usually happens when there is a network problem or the target system is down for some reason. Is there a way to ignore the waiting status so that the next scheduled job runs would be affected? If not can CPS be configured to constantly request for the actual status of the job in the target system?

Hi,
Set the below parameter on the process server of the target system for which jobs stays in waiting state.
Parameter: SAP_MaxReconnectTime value: 60
Reason: Process servers tries to connect to Target system at the time when the network issue happens and due to that It does not connect to the target SAP system and all the jobs stays in waiting status.
When you set this parameter with the value (what ever you want in Minutes), it will automatically try to reconnect to the target SAP System at every 60 min (or the value provided) when ever it loses the connection with Target system and Jobs will start processing again.
Thanks and Regards,
Vipul Kaswala

Scheduled jobs are not running DPM 2012 R2

Hi,
Recently upgraded my dpm 2012 sp1 to 2012 R2 and upgrade went well but i got 'Connection to the DPM service has been lost.(event id:917 and other event ids in the eventlog errors ike '999,997)'. Few dpm backups are success and most of the dpm backups consistenancy
checks are failed.
After investigating the log files and found two SQL server services running in the dpm 2012 r2 server those are 'sql server 2010 & sql server 2012 'service. Then i stopped sql 2010 server service and started only sql server 2012 service using (.\MICROSOFT$DPM$Acct).
Now 'dpm console issue has gone (event id:917) but new issue ocurred 'all the scheduled job are not running' but manully i can able to run all backup without any issues. i am getting below mentioned event log errors
Log Name: Application
Source: SQLAgent$MSDPM2012
Date: 7/20/2014 4:00:01 AM
Event ID: 208
Task Category: Job Engine
Level: Warning
Keywords: Classic
User: N/A
Computer:
Description:
SQL Server Scheduled Job '7531f5a5-96a9-4f75-97fe-4008ad3c70a8' (0xD873C2CCAF984A4BB6C18484169007A6) - Status: Failed - Invoked on: 2014-07-20 04:00:00 - Message: The job failed. The Job was invoked by Schedule 443 (Schedule 1). The last step to
run was step 1 (Default JobStep).
Description:
Fault bucket , type 0
Event Name: DPMException
Response: Not available
Cab Id: 0
Problem signature:
P1: TriggerJob
P2: 4.2.1205.0
P3: TriggerJob.exe
P4: 4.2.1205.0
P5: System.UnauthorizedAccessException
P6: System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal
P7: 33431035
P8:
P9:
P10:
Log Name: Application
Source: MSDPM
Date: 7/20/2014 4:00:01 AM
Event ID: 976
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer:
Description:
The description for Event ID 976 from source MSDPM cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
The DPM job failed because it could not contact the DPM engine.
Problem Details:
<JobTriggerFailed><__System><ID>9</ID><Seq>0</Seq><TimeCreated>7/20/2014 8:00:01 AM</TimeCreated><Source>TriggerJob.cs</Source><Line>76</Line><HasError>True</HasError></__System><Tags><JobSchedule
/></Tags></JobTriggerFailed>
the message resource is present but the message is not found in the string/message table
plz help me to resolve this error.
jacob

Hi,
i would try to reinstall DPM
Backup DB
uninstall DPM
Install DPM same Version like before
restore DPM DB
run dpmsync.exe -sync
finished
Seidl Michael | http://www.techguy.at |
twitter.com/techguyat | facebook.com/techguyat

Scheduled jobs do not run as expected after upgrading to 10.2.0.3 or 4

FYI, we've had a ticket open for several days because our scheduled jobs (dbms_scheduler) would no longer run as scheduled after an upgrade to 10.2.0.4 on HPUX, couldn't find the solution by searching in metalink, nor did I find it here or using Google - obviously I wasn't searching correctly. There is a note id that references a set of steps that appears to have resolved our problem. I am putting this note out here so that if you encountered the same difficulty you may come across this note earlier in your troubleshooting efforts rather than later. The full title of the note is: 'Scheduled jobs do not run as expected after upgrading to either 10.2.0.3 or 10.2.0.4'. The Doc ID is: 731678.1.

Thanks - our ticket should be getting closed out on it (our dba will be updating it), the scheduler has been running reliably since we took the steps in the doc mentioned.

Scheduled jobs are in released state only

Dear Experts,
we shedule jobs in background periodically. But for a particular time, all scheduled jobs are in released state only. Please suggest what might be the issue. Even some SAP std jobs have have not started.

Hi Raghavendra,
Have you checked enough BTC work process available in your SAP system.
Use SM65 transaction,goto =>Additional Tests ;check mark "Determine work process status" and "Determine no of jobs in queue"
and see the test results for any problems.
Best Regards,
Shyam Dontamsetty

Scheduled jobs fail to run after reboot

A couple of months back we moved our CF 8 server to a VM (VMWare). We have noticed that after the server (Windows OS) is rebooted, all scheduled jobs do not run. There are no errors in the logs. One oddity is that after the reboot in the scheduler log there are a series of entries for all jobs with the ThreadID of "main", after that there are no other entries. Normally when the job runs the ThreadID will be something like “Scheduler-1”. Here is where it gets really strange. Simply logging into the console will “trigger” the jobs and they will run. I do not have to manually initiate on of the jobs. This can be repeated over and over simply by rebooting the server. Manually stopping and starting the service does not trigger this issue nor will it “kick start” the jobs to run.

Update:
I opened up a case with Microsoft Support and resolved the issue. Apperantly this is a known issue and the bug will be addressed in CU6. Microsoft was able to give me a hotfix (QFE_MOMEsc_4724.msi) which I applied on all systems that have SCOM Console. I
am told that this issue occurs when SCOM 2007 R2 CU5 runs on SQL 2008 R2.
I hope it helps to others that run into same problem.
ZMR

BI Publisher (Obiee 11g) Scheduled jobs start randomly after services restarting

Hi everybody,
I've a problem with scheduled jobs on BI Publisher that start randomly after server restarting.
For example if there's a job scheduled every day at 8.00 am it works fine until the server is not restarted but when I restart it next job running start at 9.28 am (it is an example because the real start time is very unpredictable).
In my case bi publisher is integrated with obiee 11g (11.1.1.6.2) and I've scheduled jobs with administrative user (weblogic). For this user I've set the Bi Publisher Preferences (report locale = Italiano-Italia, Report Time Zone = GMT +1:00) from obiee analytics user account preferencies.
Can anyone have this problem too and help me?
Thanks
Annalisa

These are not helpful. The first link is to OBIEE 10g and the second is just an install guide. I am having the same issue with BI Publisher returning java.lang.NullPointerException in OBIEE 11g. Any help would be appreciated. Thanks,
Paul
Edited by: pneedleman on Nov 17, 2010 10:15 AM

Some Schedule jobs are not running in Oracle 10g

i have total of 8 Schedules jobs in Oracle 10g test database which were not in sync with prod database . So i re-created all of them again and then enbled them . but some 4 of them didnt ran on their NEXT_RUN_DATE . Showing NULL on LAST_START_DATE and LAST_RUN_DURATION . How to make them Run
select OWNER,JOB_NAME,START_DATE,STATE,SCHEDULE_NAME,LAST_START_DATE,LAST_RUN_DURATION,NEXT_RUN_DATE from ALL_SCHEDULER_JOBS
where OWNER='MESH_FOR' and last_start_date is NULL;
OWNER     JOB_NAME     START_DATE     STATE     SCHEDULE_NAME     LAST_START_DATE     LAST_RUN_DURATION     NEXT_RUN_DATE
MESH_FOR     REFRESH_TERMINALS_J     27.07.2010 11:00:00,000000000 +02:00     SCHEDULED     DAILY_EVERY_30_MINUTES     NULL     NULL     27.07.2010 11:00:00,000000000 +02:00
MESH_FOR     REFRESH_MN_SERVERS_J     27.07.2010 11:00:00,000000000 +02:00     SCHEDULED     DAILY_EVERY_30_MINUTES     NULL     NULL     27.07.2010 11:00:00,000000000 +02:00
MESH_FOR     REFRESH_EVENT_INFO_J     27.07.2010 11:00:00,000000000 +02:00     SCHEDULED     DAILY_EVERY_30_MINUTES     NULL     NULL     27.07.2010 11:00:00,000000000 +02:00
MESH_FOR     UPDATE_MV_CHANGES_J     27.07.2010 11:00:00,000000000 +02:00     SCHEDULED     DAILY_EVERY_30_MINUTES     NULL     NULL     27.07.2010 11:00:00,000000000 +02:00

Hi,
Could you please explain, what is OS authentication?
I created a new user for creating and runing jobs.
I have given following priveleges to the new User.'
1)Connect
2)SELECT_CATALOG_ROLE
3)Create Job
Then, I created the job as follows.
BEGIN
sys.dbms_scheduler.create_job(
job_name => 'SMPL_TST_JB',
job_type => 'PLSQL_BLOCK',
job_action => 'Declare
Result Integer;
begin
Result:=1;
/* Other statments */
Exception
when others then
Result:=3;
end;',
repeat_interval => 'freq=daily;byhour=10;byminute=00;bysecond=00',
start_date => systimestamp,
job_class => 'DEFAULT_JOB_CLASS',
auto_drop => FALSE,
enabled => TRUE);
sys.dbms_scheduler.set_attribute( name => 'SMPL_TST_JB', attribute => 'logging_level', value => DBMS_SCHEDULER.LOGGING_FULL);
sys.dbms_scheduler.set_attribute( name => 'SMPL_TST_JB', attribute => 'restartable', value => TRUE);
END;
Then, I run the job as following.
SQL> begin sys.dbms_scheduler.run_job ('SMPL_TST_JB'); end;
2 /
begin sys.dbms_scheduler.run_job ('SMPL_TST_JB'); end;
ORA-03113: end-of-file on communication channel
Thank you,
Regards
Gowtham Sen.

How to Schedule Jobs to only run during a time window

I have a long running task that needs to schedule jobs to process data.
I only want these scheduled jobs to start during a specific window of time each day, probably 10:00 PM to 6:00 AM.
If the scheduled jobs do not begin during the specified time frame, they must wait until the next day to start running.
Each scheduled job will only be executed once and then auto dropped.
How should I go about creating these scheduled jobs?

Hi Jeff,
I agree that the documentation isn't clear enough about the purpose of windows.
You can indeed use windows for changing the resource plan, but you can also use them for scheduling your jobs.
I did a simple test in real-time to illustrate the latter.
At around 10.30 am today I created a table that will populated by a job:
CREATE TABLE TEST_WINDOW_TABLE(EVENT_DATE DATE);
Then, I created a window whose start_date is today at 10.40 am :
dbms_scheduler.create_window(
                             window_name     =>'TEST_WINDOW',
                             resource_plan   => NULL,
                             start_date      => to_date('10/04/2014 10:40:00', 'dd/mm/yyyy hh24:mi:ss'),
                             repeat_interval => NULL,
                             duration        =>interval '5' minute
You can see that this window doesn't have a resource plan, and its repeat interval is NULL (so it will be opened only once).
The window will stay open for 5 minutes.
Finally, I created a one-off job whose schedule is the previously created window:
DBMS_SCHEDULER.create_job (
                           job_name      => 'TEST_WINDOW_JOB',
                           job_type      => 'PLSQL_BLOCK',
                           job_action    => 'BEGIN insert into test_window_table values (sysdate); COMMIT; END;',
                           schedule_name => 'SYS.TEST_WINDOW',
                           enabled       => true,
                           auto_drop     => true
Checking the user_scheduler_job_log before 10.40 would return no rows, which mean the job hasn't started yet since the window was not open.
Now, from 10.40, it shows one entry:
SQL> select log_date, status from user_scheduler_job_log where job_name = 'TEST_WINDOW_JOB';
LOG_DATE                                                                         STATUS
10/04/14 10:40:02,106000 +02:00                                                  SUCCEEDED
The TEST_WINDOW_TABLE has also got the row:
SQL> select * from TEST_WINDOW_TABLE;
EVENT_DATE
10/04/2014 10:40:02
Voilà.
In your case, since you want to run the jobs daily between 10 pm and 6 am (duration of 8 hours), the window would look like this:
dbms_scheduler.create_window(
                             window_name     =>'YOUR_WINDOW',
                             resource_plan   => NULL,
                             repeat_interval => 'freq=daily;byhour=22;byminute=0;bysecond=0',
                             duration        =>interval '8' hour
For your jobs, you may need to specify an end_date if you want to make sure the job gets dropped if it couldn't run in its window.

DBMS_SCHEDULER.RUN_JOB causes scheduled job not to run again

Environment: 10.2.0.2 Linux 64-bit
Hi,
I have some DBMS_SCHEDULER chain jobs scheduled to run every hour which has been running fine with no issues for a while now.
I needed to run a couple of jobs manually in-between scheduled times so I ran the job using DBMS_SCHEDULER.RUN_JOB, and that worked as expected as it has done in the past.
This issue is that the jobs I ran manually haven't run at their scheduled time since I did that. The only way around it was to recreate the job completely.
Any idea if this is normal functionality, or should I be raising this as a possible issue through Oracle Metalink?
Any help or ideas would be much appreciated.
Thanks
Tim

Hi Tim,
This is a known bug which is tracked internally by bug #5705385. It will be fixed in the next patchsets for 10.2 and 11.1 (i.e. 10.2.0.5 and 11.1.0.7) . If you urgently need a fix, an official patch seems to be available for 10.2.0.3 .
There does seem to be a workaround - using run_job again after the first run_job has completed will not do anything but the chain job should again run on schedule.
Hope this helps,
Ravi.

Backup job stuck in running state

Hi
I am using 11gR2 RAC on Windows 2008 R2. I have several different database jobs stuck in a running state. However if I check the view v$session_longops I can not see anything in there relating to RMAN. If I drill down to the job and the step that is running, in the Error Log it states:
error writing input to command
Could someone point me in the right direction as to how to investigate this?
Thanks

if you know that the execution finished or is hung,use this query:
SELECT p.SPID, s.sid, s.serial#, sw.EVENT, sw.SECONDS_IN_WAIT AS
SEC_WAIT, sw.STATE, CLIENT_INFO
FROM V$SESSION_WAIT sw, V$SESSION s, V$PROCESS p
WHERE s.client_info LIKE 'rman%'
AND s.SID=sw.SID
AND s.PADDR=p.ADDR;
and kill them.

Scheduled task going to running state in OIM

hi all,
After running the Target reconciliation it is going to running state ....how to fix this?
Thank you.

For how much time it shows Running status ?
Check the status of schedule task using http://localhost:7001/xlScheduler if OIM is deployed on weblogic on 7001 port.
I have seen couple of clients who are using OID connector and never heard such issues in OOTB connector.
Try with restarting the server.

How to setup a daily schedule job that will run a PL/SQL procedures every night

I have an update program that will need to run every night, can I setup a schedule job in data server?

Hi Kane,
You can try to use the package DBMS_JOB.
In the package specification is a description how to use it. The parameter called INTERVAL can be used to start your job every night.
Hope this helps...

Job hang in RUNNING state

Hi,
Database ver. 11g (11.1.0.7.0)
I have created simple job using DBMS_SCHEDULER.
begin
dbms_scheduler.create_job (
job_name => 'test_job',
job_type => 'plsql_block',
job_action => 'null;',
enabled => true);
end;
SELECT job_name, job_action, schedule_type, state
FROM all_scheduler_jobs
WHERE job_name = 'TEST_JOB';
JOB_NAME JOB_ACTION   SCHEDULE_TYPE    STATE
TEST_JOB   null;        IMMEDIATE      RUNNING
SELECT job_name, session_id , running_instance, cpu_used
FROM dba_scheduler_running_jobs
WHERE job_name = 'TEST_JOB';
JOB_NAME SESSION_ID RUNNING_INSTANCE, CPU_USED
TEST_JOB   null          null          null Job is remaining in hang state, could you please let me know possible reason?
Many thanks.

Hi,
Actually your syntax is exactly right for running a single run-immediate job.
it looks like the slave running your job may have crashed or terminated unexpectedly. You should do a stop_job (force=>true) on your job and you should look through your job slave trace files j0trc for reasons why your job slave did not finish the job. You can also try grepping your job slave traces for the job name 'TEST_JOB' to find the right trace.
Hope this helps,
Ravi.

Process Schedule jobs stay queued

Our quality assurance environment was refreshed and everything came backup and seems to working fine except we can't run any jobs using process scheduler. Any job submitted remains at the queued status. Our PS admin is on vacation. Can anyone give me any ideas on what might be the problem. I have tried booting the server and restarting the process scheduler.
We are windows, PT 8.49, campus solution
Thanks for taking my question!
Kathie

I found the problem - bad data mover export of peoplesoft tables taken prior to the refresh. No idea how the export got corrupted or why all process scheduler tables appeared to have the correct data. The bad data only showed up after attempting another refresh.
To fix, I re-imported an old data mover export and reconfigured the process scheduler.
Thanks to everyone for their comments and help!
Kathie

ODI 11g Scheduled job stays in running state

Similar Messages

Maybe you are looking for