RE: error after creating second database

From: Jacques Kilchoer <Jacques.Kilchoer_at_quest.com>
Date: Wed, 07 Mar 2001 11:23:44 -0800
Message-ID: <F001.002C625A.20010307103257@fatcity.com>

> -----Original Message-----
> From: Bambang Setiawan [mailto:Bambang.Setiawan_at_Sidola.com]
> Sent: mardi, 6. mars 2001 21:55
>
> but my primary question not only how to fix it but
> why this thing happened ?
>
> >>> "Joseph S. Testa" <teci_at_oracle-dba.com> 03/07/01 11:35 >>>
> HINT: > You may need to run PUPBLD.SQL as SYSTEM

Read the following manual
 SQL*Plus User's Guide and Reference
Release 8.1.5
A66736-01

(or the corresponding manual for your version of Oracle)

Appendix E, security, describes the use of the PRODUCT_USER_PROFILE table

<<Various Oracle products use PRODUCT_USER_PROFILE, a table in the SYSTEM account, to provide product-level security that supplements the user-level security provided by the SQL GRANT and REVOKE commands and user roles.

Overview
DBAs can use PRODUCT_USER_PROFILE to disable certain SQL and SQL*Plus commands in the SQL*Plus environment on a per-user basis. SQL*Plus--not Oracle--enforces this security. DBAs can even restrict access to the GRANT, REVOKE, and SET ROLE commands to control users' ability to change their database privileges.

SQL*Plus reads restrictions from PRODUCT_USER_PROFILE when a user logs in to SQL*Plus and maintains those restrictions for the duration of the session. Changes to PRODUCT_USER_PROFILE will only take effect the next time the affected users log in to SQL*Plus.>>

You can find online documentation at the Oracle Technology Network website http://otn.oracle.com/docs/index.htm

---

any ignorant comments made are the sole responsibility of J. R. Kilchoer and should not reflect adversely upon my employer.

 
Jacques R. Kilchoer
(949) 754-8816
Quest Software, Inc.
8001 Irvine Center Drive
Irvine, California 92618
U.S.A.
http://www.quest.com Received on Wed Mar 07 2001 - 13:23:44 CST