Path: dp-news.maxwell.syr.edu!spool.maxwell.syr.edu!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!postnews.google.com!i39g2000cwa.googlegroups.com!not-for-mail
From: "Joel Garry" <joel-garry@home.com>
Newsgroups: comp.databases.oracle.server
Subject: Re: weird issues with large# of jobs
Date: 17 Apr 2006 15:07:22 -0700
Organization: http://groups.google.com
Lines: 27
Message-ID: <1145311642.889621.317340@i39g2000cwa.googlegroups.com>
References: <u7v742d17fbqtqb09j8441nobaj6rmnq0v@4ax.com>
NNTP-Posting-Host: 67.116.125.178
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
X-Trace: posting.google.com 1145311648 23644 127.0.0.1 (17 Apr 2006 22:07:28 GMT)
X-Complaints-To: groups-abuse@google.com
NNTP-Posting-Date: Mon, 17 Apr 2006 22:07:28 +0000 (UTC)
In-Reply-To: <u7v742d17fbqtqb09j8441nobaj6rmnq0v@4ax.com>
User-Agent: G2/0.2
X-HTTP-UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0),gzip(gfe),gzip(gfe)
X-HTTP-Via: 1.0 ISA2K4-OC1
Complaints-To: groups-abuse@google.com
Injection-Info: i39g2000cwa.googlegroups.com; posting-host=67.116.125.178;
   posting-account=YRNZ5wwAAAAg-yYjMFwy3FyWUbPiwNdq
Xref: dp-news.maxwell.syr.edu comp.databases.oracle.server:265666

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

