|
| Problem | DBA Role for EJSADMIN | | | | Solution |
Assuming EJSADMIN is the userid that will own the WebSphere Repository, the DBA role is not required for the EJSADMIN user. The EJSADMIN userid only needs the normal privileges CONNECT and RESOURCE so it can connect and create objects in Oracle database.
Example SQL statement to create the userid EJSADMIN using SQL*Plus:
$ sqlplus system/manager
SQL> CREATE USER ejsadmin IDENTIFIED by ejsadmin ;
SQL> GRANT CONNECT, RESOURCE TO ejsadmin ;
If the EJSADMIN doesn't have the DBA role, starting the HitCount CMP EJB (comes with Default Server) may fail with the error ORA-01031: Insufficient privileges. The reason the HitCount bean fails to start is because the userid/password specified for the datasource is defaulted to EJSADMIN/EJSADMIN and the HitCount bean is hardcoded to use the userid/password EJB/EJB. Since EJSADMIN has no DBA role, it can't create the table IncBeanTbl in the EJB's schema .
In summary, the EJSADMIN for Oracle does not require the DBA role. | |
| |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Administrative Console (all non-scripting) Operating system(s): Multi-Platform Software version: 3.0.2.x, 3.5 Software edition: Standard & Advanced Editions Reference #: 1113289 IBM Group: Software Group Modified date: 2003-06-23
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|