Suspend automation jobs from running on weekends?

Every month, our W2K3 servers reboot over a weekend to activate security patches and updates released by microsoft. If any portal automation jobs are running when the server reboots, the next time they run, they fail because the operation is locked. We have many jobs that run every 10 or 15 minutes, so over the course of a weekend after a reboot, this causes many failures. We would like to suspend the jobs either nightly or just every weekend during off hours, but there is no way to do that via the job settings in Admin.
I found some references to such things in the PT tag reference - PT_SCHEDULE_SUSPEND_WEEKEND_BEGIN_TIME and PT_SCHEDULE_SUSPEND_WEEKEND_END_TIME, but I have no idea where or how to use such code. Actually, I'm not 100% sure that code is for the automation service (what else would it be though?). Oracle being Oracle, there is no sample code on how to use it or even a description of what it's for.
Any ideas on how to suspend automation jobs from running during certain hours on the weekends would be greatly appreciated. Thanks.

user2604361 wrote:
Any ideas on how to suspend automation jobs from running during certain hours on the weekends would be greatly appreciated. Thanks.I have zero idea if this is possible, but I'm wondering if it would be possible to create a .bat file that turns them all off on Friday night and reactivates them all on Monday morning. I've heard that the Automation service can run custom jobs to do such things although I've never attempted it.
Sorry I can't be any help! Whatever solution you come to, please post back here as I'm interested in what you come up with!

Similar Messages

Retrospect automated jobs dont run

I have recently noticed that on one of my xserve (10.3.9 server) the automated Retrospect (6.0.204) jobs fail to automatically start at the scheduled time. I have a backup job to external FW 800 running at 12.01am and a backup job to tape at 04:00am. If I login to the server in the morning and run Retrospect application the "queued" jobs immediately start to kick in. Any ideas why this would happen?

Try to leave the machine logged in when Retrospect is supposed to run. Since it is an application it should require the user be logged in.

Job not running in DBA_Jobs

