I was loggd in as SYSTEM. The solution came from opening the PUPBLD.SQL
file and running each command manually. There were a variety of small
problems--based on issues with how I'd allocated space--that kept some
commands from completing successfully. I fixed the issues with space
allocation, and all the commands ran fine.
Pete Sharman <psharman_at_us.oracle.com> wrote in message
news:3823587A.C6F375F6_at_us.oracle.com...
> Never seen this unless the script was run as someone else. Were you by
chance
> logged on as sysdba when you ran it, because that puts you under SYS's
security
> domain. Check the table owner column in DBA_TABLES to make sure.
>
> HTH.
>
> Pete
>
> John Haskins wrote:
>
> > Hi, folks:
> >
> > I've added two new instances to an existing Oracle 7.3.4.0.1 server
(Solaris
> > 2.6). Even though I have already run PUPBLD.SQL as SYSTEM in each new
> > instance, each time I log on I get this message:
> > Error accessing PRODUCT_USER_PROFILE
> > Warning: Product user profile information not loaded!
> > You may need to run PUPBLD.SQL as SYSTEM
> >
> > Anyone know why this is happening, and what I can do about it?
> >
> > Thanks.
>
Received on Mon Nov 08 1999 - 15:58:52 CST
