Oracle Booksellers

Oracle Scheduler makes a lot of things outside the box, and if the requests are not too high, Oracle Scheduler can cover most situations. When the application needs to run to many thousands of jobs in an hour and record over a long period, a smaller attention is necessary. In cases where requests are high, beware of a few more things to keep the system happy. What we do depends on how planning is used and what kind of load that should be managed.

In this chapter we will see more closely how you can control this beast. We will consider the privileges to create jobs, running jobs, and management planning. It will also examine how to control the registration of conservation and find a way to prevent the execution of the work when the database starts.

Job creation

Like most types of database objects, as we saw at the beginning of Chapter 1, Oracle allows us to create objects of planning. Privileges to create jobs and create jobs outside are very important. In general, you should use to build an application system. There is also a creation of any privilege of employment, which can be useful when you need to create a job in a different scheme. Typically, this privilege should not be granted to anyone. This will enable the receiver to execute arbitrary code on any scheme, which is not particularly desirable. Instead, simply register with the schedule correctly and carry out tasks with the appropriate privileges.

(A table showing the privileges to download below).

Here, it is interesting that the fall of every privilege of working seems to be missing. For other types of object, and creates no privilege to drop all privileges. By using these privileges every aspect elegant at first sight. However, making the system more transparent and more difficult to maintain finish. Preferably, the objects are explicitly granted, instead of falling into any privilege to build an application. For example, select any table and you realize it is much harder to find a way to flow demand or what the impact of a falling object. If permissions are explicitly granted, we can see that someone is using our object.

Above all, it is smarter to build lists with fewer privileges principle. This means that one or more schemas contain tables that contain data and other models contain the procedures that act on different tables. Users or functions must have the privileges of the procedures.

DBMS_SCHEDULER The package is available to the public. The use of the package is controlled by the privileges then how to create jobs, management planning, implementation and privileges DBMS_SCHEDULER package products such as employment, programs and job classes.

Click here to download the entire chapter.

To learn more about the book click here: http://www. packtpub. com/mastering-oracle-scheduler-in-oracle-11g-databases/book