Hi,
We have a job set in dba_jobs.
Suddenly after 31st mar-2011 the job is not running
The job of 31st mar 2011 is still in active state and exists in the database
The details of the job are as follows:
SELECT r.sid, r.job, r.this_date, r.this_sec, SUBSTR(what,1,40) what
FROM dba_jobs_running r,dba_jobs j
WHERE r.job = j.job;
SID JOB THIS_DATE THIS_SEC
439 65709 31-MAR-11 06:31:54
A OS process also exists
oracle 11130 1 0 Mar 31 ? 1:51 ora_j000_GAT
SQL> select status, to_char(logon_time,'dd-mm-yyyy:hh24:mi:ss') from v$session where sid=439;
STATUS TO_CHAR(LOGON_TIME,
ACTIVE 31-03-2011:06:31:29
SQL> select THIS_DATE,NEXT_DATE from dba_jobs where job=65709;
THIS_DATE NEXT_DATE
31-MAR-11 31-MAR-11
In long running SQL
439 SELECT TO_CHAR(HPEOP_EIN) EMPLID, NVL(HP GAT_OWNER 31-03-11:06:31:29 ACTIVE
EOP_GRADE,' ') JOBCODE, NVL(HPEOP_PREFER
RED_PHONE,' ') BT_PREFERRED_COMMS, NVL(H
The jobs usually take 1-5 mins
Can you please advice what needs to be done
What could have happened.

Can you kill the job from the OS?
Then stop the job from running : set it to broken
Find out why it doesn't stop this time: look in code and data.
If you are confident it will not happen again schedule the job again.

Can not see running jobs from, package

I have a problem with processing parallely runing jobs:
I am creating another immediately runned jobs in a main job. Those two parallel jobs (2 loads from different databases) have to be finished before I run next operation (working out loaded data). Problem is that, after starting those 2 parallel jobs, I can not see them by select from ALL_SCHEDULER_RUNNING_JOBS that is executed immediately after I create those jobs in a package. If I take a look into ALL_SCHEDULER_RUNNING_JOBS from anonymous statement I can see all my running jobs. Let's sum it up:
1/ Start of main job
2/ Running 2 immediately created jobs (load data)
3/ Checking in loop if jobs created in step 2 are still running
3.1/ Jobs are running (ALL_SCHEDULER_RUNNING_JOBS check) - sleep for a
while - It never happens - can't see any running jobs from select executed in
package but can see them in
anonymous statement
3.2/ Jobs finished - start processing loaded data
Can somebody help me with this task?
Thanks alot!
Jakub

Hi,
There is no reason a job should be visible from an anonymous block but not from inside a job. There are two things that may be happening here.
- jobs scheduled to run immediately my not start running as soon as they are created/enabled, you may need to wait a bit before they start running (they will appear in all_scheduler_jobs immediately but maybe not all_scheduler_running_jobs immediately)
- you may be running into privilege issues. Is the user that executes the anonymous block the same as the user that the job is running as (the job's schema) ? If not maybe the job user does not have privileges to see the job (you can grant alter on the job to the user to ensure this).
Can you see the jobs in the all_scheduler_jobs view from within the job with status RUNNING ? If you can see jobs in all_scheduler_jobs as RUNNING but not in all_scheduler_running_jobs then this is a bug of some sort.
Thanks,
Ravi.

How Can I Run a SQL Loader Job from Schedular

How Can I Run a SQL Loader Job from Schedular , So that It Runs every Day.

Depends on a couple of factors.
If you are on a UNIX platform, you can create a shell script and schedule it with cron.
If you are on a Windows platform, you can create a batch file and schedule it with the Windows scheduler.
Or, if you are on Oracle 9i or 10g, you could use the external table feature instead of SQL*Loader. Then you could write a stored procedure to process the external table and schedule it using the Oracle scheduler (DBMS_JOB). This would probably be my preference.

Running a SQL Loaded Job from Schedular

How Can I Run a SQL Loader Job from Schedular ,
Message was edited by:
jus

The trick is to create a wrapper script that is referred to by the PROGRAM object with arguments. The wrapper should do the work.
/usr/local/bin/do_sqlldr.sh:
#!/usr/bin/env ksh
# setup actions
sqlldr control=...
Don't forget to check who is the owner of $ORACLE_HOME/bin/extjob and that the owner is available.
My question is how this can be fitted in an DTAP environment where Developement and Test environment are on the same server and have the same job definitions. Development and Test should use different datafile and logfile locations.
regards,
Ronald
http://ronr.nl/unix-dba

DBMS_JOB.RUN: cannot run a job from a job

I'm trying to set up a job to automatically run every October 1st. The "submit" part of this job is pretty simple, but I am getting some errors on the "run" part:
declare
job_nbr binary_integer;
BEGIN
dbms_job.submit(job => job_nbr,
          what => 'RESET_ORDER_NBR_SEQ;',
          next_date => to_date('10/1/2008', 'mm/dd/yyyy'),
          interval => 'add_months(sysdate,12)');
dbms_job.run(job_nbr);
COMMIT;
END;
When I run this script, I get the following error: "ORA-32317: cannot run a job from a job". I know this is due to the dbms_job.run because I don't get the error when I comment this line out. Also, even when I moved the dbms_job.run into its own script (and even hard-coded the job_nbr, so the dbms_job.run was the only line in the script), it still gave me the same error. This is working in SQL Developer when but not in Application Express. It seems to be something specific to the "run", since "submit" and "remove" work fine. Has anyone had any problems like this?

MBETTIS,
Rather than including dbms_job.run in your PL/SQL block, why don't you just schedule the job to run via next_date?
Also, the interval will be computed after the job successfully executes. So if your job takes 5 minutes to run, the value of SYSDATE in your interval may "slide" after each execution. Consider using some form of TRUNC against the SYSDATE in your interval if you want to achieve a consistent execution time.
Joel

Run job from another user

Hi, first of all, sorry for my pour english.
I'm system in a db, and i need to run a job from another user. I don't have the password. Theres a way to run this job?
It's a oracle db 10g enterprise.
Thanks in advice.

I have the permissions, and I can't change the user password or application may stop. There's a way, but I just can't remember:
PRIVILEGE
ANALYZE ANY
UNLIMITED TABLESPACE
CREATE TABLE
ALTER TABLESPACE
ALTER DATABASE
GLOBAL QUERY REWRITE
CREATE MATERIALIZED VIEW
SELECT ANY TABLE
8 linhas selecionadas.
Decorrido: 00:00:00.21
PRIVILEGE
FLASHBACK
DEBUG
QUERY REWRITE
ON COMMIT REFRESH
REFERENCES
UPDATE
SELECT
INSERT
INDEX
DELETE
ALTER
FLASHBACK
DEBUG
QUERY REWRITE
ON COMMIT REFRESH
REFERENCES
UPDATE
SELECT
INSERT
INDEX
DELETE
ALTER
FLASHBACK
DEBUG
QUERY REWRITE
ON COMMIT REFRESH
REFERENCES
UPDATE
SELECT
INSERT
INDEX
DELETE
ALTER
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
SELECT
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
EXECUTE
SELECT
SELECT
EXECUTE
EXECUTE
EXECUTE
WRITE
READ
WRITE
READ
WRITE
READ
69 linhas selecionadas.
Decorrido: 00:00:00.48
GRANTEE GRANTED_ROLE ADM DEF
SYSTEM MGMT_USER NO YES
SYSTEM TRIPOA_READ YES YES
SYSTEM DBA YES YES
SYSTEM TRIPOA_WRITE YES YES
SYSTEM AQ_ADMINISTRATOR_ROLE YES YES
SYSTEM TRIPOA_EXEC YES YES
SYSTEM PRIV_DML_STUDENTSLOG YES YES
SYSTEM PRIVILEGE_ALL_TRIPOA YES YES
8 linhas selecionadas.

How to research a long running job from 3 days ago

Re: How to research a long running job from 3 days ago
Client called to say that a job that normally runs for 6 hours ran for 18 hours on 11/01. 11/01 was a Saturday, and end of month. The long running job writes to a log and I can from the log that that the problem started right around 10:43am. Every step
before 10:43 was taking the normal amount of time. Then at 10:43 a step that takes seconds hung for 12 hours. After 12 hours the step finished and the job completed successfully.
I looked at the SQL Log, Event Log, Job History (for all jobs). What else can I look at to try and resolve an issue that happened on 11/01/2014?

It does execute an SSIS package.
Personally I feel this as kind of bug in SSIS package but I am not expert in SSIS so I would move it to SSIS forum. Please update your question giving complete information what SSIS package does.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

Email address not showing up in TO box of outlook when a job is run from OBIEE agent

HI Everone,
I am running an Agent in OBIEE 11g(11.1.1.5), we are sending report's output as excel/pdf. Jobs are running fine, but we don't see user's email address in TO box of their outlook(inbox). Is there any settings which I can enable, so that agent can show user's email address upon delviery, right now TO box of inbox is blank.
Thanks for help in advance.

Even I don't think its an version issue. But, at the same time, I am not sure how to get it(email address in TO box of outlook). Just wondering, is this setting done in OBIEE or Outlook

Re-planned jobs from DDIC which have deleted with program RSBTCDEL

Hi Experts,
I deleted jobs planned by the DDIC from transaction db13 by mistake.
When you run the job scheduled for the day that is planned, the job status remains "Released./Susp." and it doesn't work. Since the transaction db13, the state is scheduling the planned action failed.
Someone can tell me how I can re-planned the job for executed from the scheduler (db13)?
Thanks in advance!
Regards
XeviG.

;Released./Susp.' status is due to the fact that someone might had run BTCTRNS1 report in this sap system. That's why the jobs are suspended temporarily. It might happen that all other jobs are suspended too, not just db13 related jobs in this system. So to reset the jobs' status you execute BTCTRNS2.
However, as you have deleted the jobs from DB13 then better reschedule them from DB13 itself instead of trying to execute them from SM37.

Delete scheduled jobs from previous days

Post Author: supermeerkat
CA Forum: Administration
I look after a Business Objects server that runs about 400 reports per day.
Over the weekend the CMC stopped, nothing was reported in the logs, no attemps at restarting occured. But this isn't the problem.
When I restarted the CMC it started up with no problems, but in the
Instance Manager, it has started running the scheduled reports from the
day it stopped (Sunday the 4th May). It looks like it'll work through
all of the scheduled reports from Sunday, then Monday, before it gets
to today (Tuesday).
Is there any way I stop it from running the scheduled reports from
Sunday and Monday, and just have it run Tuesdays reports? Any help
would be gratefully recieved.

Nope. You can't get that, if house keeping jobs are scheduled.
Regards,
Subhash

Cron job not running - script uses rsync, ssh (with id_rsa)

Does anyone know how to get cron to run a rsync/ssh script which uses id_rsa for passwordless logins?
I have a backup script I have slaved for months over that works wonderfully when running it from the command line.
It uses rsync and connects with SSH (passwordless using ssh keys). I have setup id_rsa and id_rsa.pub for passwordless logins (this is my user account, and connects using root@ to the server)
As stated all works find when run from the command line. But when I setup a cron job to run this file (exact same line I run from the command line) it does not execute. Actually, it does run, as I have an email notifiction which sends to me. It is just the rsync/ssh part that does not run.
I have spent days and days trying to figure it out. No error messages occur, nothing. Took me a while to find out cron is emailing the user account on Lion the messages (not to a proper email address).
The error shows a permission denied, which I believe to be the cron user cannot use the id_rsa/ssh connection.
Cron is running the script as my user, the same I use on the command line. I even tried copying the id_rsa to the root user .ssh folder in case cron is running as root but that does not work either.
So does anyone know how to get cron to run this rsync/ssh script which used id_rsa for passwordless logins?
Thanks a lot

YES! Got it working, finally!
So the issue is indeed cron/launchd not being able to access the ssh-agent which holds the key.
So this is the solution...
Download keychain for Mac:
http://www.funtoo.org/wiki/Keychain
Then once its installed and configured, the script to run needs this added to the top:
eval `keychain --noask --eval id_rsa` || exit 1
Note I am using id_rsa whereas keychains instructions refer to id_dsa so I just changed it and it works OK.
When the script runs the first time it asks for the key password. Then it works from then on.
What I do not know yet is will I need to re-enter the password when I logoff/logon again. That will cause an issue as I auto restart the Mac every day which means if I am off for a few days backup will stop (can you see the madness in this issue!).

An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))

We are using DPM Version: 4.1.3465.0 with System Center 2012 Service Pack 1 to back up VMs in our Hyper V Cluster. We have a total of 37 VMs with a combination of 2008r2 servers and 2012 servers. One of our 2012 servers will not backup, and we consistently
get the message "An unexpected error occurred while the job was running. (ID 104 Details: The parameter is incorrect (0x80070057))". I have seen this error message when I Googled it, but cannot get past it. I have deleted the Protection Group and
data and tried to re-create, but get the same errors. I also thought the the server might be mis-reporting the data size, but I expanded that to cover the replication data. I have also tried to perform consistancy checks multiple times with no luck. I have
not seen a difinitive answer from my Google searches, so was hopeful someone has seen this also, and have had success in resolving. Currently this server has no backup recovery points, so I am worried if it does crash. I think I have the rollups installed
as well.

Hi Kelly,
does the issue still persists?

Submitting job from a procedure

Hi,
I need to submit a job and call it frm a procedure. I need to run the job exactly at 12 in the midnight. How will i pass the start_time to the job? the problem i face here is the procedure can be called on any date. following is the procedure
CREATE OR REPLACE PROCEDURE JOBS(DT NUMBER)
AS
L_JOB NUMBER;
BEGIN
     FOR I IN (SELECT JOB FROM USER_JOBS WHERE WHAT LIKE 'SPARCHIVE%')
     LOOP
           DBMS_JOB.REMOVE(I.JOB);
     END LOOP;
     DBMS_JOB.SUBMIT(L_JOB, 'SPARCHIVE('||DT||');', SYSDATE , 'sysdate+1');
     commit;
END;
/pls help me how to do it.
Thanks
Muneer

Current date and time
SQL> SELECT to_char(sysdate, 'DD-MON-YYYY HH24:MI:SS') FROM dual;
TO_CHAR(SYSDATE,'DD-
18-OCT-2004 13:13:09the previous midnight...
SQL> SELECT to_char(trunc(sysdate), 'DD-MON-YYYY HH24:MI:SS') FROM dual;
TO_CHAR(TRUNC(SYSDAT
18-OCT-2004 00:00:00the next midnight...
SQL> SELECT to_char(trunc(sysdate+1), 'DD-MON-YYYY HH24:MI:SS') FROM dual;
TO_CHAR(TRUNC(SYSDAT
19-OCT-2004 00:00:00Okay?
Cheers, APC

Suspend automation jobs from running on weekends?

Similar Messages

Maybe you are looking for