An Oracle9iAS Portal user account does not have any direct privileges on the database. However, because Oracle9iAS Portal pages are displayed by executing procedures in the database, a user account needs to have execute privileges on those procedures. To do this, each user account must be associated with a database schema that has the privilege to display Oracle9iAS Portal pages.
By default, each new user account is associated with the <PORTALOWNER>_PUBLIC database schema (where PORTALOWNER is the database schema in which Oracle9iAS Portal is installed), which has all the necessary privileges for displaying Oracle9iAS Portal pages. However, if a user has his or her own database schema or you want to associate the account with a schema that has privileges in addition to the ones needed to display pages, you may want to change the account's database schema.
If
you do change the account's database schema, the schema you
associate with the account must be set up for
use with Oracle9iAS Portal
user accounts.
You must be the database administrator, or have Manage privileges on All Schemas to change a user account's database schema.
Locate the Portal User Profile portlet. By default, it is located on the Administer tab of the Builder page.
Enter the user name of the account whose database schema you want to
change in the Name field.
Or, click
and select from the list provided.
Click Edit.
In the Database Schema
field, enter the name of the database schema to use to execute the
procedures that display Oracle9iAS
Portal pages. Or click
and select from the list provided.
Click OK.
Changing a user account's database schema decreases the hit-rate for the connection pool that is maintained in mod_plsql, since the schema-identity for a given request changes more frequently. Depending on the number of unique schema-identities, and their access rates, the performance of the system may decrease.