RE: URGENT!!! - Inadvertantly ran catalog.sql in an existing database

  • From: "Bobak, Mark" <Mark.Bobak@xxxxxxxxxxxxxxx>
  • To: <paulastankus@xxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
  • Date: Wed, 6 Sep 2006 16:45:22 -0400

What happens if you do:
alter package standard compile;
Then try utlrp.sql not utlirp.sql  (no need to invalidate everything and
then recompile it all.  Just recompile what's not valid.)

Mark J. Bobak 
Senior Oracle Architect 
ProQuest Information & Learning 

"A human being should be able to change a diaper, plan an invasion,
butcher a hog, conn a ship, design a building, write a sonnet, balance
accounts, build a wall, set a bone, comfort the dying, take orders, give
orders, cooperate, act alone, solve equations, analyze a new problem,
pitch manure, program a computer, cook a tasty meal, fight efficiently,
die gallantly. Specialization is for insects."   --Robert A. Heinlein



From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Paula Stankus
Sent: Wednesday, September 06, 2006 4:37 PM
To: oracle-l@xxxxxxxxxxxxx
Subject: Re: URGENT!!! - Inadvertantly ran catalog.sql in an existing

Then I tried to just run standard.  
It said it created the package.
Then I tried to run utlirp.sql
It hangs and comes back with messages standard not accessible.
Now my whole machine is hanging.
Is there anyway to cleanup the catalog without recoverying the entire
I read that it might be necessary to just have online a large rbs,
create standard, run catalog.sql, run catproc.sql and utlirp.sql
Any advice is greatly appreciated.  The good thing is this is test but
it means contract $$ if we have to loose a day.  


Get your email and more, right on the new

Other related posts: