catalog.sql, catproc.sql and pupbld.sql

ton de w wrote:
> Hello,
>
> I have an application to install on 9i - it says I must run
> catalog.sql, catproc.sql and pupbld.sql before installing.
> hmmm.
> So how do I know if they have been run before? And if they have been
> run before will running them twice be OK?
>
> The instructions seem a bit old - is it possible I dont have to run
> these scripts on 9i?
> Or 10G? I have an install coming up on 10G!
>
> TIA
>
> Ton
>

The catalog.sql and catproc.sql scripts are run when the database is
created. You can safely re-run these scripts as SYS without causing any
problems.

The pupbld.sql script is not run on database creation. IIRC, this script
is run as SYSTEM. If you look at the script, you will see that it
creates a table called PRODUCT_USER_PROFILE. If this table exists, then
you should not need to run the script. If the table does not exist, then
run the script as SYSTEM.

HTH,
Brian

--
===================================================================

Brian Peasland
dba@nospam.peasland.net
http://www.peasland.net

Remove the "nospam." from the email address to email me.


"I can give it to you cheap, quick, and good.
Now pick two out of the three" - Unknown

--
Posted via a free Usenet account from http://www.teranews.com

ton de w schreef:
> Hello,
>
> I have an application to install on 9i - it says I must run
> catalog.sql, catproc.sql and pupbld.sql before installing.
> hmmm.
> So how do I know if they have been run before? And if they have been
> run before will running them twice be OK?
>
> The instructions seem a bit old - is it possible I dont have to run
> these scripts on 9i?
> Or 10G? I have an install coming up on 10G!
>
> TIA
>
> Ton
>
The application states the obvious - catproc and catalog run upon
creation time - no harm in rerunning, unless you run the
wrong version (from a different location, for example...).

pupbld.sql builds a rarely used table, called product_user_profile;
it can be used to allow users to use a certain interface. In that
case, it may be of interest to your app.
The first two are really over the top, and would not only make
my eyebrows raise an inch or so, I would seriously doubt the
Oracle knowledge of the vendor.

Doesn't it say "Switch on your computer" anywhere

--
Regards,
Frank van Bortel

Top-posting is one way to shut me up...

On 14 Mar, 20:05, Frank van Bortel wrote:
> ton de w schreef:
>
>
>
> > Hello,
>
> > I have an application to install on 9i - it says I must run
> > catalog.sql, catproc.sql and pupbld.sql before installing.
> > hmmm.
> > So how do I know if they have been run before? And if they have been
> > run before will running them twice be OK?
>
> > The instructions seem a bit old - is it possible I dont have to run
> > these scripts on 9i?
> > Or 10G? I have an install coming up on 10G!
>
> > TIA
>
> > Ton
>
> The application states the obvious - catproc and catalog run upon
> creation time - no harm in rerunning, unless you run the
> wrong version (from a different location, for example...).
>
> pupbld.sql builds a rarely used table, called product_user_profile;
> it can be used to allow users to use a certain interface. In that
> case, it may be of interest to your app.
> The first two are really over the top, and would not only make
> my eyebrows raise an inch or so, I would seriously doubt the
> Oracle knowledge of the vendor.
>
> Doesn't it say "Switch on your computer" anywhere
>
> --
> Regards,
> Frank van Bortel
I looked into this a bit more - and it looks like store and forward
capabilites (for a gateway) are being set up.
job_queue_processes and job_queue_interval need setting in the init
file.
Might running catproc and catalog (in addition to running at db
creation) make sense after the init file was modified?

On 21 Mar, 11:37, "ton de w" wrote:
[deletia]
> Might running catproc and catalog (in addition to running at db
> creation) make sense after the init file was modified?- Hide quoted text -
>

No, running catproc.sql and catalog.sql build you data dictionary.
Changing init.ora parameters changes how your instance is configured.
They are not related.

HTH

-g