search cancel

Upgrading Oracle 12.1.0.2 to Oracle 19 for AutoSys 11.3.6

book

Article ID: 189815

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - System Agent (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Workload Automation AE

Issue/Introduction

Is upgrading Oracle 12.1.0.2 to Oracle 19 for AutoSys 11.3.6 supported?

Environment

Release : 11.3.6

Component : CA Workload Automation AE (AutoSys)

Resolution

Oracle 19c is listed on the AutoSys matrix as being supported.
Please keep in mind that refers to the database itself.
The Oracle client which is local to the AutoSys 11.x server machines must still be a 32bit Oracle until AutoSys r12.

AutoSys r12 is 64bit. 
That removes the 32bit database client requirement on the AutoSys server.


Here is a link to the current product matrix:
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-ae-and-workload-control-center/11-3-6-SP8/release-notes/ae-release-notes/ae-operating-system-and-database-support.html


If you actually stopped AutoSys and left the local Oracle client alone, and just upgraded
the Oracle DB(s) on remote host(s) such that they keep their name/locations then after the Oracle upgrade you should be able to just restart AutoSys without issue.

But if the local Oracle client is being upgraded, again be mindful of the bit requirements depending on your AutoSys version.

Also you would need to potentially make adjustments to environment variables such as ORACLE_HOME, TNS_ADMIN, PATH, LIBPATH so the needed Oracle files can be found, if their values/paths change.

Additionally if other things with the Oracle DB are changing like its name, or port or host location you will need to adjust the tnsnames.ora file on the AutoSys host and the $AUTOUSER/config.$AUTOSERV file's EventServer*= entry.
The AutoSys environment variables you would need to adjust would be in $AUTOUSER/autosys.<shell>.<hostname>. files.
The product specifically sources autosys.sh.<hostname> during startup so be sure it contain correct values.

The other profiles are more for users to consume/source based on their shell(s).

Additional Information


Make sure compliance app is able to connect to the database too (https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-ae-and-workload-control-center/11-3-6-SP8/installing/ae-installation/environment-and-database-connection/configure-the-java-database-connectivity-driver-to-use-oracle-call-interface.html)

 

For WCC: wcc_config  can be run to point to new database information.
https://techdocs.broadcom.com/us/en/ca-enterprise-software/intelligent-automation/workload-automation-ae-and-workload-control-center/11-3-6-SP8/administrating/ca-wcc-administration/administer-the-configuration-batch-interface.html#concept.dita_834f26aa195a4f1412af52b2a8559253986a5b4b_SpecifyaDifferentDatabase