Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering Oracle Scheduler in Oracle 11g Databases

You're reading from   Mastering Oracle Scheduler in Oracle 11g Databases Schedule, manage, and execute jobs in Oracle 11g Databases that automate your business processes using Oracle Scheduler with this book and eBook

Arrow left icon
Product type Paperback
Published in Jun 2009
Publisher Packt
ISBN-13 9781847195982
Length 240 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Ronald Rood Ronald Rood
Author Profile Icon Ronald Rood
Ronald Rood
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Mastering Oracle Scheduler in Oracle 11g Databases
Credits
About the Author
About the Reviewers
1. Preface
1. Simple Jobs FREE CHAPTER 2. Simple Chain 3. Control the Scheduler 4. Managing Resources 5. Getting Out of the Database 6. Events 7. Debugging the Scheduler 8. The Scheduler in Real Life 9. Other Configurations 10. Scheduler GUI Tools

Rules


Rules in a chain describe the way the Scheduler should read the job description. A chain must have a proper starting point and end point. Steps in a chain are activated when the rules in the chain definition evaluate to true (as rules are Boolean) and mention the specific step names to be started.

Let's return to the backup example once more. We know there is only one location where it makes sense to start the job—the step that shuts down the database. How can we make the Scheduler know that? Let's start with an overview of what we know. The steps are:

  1. 1. Always start with SHUTDOWN.

  2. 2. If SHUTDOWN is successful, start COPYFILES.

  3. 3. If COPYFILES is successful, start STARTUP.

  4. 4. If STARTUP is successful, start END 0.

    This lists the optimum order of executions, but does not take into account a situation with failures. What should we do if SHUTDOWN fails? What should we do if COPYFILES fails? What should we do if STARTUP fails? If it is important that we act on a status, we should tell this...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image