Job starts in un-scheduled time

Hi All,
I have created a job which runs fine for some days. But some times in runs in different time than what I scheduled. Here is the job script. It always suppose to run every day 5.00 PM.
Please advice on the same.
DECLARE
X NUMBER;
BEGIN
SYS.DBMS_JOB.SUBMIT
( job => X
,what => 'mypackage.myproc(''/u000/app/oracle/myfol'', ''NL''||TO_CHAR(SYSDATE-1, ''YYMMDD'')||''.TXT'', TO_CHAR(SYSDATE, ''YYYYMMDD''));'
,next_date => to_date('10/04/2009 17:00:00','dd/mm/yyyy hh24:mi:ss')
,interval => 'TRUNC(SYSDATE + 1) +17/24'
,no_parse => TRUE
SYS.DBMS_OUTPUT.PUT_LINE('Job Number is: ' || to_char(x));
END;
commit;

But some times in runs in different time than what I scheduled.What time are you seeing it run? Are we talking about major changes (i.e. it's running at 3 AM)? Or problems where it is running a few minutes after 5 PM?
Do you have other jobs? What is JOB_QUEUE_PROCESSES set to? Any chance there are more jobs that want to run at 5 than JOB_QUEUE_PROCESSES allows to run simultaneously at 5 so your job is getting queued?
Is the clock on the server correct? Is the clock drifting over time?
Justin

Similar Messages

Bakup did not start at the scheduled time?????

Hi all
Yesterday I scheduled my backup as usual at 1:00am and to my surprise the logs showed me that the backup was started at 9:30am in the morning............
In the morning when I tried to login I could not, I saw the status of the database it was shut down so I manually started the database which caused the backup that was started at 9:30am(which i could not see that it was running) terminated with errors.....................
Can any one please tell me how come the backup did not start at the scheduled time. However the backup of the next day was sucessfull.
Regards
Mahesh

Hello Jaipal,
I suspect that an 'sapdba' session or 'brspace' session was active on the OS level.
Some user must have kept this session active knowingly or unknowingly.
The offline backup was waiting for the active session to complete / end.
The session probably was ended / terminated around 9:30 am
(Maybe the user terminated the sapdba / brspace session at 9:30 in the morning after resuming the office work)
The backup started as soon as the sapdba / brspace session was terminated / ended.
Regards,
Ammey Kesarkar
<i>'Award points for useful info'</i>

Jobs running different than scheduled time

Hi All'
I have 10g(10.2.0.2) database in linux,It is in Austin.
Recently the jobs scheduled are running on different than scheduled time.
And time in EM and the date command in linux also showing different.
$ date
Wed Oct 31 03:59:01 CDT 2007
and the same time EM showing 2:59:42 AM
And some of the jobs are failing also.
I checked the following
SQL> select sessiontimezone from dual;
SESSIONTIMEZONE
-05:00
SQL> select dbtimezone from dual;
DBTIME
+00:00
can anybody please give the solution
Thanks in advance,
saf

There are a number of threads in this forum which deal with this type of issue:
Re: changing SO hour - problem to run a scheduled job
did it start on Oct 28th ? It may be a DST issue. Lookup in metalink 402742.1.

Mac mini would no longer start at the scheduled time

hi,
since about a week or so, my mac mini no longer automatically starts at the time i've scheduled [which can be specified under "energy saving" (?*) in "system preferences" (?*)]
but so far it does power up "manually" after presing the power butten several times.
any ideas on what could be wrong here?
*sorry if i might not be using the correct english terms, since i'm not using an english version of os x 10.4.7, but german os x. (neither is english my first language).
btw: if anyone knows of a (free, easily available) source (such as an english manual of os x tiger) where i could find the english equivalents for the terms used in the german version of the os - pls lemme know!

You might engage a professional data recover service. However there will be no guarantees of success and the costs will substantial.
Ciao.

How to capture the job start time

Hi,
how do i capture the time the job start running and the time the job end? when i query this
SQL> select * from user_jobs;no column are showing when the job start time (only last_sec and next_sec). I want to copy user_jobs view into ajob_history table, like this:
Job history table
Job_start Job_end
(?) (last_sec)

Why not add a log time into the job call itself? That way, you can collect the information yourself for the jobs you're interested in.
So instead of the "what" parameter being "my_proc(p1, p2....)", change it to something like:
declare
v_start_time TIMESTAMP;
v_end_time TIMESTAMP;
begin
v_start_time := systimestamp;
my_proc(p1, p2....);
v_end_time := systimestamp;
log_job_time('Unique identifier', v_start_time, v_end_time);
end;and have the log_job_time process insert a row into a logging table that captures the name of the job and it's start and end time.
That's if you can't include the timings in your procedure, of course.

Scheduler Jobs that run between certain times?

Is there an easy way to query which dbms_scheduler jobs run between any given times?
If I look at repeat_interval in user_scheduler_jobs, for example, I've got things like "FREQ=DAILY; BYHOUR=14,16,18,20,8,10,12; BYMINUTE=30" and "FREQ=HOURLY; INTERVAL=2;" and "FREQ=DAILY;", and it's not therefore clear to me how I could write a query that would find which jobs run between (say) 17:00 and 19:00.
Is there a function, or a neat bit of sql, that will 'explode' the repeat interval (presumably, in the case of the last two examples above, with reference to the start_date) into standardized times which I could then query? Or is there some other way of doing it?

There are no schedules used here. The repeat interval is specified for all jobs at the time of creating the job.
Besides, that wouldn't address the issue, even so. Even if schedules are in use, they declare their repeat interval in the form "freq=daily;byhour=3,4,5,6;byminute=0;bysecond=0", stored in a text field. Exactly the same, in fact, as the repeat_interval column in the user_scheduler_jobs column.
So how do you derive from that the knowledge that the job can run some time between 2 and 8AM?
I want to list all jobs which might start between those two times, but I do not know syntactically or logically how it is possible to query either user_scheduler_jobs or all_scheduler_schedules to select all rows where repeat_interval "is somehow covered by the time range 2 to 8".
Thanks for replying, though.

Changing job schedule time

Hi,
I have scheduled a job to execute at a specific time daily.
But now I want to change the execution time, job will execute daily.
How to do that ?
Regards,
Amit R.

hi,
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.
i got this from link,
http://help.sap.com/saphelp_nw04/helpdata/en/c8/6a56389f64246fe10000009b38f889/frameset.htm
Regards,
Arunsri

DBMS JOBS Start time

Hi,
We have a lot of jobs scheduled in our environment. While monitoring topas I find
out the havily running job. I have a process Id information and which sql has
running also. My actual problem is i will grep the above process id, It shows
database started time. I have issued the below command in unix environment.
PROMPT> ps -ef grep pid
Any one help to guide me.
Thanks in advance,
Upendran .A

I assume you want to find how long a specific job (from dbms_job) is running, i.e. when was it started.
Oracle uses SNP processes to "host" sessions for jobs. These SNP processes are started at the same time the database instance is started or the number of job_queue_processes is changed via alter system (the number of SNP processed = the maximum number of concurrent running jobs = the value of job_queue_processes parameter).
But, if you look into v$session, then the session hosting your job will show the starting time of the apropriate job call in the LOGON_TIME attribute (as the logon_time for SNP processes changes each time the job queue is changed). You can link the v$session information to OS pid using join between v$session and v$process:
select s.sid, s.serial#,
s.status,
s.username,
s.osuser,
s.machine,
TRIM(s.program || ' ' || s.module || ' ' || s.action) as Program,
p.spid,
to_char(s.logon_time, 'DD.MM.YY HH24:MI:SS') as logon_time
from v$session s, v$process p
where s.paddr = p.addr (+);
Alternatively, you can query the dba_jobs view (or user_jobs), the attribute THIS_TIME shows the time when the job was started for a running job. Again, using the SID you can link this to v$session and v$process.
Regards, Martin

Schedule Time Evaluation Job

Hi Experts,
I have a requirment to schedule Time Evaluation Job Automatically at Every day 12:00 am midnight. Could you pls help how to create variants and schedule the job.
Thanks
Priya

Hi, Priyadarshini.
You can schedule a job also doing the following.
1. Enter in transaction PT60.
2. Define the parameters in the enter screen and save as variant.
3. Go to menu: Program --> Execute in Background.
4. Define the printer (so we can check the log error). Here use some printer already installed in sap and inform to send to SAP spooler, then you'll able to see the log in SP01.
5. Click on the button "Date/Time";
6. Inform the Date and the Time in "Schedule Start";
7. Click on the button "Periodic job";
8. Click on "Period values" and define Daily.
And this is it. I think it's better you access the program like this to schedule the job, once in the Productive client, usually, we don't have access to the SE38.
I hope it helps.
Regards,
Luciano.

Job Scheduler Timer issue in Cisco Prime Infrastructure 1.2 ?

Has anyone run into this issue where the job scheduler in CPI 1.2 report that the job that is being scheduled is before the current time even though it isn't ?
This only started happening after our time change yesterday. The system is setup for the correct time (NTP) this is confirmed in the app and also on the CLI console access (show clock)
Anyway we get this error message (attachment) in the lower right corner of the attachement.
It's not allowing the jobs to be scheduled. Rebooted the system yesterday and thought that it fixed it, but evidently I tried another scheduled job today and it's got the same issue.
TAC Case is already opened on this but I thought I'd ask here as well.
Regards,
Tom W.

I'm answering my own question: upgrade to 1.3 from 1.2 and the problem is resolved. Rebooting the VM on 1.2 did help for 1 day but then the problem came back, so my advice is simply to upgrade to 1.3 which I would have done initially if I had known that 1.3 was available. Hope this helps. The problem itself in 1.2 is unclear what is causing it because NTP and the APP and the underlying time in the console (cli) are all good; so somewhere in the scheduler it may have gone off track after the daylight savings time shift this past week. Bottom line: 1.3 upgrade and keep hope alive, bro.

Difference between dispatch time in po and scheduled time in job

Hi all ,
can any one please explain me
what is the exact difference between dispatch time maintained in po and time/date set for job schedule
here my question is ,i maintained dispatch time as send job with periodically in PO and i had maintained date/time in job process steps with some period.
when po message is triggered ,which time will be consider system.time specified in job schedule or dispatch time in Po.
which one consider first?
Thanks
konidala

Dispatch time that is set up as part of the message output condition records, drives at which event does the output be transmitted. Conversely, the date/time during the batch job set up is the time when the batch job must execute the program.
For example, if you had selected the dispatch time for output NEU in the PO to be '1' and you had set up ME9F program as a background job running daily once at 1PM, when the PO is created and saved at 10AM, the output type NEU will be triggered and will be held in queue. At 1PM when ME9F program is run as part of the background job, it'll pick up this output type for execution and transmission.

All scheduled jobs started suddenly to fail with ORA-01031: insufficient pr

I have a setup of gridcontrol 11g on windows 2008. I've been running successful for weeks until the other day when all my scheduled jobs started to fail with
ORA-01031: insufficient privileges (rman jobs)
ERROR: Invalid username and/or password (sql scripts).
I verified for the accounts being locked, pw correct, expired / grace period, etc.
all good when I try from the command line. running an rman backup from the command line works great, but the same one through the job scheduler fails with ORA-01031.
I've dropped the jobs completely, recreated them again. same thing.
I'm using preferred credentials and dropped and recreated them. same thing.
I don't know where else to look. Only grid control scheduled jobs fail, but all of them do.
I'm using SQLNET.AUTHENTICATION_SERVICES= (NTS) in my sql.ne (always have).
we use a windows domain server / domain authentication for logging into boxes. I haven't changed any of my passwords.
I am probably looking in the wrong places. Anybody able to help?

Hi,
ERROR: Invalid username and/or password (sql scripts).This error message clearly tells that password is incorrect and "insufficient privileges" shows that perhaps you are using SYS user for running the jobs and password for user SYS is incorrect.
If you are specifying passwords in your scripts, i don't think you need to set preferred credentials.
Try following
1) Remove preferred credentials
2) Don't check password of user sys by locally logging in (because if Os authentication is on, even wrong password will allow you loging into the database and you will think that password is correct). Try connecting database using SYS user from a remote machine and check whether it accepts your password and make sure you have same password for your jobs and in sql scripts
3) If still problem, just for test, remove SQLNET.AUTHENTICATION_SERVICES= (NTS) and try
Salman

