Upgrading a shared services environment
In a shared services environment, where the connect as sysdba privilege is not present, you must provide a CREATE SYNONYM privilege to the APTARE_RO user before upgrading. APTARE_RO is a read-only user for the Portal.
Note:
Unless this privilege has been deliberately revoked, this step is mandatory for an upgrade. If this privilege is not granted, errors in the upgrade script will occur and functionality within the SQL Template Designer will be impacted.
Log in with root access.
Stop the portal and data receiver Tomcat services.
At the command line, execute the following commands:
sqlplus / as sysdba
SQL >GRANT CREATE SYNONYM TO APTARE_RO;
In a shared services environment, where the connect as sysdba privilege is not present, you must provide a CREATE JOB and DBMS_SCHEDULER privilege to the PORTAL user before upgrading.
Note:
Unless this privilege has been deliberately revoked, this step is mandatory for an upgrade. If this privilege is not granted, errors in the upgrade script will occur and functionality for Oracle jobs will be impacted.
Log in with root access.
Stop the portal and data receiver Tomcat services.
At the command line, execute the following commands:
sqlplus / as sysdba
SQL > GRANT CREATE JOB TO PORTAL;
SQL > GRANT EXECUTE ON DBMS_SCHEDULER TO PORTAL;
As a standard practice, during an IT Analyticsupgrade, Oracle-related code is leveraged and system-level objects (dba_, V$, etc.) and users (sys, system) are accessed. This scenario is not optimal in a shared service environment where organizations prefer to maintain their own Oracle credentials. Starting with release 10.4, portal upgrades can be run with limited privileges for the PORTAL user. Specific SQL statements can be executed to revoke the additional privileges assigned prior to the 10.4 release.
Note:
When privileges are revoked, the IT Analytics upgrade process is prevented from calculating the space in the datafiles and canceling Oracle jobs which may interfere with upgrade. By revoking these privileges, the local administrator assumes this responsibility.
Complete these steps to revoke privileges from a PORTAL user.
Log in with admin access.
Stop the portal and data receiver Tomcat services.
At the command line, execute the following commands:
sqplplus / as sysdba SQL >REVOKE SELECT ANY DICTIONARY FROM PORTAL; SQL>REVOKE SELECT_CATALOG_ROLE FROM PORTAL; SQL>REVOKE SELECT ON dba_free_space FROM PORTAL; SQL>REVOKE SELECT ON dba_data_files FROM PORTAL; SQL>REVOKE SELECT ON dba_temp_files FROM PORTAL;