While helping a friend setup an OTM 5.5 instance, I ran into a problem where the create_glog_roles.sql and create_glog_users.sql scripts were failing because the SYSTEM user didn't have privileges to run some of the required commands.
The fix is simple, rather than running both scripts as SYS (which I avoid doing - much like running commands as root on Unix / Linux boxes), or granting more privilleges to the SYSTEM user, you can get buy with just running certain commands as SYS.
Here's the course of events:
--Chris
The fix is simple, rather than running both scripts as SYS (which I avoid doing - much like running commands as root on Unix / Linux boxes), or granting more privilleges to the SYSTEM user, you can get buy with just running certain commands as SYS.
Here's the course of events:
- Login to your OTM app server
- Change directories to <otm_home_dir>/glog/oracle/script8
- Sqlplus into your OTM database as the SYSTEM user
- Run
Code:
@create_glog_roles.sql
- Sqlplus into your OTM database as the SYS user
- Run:
Code:
grant SELECT ON DBA_SYNONYMS to app_owner; grant execute on dbms_rls to app_owner; grant select on sys.v_$context to app_owner; GRANT execute on dbms_rls to rep_owner; commit;
- Sqlplus into your OTM database as the SYSTEM user
- Run:
Code:
@create_glog_users.sql
- Sqlplus into your OTM database as the SYS user
- Run:
Code:
grant DBA to glogowner; grant DBA to glogdba; grant execute on dbms_aqin to glogdba; grant execute on dbms_rls to glogowner; GRANT EXECUTE ON DBMS_AQIN TO glogowner; GRANT execute on dbms_pipe TO glogowner; commit;
--Chris
Comment