Job started approx 1 hour late than scheduled.

I identified req_start_date and actual_start_date are not same. Job started 1 hour late than scheduled.
Database has been configured with following -
job_queue_processes integer 1000
processes integer 150
sessions integer 248
Please suggest, why job started approximately 1 hour latter.
Thanks for your help in advance.
Thanks
Ajay
--

Perhaps you also need to increase the PROCESSES parameter to a value of (at least) 1000?
http://docs.oracle.com/cd/E11882_01/server.112/e25494/create005.htm#ADMIN11108
Have you already tried that?

How to check why some of the Cron jobs didn't ran at the scheduled time?

This is my first question ever on the forum. Hope I'm following the format of posting the thread.
I could find a similar query on the forum but couldn't find the exact answer.
Versions:
Oracle: 11.2.02.0
Linux: Linux xxxxx 2.6.32.12-0.7-default #! SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/LINUX
In our crontab there are lot of scripts that ran at the scheduled time. Around 3 reports didn't ran at the scheduled time today?
There is no error or some error mail saying that those reports got failed. They just didn't ran at that time.
How to find out why those jobs didn't ran?
Is there anything like cron log or something like that to trace it?
Please guide me. Thanks in advance.

977789 wrote:
This is my first question ever on the forum. Hope I'm following the format of posting the thread.
I could find a similar query on the forum but couldn't find the exact answer.
Versions:
Oracle: 11.2.02.0
Linux: Linux xxxxx 2.6.32.12-0.7-default #! SMP 2010-05-20 11:14:20 +0200 x86_64 x86_64 x86_64 GNU/LINUX
In our crontab there are lot of scripts that ran at the scheduled time. Around 3 reports didn't ran at the scheduled time today?
There is no error or some error mail saying that those reports got failed. They just didn't ran at that time.
How to find out why those jobs didn't ran?
Is there anything like cron log or something like that to trace it?
Please guide me. Thanks in advance.Since this question has nothing to do with Oracle Databases and everything to do with Linux functions and usage, it would be better asked in the [url https://forums.oracle.com/forums/forum.jspa?forumID=135]Linux Forum
When posting there, you can save yourself a bit of time by going ahead and showing the line from crontab for a report that "didn't run", and perchance the script itself. Best enclosed in the / tags to preserve formatting.

How to restrict the job start conditions (only "Immediate" type) ?

Hi,
We allow our users to schedule and execute in background mode transactions (example IP19, IW38). We gave them for that authorizations (object S_BTCH_JOB with LIST, PROT, RELE and SHOW - objetct S_PROGRAM with BTCSUBMIT).
We would like that users can schedule and execute their jobs only with the u201CImmediateu201D job start condition (in the Start Time screen for the type of start condition : Immediate, Date/Time, After job, After event, or At operation mode).
Another solution: prohibit the scheduling and the execution background job in a certain time interval ...
How can restrict the job start conditions ?
Thank you.
Patrice.

Hi Jan,
Yes, sa38 makes it possible indeed to execute in background into immediate mode a job but
the user have to know the name of the program to be carried out ...
The user knows only the name of these transactions trade. For example, IW38.
In the menu of this transaction, SAP gives the possibility to execute in background :
Program --> Execute in Background --> display of Start Time screen for the type of start condition :
Immediate, Date/Time, After job, After event, or At operation mode).
It is at this time there that we want that the user can only choose the "immediate" mode.
We must thus prohibit the other choices (Date/Time, After job, After event, or At operation mode) ... and
and we don't know how to restrict these other options in this screen "Start Time screen for the type of start condition".
Thank you.
By.

Job starts in un-scheduled time

Similar Messages

Maybe you are looking for