| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Usenet -> c.d.o.server -> Re: New instance keeps asking for PUPBLD.SQL even after it's run...why?
That seems odd. I'd be interested in the ultimate solution
to this one. A couple things come to my mind. Did you run
the correct PUPBLD version for the release of Oracle that
you are running? You probably did, but it's worth checking.
What is the SQL*Plus release? Does it match the database?
You might also look at the permissions. The SYSTEM user should own a view (or a table) named PRODUCT_USER_PROFILE. Everyone needs select access to that. If SQL*Plus doesn't see it when you log on, you get that error. You might also check to see if the synonym by the same name exists.
Jonathan
On Fri, 05 Nov 1999 17:17:56 GMT, "John Haskins" <76054.334SPAMBEGONE_at_compuserve.com> wrote:
>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?
Received on Fri Nov 05 1999 - 16:22:14 CST
 |
 |