 |
|
Oracle Replication Tips by Burleson |
Using Oracle dbms_job
You can use the dbms_job
package to administer jobs within your own schema. The
dbms_job
package allows you to:
-
“Break”
or “Unbreak”
a job using the dbms_job.broken
procedure.
-
Change the interval between jobs with the
dbms_job.interval
procedure.
-
Change the next execution date for a job with the
dbms_job.next_date
procedure.
-
Remove an existing job using the dbms_job.remove
procedure.
-
Run an existing job using the dbms_job.run
procedure.
-
Add a job using the dbms_job.submit
procedure.
-
Query the job scheduler for the description of the job with the
dbms_job.what
procedure.
Note that when using dbms_job,
only the user that created the job has the ability to change or
delete the job.
However,
privileged accounts such as SYS can use the dbms_job
package to administer any job in the system. Most of the procedures
in dbms_job
are in dbms_job,
though some parameters may differ. An example of a procedure
that is not in dbms_job is the
CHANGE procedure.
In some versions of Oracle (it also appears to be version specific)
you may
need to issue a commit after an execution of the dbms_job
command. If you find that your calls to dbms_job
do not appear to be working, try issuing
a commit afterwards.
This is an
excerpt from Oracle Replication By Rampant TechPress (only $19.95).
You can click here to order a copy and get instant access to the code
depot:
http://www.rampant-books.com/book_2003_2_replication.htm
Get a Personal Oracle
Replication Mentor
The author is now offering personal mentors for
Oracle DBAs where you can have an Oracle expert right at your
fingertips, anytime day or night. We work with hundreds of Oracle
databases every year, so we know exactly how to quickly assist you
with any Oracle replication question.
You can get me personally, or any Oracle Certified replication DBA
with more than 20 years of full-time IT experience.
|
