Re: weird issues with large# of jobs

Are you checking to see if there are locking and latching issues? At a wild guess, I'd say locks are taken out for the index creations, and with all the contention of system tables for the ddl, things are happening in the wrong order.

If it's not something as silly as using a single table to keep the name of the current index being rebuilt in your sql.

When scripting ddl, serialization and sanity checks are important. You can't just assume things you've fired off are going to work.

For example, create a table, select a row for update.

In another session, drop the table. You'll get an ora-00054.

That's just one legitimate example of things that can go wrong (in this case, implying a user/app left something out there), more difficult to demonstrate things can happen with a non-scalable solution as you've described. That's not even getting into plain old bugs. If you could prove a jobs bug where info gets swapped, that would be real scary.

jg

--
@home.com is bogus.
Entry on "funny worst resumes" is real:
http://ihatemylife.us/story.html