BC remote Oracle DBA - Call (800) 766-1884  
Oracle Consulting Oracle Training Development

Remote DBA

Remote DBA Plans  

Remote DBA Service

Remote DBA RAC

   
Remote DBA Oracle Home
Remote DBA Oracle Training
Remote DBA SQL Tuning Consulting
Remote DBA Oracle Tuning Consulting
Remote DBA Data Warehouse Consulting
Remote DBA Oracle Project Management
Remote DBA Oracle Security Assessment
Remote DBA Unix Consulting
Burleson Books
Burleson Articles
Burleson Web Courses
Burleson Qualifications
Oracle Links
Remote DBA Oracle Monitoring
Remote DBA Support Benefits
Remote DBA Plans & Prices
Our Automation Strategy
What We Monitor
Oracle Apps Support
Print Our Brochure
Contact Us (e-mail)
Oracle Job Opportunities
Oracle Consulting Prices





   

 

 

 

Remote DBA services

Remote DBA Support

Remote DBA RAC

Remote DBA Reasons

Remote Oracle Tuning

Remote DBA Links

Oracle DBA Support

Oracle DBA Forum

Oracle Disaster

Oracle Training

Oracle Tuning

Oracle Training

 Remote DBA SQL Server

Remote MSSQL Consulting

Oracle DBA Hosting

Oracle License Negotiation

 

 


 

 

 

 

 
 

Automating Oracle

Oracle Tips by Mike Ault

The DBMS_JOB Package

We will be looking in detail at the SUBMIT, ISUBMIT, RUN and REMOVE procedures in the course of this presentation. For a more detailed discussion of how this package is used look in “Oracle Built-In Packages” by Steven Feuerstein, Charles Dye and John Beresniwicz from O’Reilly Publishing or “Oracle8 Administration and Management” by Mike Ault from Wiley and Sons publishing.

To submit a job to the job queues you use either the ISUBMIT or SUBMIT procedures. The difference between ISUBMIT and SUBMIT is that with ISUBMIT you must set the job number manually while with SUBMIT a job number is pulled from an internal sequence. The standard for both of the procedures is:

DBMS_JOB.SUBMIT(job_num, what, next_date, interval, no_parse)

Where:
 
            Job_num         is a number (an IN for ISUBMIT, and OUT for SUBMIT)
            What                is a specific PL/SQL action
            Next_date        is a date expression for when the action should first be taken
            Interval                         is a character string that evaluates to a date in the
future
            No_parse         is a boolean the specifies when the PL/SQL should be parsed (defaults to false)

An example job submission using the  ISUBMIT procedure would be:

EXECUTE DBMS_JOB.ISUBMIT(999,’BEGIN testit; END;’,SYSDATE,’SYSDATE+(15/1440)’);

SEE CODE DEPOT FOR FULL SCRIPTS


For more information on this topic, I recommend Don Burleson's latest book "Oracle Tuning: The Definitive Reference". 

You can buy it direct from the publisher for 50%-off and get instant access to the code depot of Oracle tuning scripts:

http://www.rampant-books.com/book_1002_oracle_tuning_definitive_reference_2nd_ed.htm


Expert Remote DBA

BC is America's oldest and largest Remote DBA Oracle support provider.  Get real Remote DBA experts, call
BC Remote DBA today.

 

 

Remote DBA Service
 

Oracle Tuning Book

 

Advance SQL Tuning Book 

BC Oracle support

Oracle books by Rampant

Oracle monitoring software

 

 

 

 

 

 

BC Remote Oracle Support

Remote DBA

Remote DBA Services

Copyright © 1996 -  2013 by Burleson. All rights reserved.

Oracle® is the registered trademark of Oracle Corporation.



Hit Counter