AFAIK, you would run:
-
catalog.sql, catproc.sql and catexp.sql (for export/import views), and possibly pupbld.sql (while logged in as system). catrep.sql is only executed if you are setting up a replicated environment.
Run them as SYS or INTERNAL (they are a kind of synonymous account, but INTERNAL will not be supported in future releases any more), either in SQL*Plus or in svmgrl (as a matter of fact, you can run catdbsyn.sql also as SYSTEM or any DBA user, but it is simplier if you run all of them as SYS or INTERNAL).
Do *not* run those scripts as SYSTEM. This is true also for catalog.sql, catproc.sql and catexp.sql, do not follow Halo's advice to run them as SYSTEM - they should be run as SYS or INTERNAL.
BTW, if you are in doubt you can allways open each of those scripts in text editor and in the header you'll usualy find the instrunctions on how and under each account the script should be run.
HTH,
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Yes it is obsolete for quite some time, at least form Oracle7 era... and yet they still include it in any new distribution...
catdbsyn.sql can be used if you want to have *private* synonyms for all DBA_% views, which is kind of silly since there are public synonyms for all those views. So you don't need to run this script at all. It wouldn't do you any harm (except for a bounch of useless objects in the catalog), but it wouldn't do you any good either.
Jurij Modic ASCII a stupid question, get a stupid ANSI
24 hours in a day .... 24 beer in a case .... coincidence?
Most of the scripts will run as part od catproc.sql. have a look at the end of catproc.sql, you will see all the default options that will be included when you run catproc.sql. You don't need to run 'em explicitely unless otherwise its not included in catproc.sql.
Reply With Quote
Bookmarks