I have recently installed Oracle on my laptop (v 9.2.0.1.0). A
database was created as part of the installation and that seems fine.
However i have since created a new database using scripts as I want to
replicate another database we have. I have run catalog.sql and that
didn't take long but am currently running catproc.sql and it seems to
be taking a very long time. I have tried it once and left it running
for 12 hours and still hadn't finished. On checking the log, however,
I realised that it needed the database to be open as errors were
occuring (mine was started but not mounted). I started it the database
and ran catalog.sql again and started catproc.sql (a couple of hours
ago) and it's still going. Is this normal?? Any suggestions as to why
it could be taking so long would be much appreciated

Cheers
Jude

Jude wrote:

There seems to be an awful lot of fumbling and stumbling going on there. The
script of course needs to be run with the database fully open as it is
about to create a lot of objects *within* the database. It also needs to be
run (like catalog.sql) as SYS.

Yes, catproc can take a long time to run. I used to get my classes to start
it as they left for lunch. It was invariably finished by the time they
returned or shortly thereafter. Therefore, on a Pentium III 866MHz, expect
it to take 1 hour.

Make sure your database is not in archivelog mode when you run it. If you
have to be inarchivelog mode, make sure that ARCH has been started and can
generate all and every archive log that it needs to.

After that, it's time to start wondering about your memory allocations and
your I/O issues generally, and the only thing that's going to be of
definitive help there is Staspack.

HJR

It happened to me a couple of times (running for more than 2hrs). Now
I do a 'set term off' in sqlplus before running the catproc.sql script
and don't have this issue. So, you might want to give it a shot.

-Madhu S

judeyjazz (AT) hotmail (DOT) com (Jude) wrote in message news:<5cdd50fb.0409080213.5fa1898c (AT) posting (DOT) google.com>...

Is this normal?? Any suggestions as to why
I would recommend increasing the size of your redo log files... if
they are very small (i.e. default), catproc.sql can take ages to run.

Try setting them to between 10 and 30 Mb.

Matt