Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!zephyr.ens.tek.com!tektronix!sequent!crg5!larrys
From: larrys@crg5.UUCP (Larry Scheurich)
Newsgroups: comp.databases
Subject: Re: Oracle Application Foundation on Suns
Keywords: Oracle, Version-6, Sun, NFS, Application Foundation
Message-ID: <19876@crg5.UUCP>
Date: 29 Aug 90 15:24:12 GMT
References: <5559@thebes.Thalatta.COM>
Reply-To: larrys@crg5.UUCP (Larry Scheurich)
Distribution: na
Organization: Sequent Computer Systems, Inc
Lines: 44

In article <5559@thebes.Thalatta.COM> depner@Thalatta.COM (August Depner) writes:
>We're trying to bring up Oracle Application Foundation on a Sun 3/50,
>without success so far.
>
>The barebones DBMS runs fine, but when we try to install Application Foundation,
>the install script bombs after a while with an ORACLE error of 01547 - failed to
>allocate extent of size 'xxx' in tablespace 'SYSTEM'.  We've pared down what we're installing and
>increased the size of tablespace 'SYSTEM'  several times with no luck. At present, we are allocating
>over 100 Mb of diskspace to ORACLE, and cannot complete the install.

I've worked extensively with this product for the last two years, and have
some suggestions that may help.

If your database only contains a system tablespace, that may be your problem.
One of the very first steps of the install is to do a very large import of
a user known as APPLSYS.  This user contains all of the database information
about Application Foundation.  If you have only one tablespace, you're 
probably getting "nailed" by rollback segments that are trying to grow
in the same tablespace that the data's going into.  In order to verify this,
you may want to run sqldba/monitor while the import's runninng to see
if that's the problem.  I suspect that this is the problem.  If it is,
you have three possible solutions:

1.  cd $FND_TOP/install/import
	- look at the file afsys40.dat (I think that's the name).  This file
	  contains the import parameters.  Make sure that it contains a line
	  that says COMMIT=Y.  This will help reduce rollback segment growth.
    then, re-run the install.
2.  Create two tablespaces other than your system tablespace.  Use one solely
    for rollback segment, and the other for applsys's data.  This will allow
    the rollback segments to grow without running into contention with the
    import.
3.  change the storage parameters on your rollback segments.  The keys are
    initial extent and pctincrease.

Let me know if this doesn't help, and I'll see if there's anything else that
we've done.

--
Larry Scheurich				uunet!sequent!larrys
Sequent Computer Systems		(503)-526-4240
Beaverton, OR

"Smile, it makes people wonder what you're up to"