Configuring an IBM® WebSphere Portlet Factory user on OracleAdded by IBM on August 31, 2010 | Version 1 (Original)
|Prior to running a script on Oracle, you must configure a user.
Prior to running a script on Oracle, you must configure a user.
The Oracle database has a generic user that is created on each instance. This user is named "scott" and the password associated with this user is "tiger". WebSphere® Portlet Factory profiles in a DB can be accessed by any user that has at minimum the same security level as user "scott," as well as EXECUTE permission on the DBMS_LOCK object listed under the Object Privileges for the schema belonging to SYS.
To configure a WebSphere Portlet Factory user on Oracle:
- Using the Oracle DBA Studio, log into the Oracle instance to which the profile sets in a DB is being installed. (Log into the Oracle DBA Studio using the Oracle SYS account.)
- Expand the Security tree element and then expand the Users tree element.
- Select the specific user that will become the owner of the WebSphere Portlet Factory Profile Sets in a DB schema.
If the user does not exist, create a user with at a minimum, the same security level as the user "scott." To quickly duplicate the "scott" user, right click on the "scott" user, and select Create Like..., then enter the new username for the owner of the WebSphere Portlet Factory Profile Sets in a DB.
- To verify/add this permission, using the Oracle DBA studio, select the owner of the WebSphere Portlet Factory profile sets on the left side by single left mouse clicking the user.
- Select the Object Privileges tab, expand the Schema tree, expand the SYS user, then expand the Packages element.
- Select the DBMS_LOCK package.
- Under Available Privileges will be EXECUTE. Select the EXECUTE privilege, and click on the down arrow to Grant this privilege to the Factory Profile Sets in a DB user.
- Click the Apply button.
Note: If the apply action fails, this usually indicates that the user currently logged into the instance does not have access to delegate privileges belonging to the SYS schema. If this is the case, disconnect from the database instance and reconnect to the instance with a user that has access to the SYS objects.
Parent topic: Setting up database storage: wpf7