This content has been marked as final. Show 2 replies
Oracle Scheduler is a substantially superior product in just about every way imaginable.
1. Works the same on every hardware platform and operating system.
2. Requires knowledge of only a single product and language across all platforms.
3. Work can be exported/imported
4. Work is backed up with normal RMAN backup
5. Works seamlessly if moving from single-instance to RAC
6. Performance is identical
7. Data dictionary provides lots of metrics
8. Far more secure
9. I'd favour tossing out the KSH scripts and coding it all inside the database to leverage the increased portability ... but either way ... plunk the output into tables or write it to a text file.
The demos here may help:
Thanks for the response,
I think I agree with everything you said.
"I'd favour tossing out the KSH scripts and coding it all inside the database."
Me too and that will increase performace because shell script woudln't need to waste resources on a sql net connection. But unfortunatly a lot of what my scripts do is move files around, or create oracle reports (I'd like to toss that also).
I have 3 chapters of the Oracle Admin guide to read on concepts, 116 pages of pl_sql package reference, and "Mastering Oracle Sheduler" by Ronald Room.