Upgrade 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.
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.
The absolute install path of Portal is represented as <install_path>. Substitute <install_path> with the absolute path of the Portal installation as applicable. If the Portal is installed on the default path, substitute by /opt which is the default path.
Note:
If the portal is configured with non default APTARE and Tomcat users, update the users in /<install_path>/aptare/upgrade/ant/sc_upgrader.xml before executing /<install_path>/aptare/upgrade/upgrade.sh
Log in with root access.
Stop the portal and data receiver Tomcat services.
At the command line, execute the following commands:
su - aptare
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:
su - aptare
sqlplus / as sysdba
SQL > GRANT CREATE JOB TO PORTAL;
SQL > GRANT EXECUTE ON DBMS_SCHEDULER TO PORTAL;