RE: Oracle Job Scheduling
- From: "Xu, Roger" <Roger.Xu@xxxxxxxx>
- To: "Goulet, Richard" <Richard.Goulet@xxxxxxxxxxx>, <nigel.cl.thomas@xxxxxxxxxxxxxx>
- Date: Tue, 17 Feb 2009 09:57:17 -0700
Thanks for everyone's reply on this. It's for our internal auditors -
the SOX compliance team.
________________________________
From: Goulet, Richard [mailto:Richard.Goulet@xxxxxxxxxxx]
Sent: Monday, February 16, 2009 9:09 AM
To: nigel.cl.thomas@xxxxxxxxxxxxxx; Xu, Roger
Cc: oracle-l@xxxxxxxxxxxxx
Subject: RE: Oracle Job Scheduling
On top of that, who really cares if job scheduling in being used. Any
ERP package has a job scheduler that it uses, why should Oracle's be any
different. And if your on 10g or higher then the database does create
jobs for AWR & other maintenance tasks. Sheesh, these auditors are
getting out of hand.
Dick Goulet
________________________________
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Nigel Thomas
Sent: Saturday, February 14, 2009 1:10 PM
To: Roger.Xu@xxxxxxxx
Cc: oracle-l@xxxxxxxxxxxxx
Subject: Re: Oracle Job Scheduling
Roger
You could also show them the init.ora parameter JOB_QUEUE_PROCESSES, and
the scheduler attribute max_job_slave_processes:
"If JOB_QUEUE_PROCESSES is 0, DBMS_JOB is disabled, and the maximum
number of job slave processes for Scheduler is controlled by the
max_job_slave_processes Scheduler attribute." See the 11g documentation
<http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/appendix
_a003.htm> .
It might also help to show them that noone has been granted the various
scheduler privileges
<http://download.oracle.com/docs/cd/B28359_01/server.111/b28310/schedadm
in007.htm#i1011204> .
Regards Nigel
2009/2/13 Xu, Roger <Roger.Xu@xxxxxxxx>
Will the following 2 SQL's against dba_jobs and dba_scheduler_jobs show
auditors that we do not use Oracle Job Scheduling? Is there a better way
to convince them?
http://www.drpeppersnapplegroup.com/about/corporate to learn more about Dr
Pepper Snapple Group’s commitment to corporate social responsibility.
Please be conscious of the environment and print this email only if absolutely
necessary.
This e-mail (including any attachments) is confidential and may contain
privileged information of Dr Pepper Snapple Group, Inc. and/or its subsidiaries
("Dr Pepper Snapple Group"). If you are not the intended recipient or receive
it in error, you may not use, distribute, disclose or copy any of the
information contained within it and it may be unlawful to do so. If you are not
the intended recipient, please notify us immediately by returning this e-mail
to us at mailto:mailerror@xxxxxxxx and destroy all copies. Any views expressed
by individuals within this e-mail do not necessarily reflect the views of Dr
Pepper Snapple Group. This e-mail does not constitute a binding offer,
acceptance, amendment, waiver or other agreement, unless the intent that an
e-mail will constitute such is clearly stated in the body of the email.
Recipients are advised to subject this e-mail and attachments to their own
virus checking, in keeping with good computing practice. Please note that
e-mail received by Dr Pepper Snapple Group may be monitored in accordance with
applicable law.
Other related posts:
