woensdag, september 02, 2009

Oracle Scheduler in 11gR2 - p1

rdbms installation


Now that oracle 11gR2 can be downloaded and the documentation is available it is time to dive into the new features of the Oracle Scheduler.


A single day to play is not enough to see everything but the changes start immediately at the beginning, the installation, or even before that, the download. The 11.2.0.1.0 rdbms installation consists of 2 zip files of about 1GB each that have to be merged. Together they form the database directory.


unzip -qq linux.x64_11gR2_database_1of2.zip
unzip -qq linux.x64_11gR2_database_2of2.zip

The result of this is the database directory where the runInstaller script can be found. The setup of the response files is a bit different than from 11gR1 and so is the setup for the root.sh that is generated at the end of the installation.


If you are used to do some customization there are more scripts that need attention now. Also the prerequisites are more tight than they were for 11gR1.


schagent installation


In 11gR1 we could find the schagent as part of the gateways installation, this time check the client installation first if you are going to use the new schagent. It does make a little more sense, the Scheduler Agent can be seen as some kind of a client that connects to the database.

improvements


There really are some improvements visible.

  • We can now see the locations that are available to schedule jobs to.

  • We can now define a job to generate an notification email for every status change in the job.

  • We can now define jobs to wait for a file arrival event.

  • We can now scheduler pl/sql type of jobs to a remote database

  • We can now use the schagent as a file watcher

  • ... more diving to do ...


Is this all? No, there will be more. If time allows I will follow-up soon with more details and maybe with remaining wishes. I already saw that in the put_file procedure the permission bits are still reserved for future use. This could be very useful to use for OS-script distribution/placement.


One of the next things to check is the resource manager integration for remote external jobs. I do really hope that at least the session pool is now useable to control the number of jobs that a database can send to an agent.


One thing is for sure, there is more work to do for the Oracle Scheduler integration in DbVisualizer.

OOW 2009


This year I will be visiting Oracle Open World. With a little luck we can meet. I will be on the publishers conference on Tuesday and for the Monday I tried to reserve a spot for the Unconference on Monday afternoon.