Re: System Tablespace gone mad!

Interesting you should mention a runaway compilation, as a week or so ago, a developer had such an occurence, where a fairly pedestrian compilation simply hung his session. I think we ended up killing the session, and a repeat of the compilation completed without incident.

I can't really thing of why something as simple as a package compilation could trash an instance. I don't think it was a particularly large package, and I know that the package was not in-use at the time it was compiled (which sometimes causes prolonged compile times). Most of our development is for web-based packages, which don't spend a great deal of time in the database at any one time.

One of the mysteries of Oracle, I suppose.

Now, repeat after me :-

Oracle is STILL the best relational database, Oracle is STILL the best relational database, Oracle .....

;-)

Rich Woodland.
Magic Interface, Ltd.

Ricky Sanchez wrote:

> Rich-
>
> I seem to recall if Designer 2000 is installed an option is offered to
> increase idl_ub2$ storage parameter and perhaps another table as well,
> but I don't recall the details. Is it possible someone installed either
> Designer or another similar tool and applied some absurd value to the
> option?
>
> Or perhaps some huge runaway plsql compilation took place, grew the
> table and maybe later the plsql objects were dropped but the table is
> still huge? I would look for something silly to have happened, which
> means *nobody* will admit to having done it.
>
> - ricky
>
> Richard Q Woodland wrote:
> >
> > A few days ago, the system tablespace on our development server
> > filled-up, and hit a half gig. At that time, we doubled the system
> > tablespace to over a gig. Today, it's back to being filled up.
> >
> > The load on this server, and the amount of development work being done
> > has not changed in any significant way over this period of time.
> >
> > The chief space hogs in system seem to be SYS.IDL_UB2$ (500+ Mb) and
> > SYS.I_SOURCE1 (614Mb).
> >
> > I can't imagine what a handful of users could possibly generate enough
> > PL/SQL source code to consume a half gig in three days!!
> >
> > Can anybody think of a scenario which might cause these two entities to
> > start to ballon in size?
> >
> > Thanks (in advance) for any comments!
> >
> > Rich Woodland.
> > Magic Interface, Ltd.
Received on Fri Nov 02 2001 - 06:53:46 CST