TNS_ADMIN still points to 32bit TNS_ADMIN after upgrade from Autosys 11 to 12

Products

• Autosys Workload Automation

Issue/Introduction

After upgrading from Autosys 11.3.x to 12.x,  though customer provided 64bit Oracle client location and a successful upgrade,  post upgrade many files still point to Oracle 32 bit TNS_ADMIN path

Below is list of just a few files in autouser directories. There are other files which also still point to 32 bit Oracle client.

# grep -R oracle32 autouser.*
autouser.ACE/autosys.csh.HOST1234:setenv TNS_ADMIN /local/apps/oracle32/product/12.1.0/client_1/network/admin
autouser.ACE/autosys.ksh.HOST1234:TNS_ADMIN=/local/apps/oracle32/product/12.1.0/client_1/network/admin ; export TNS_ADMIN
autouser.ACE/autosys.env.HOST1234:setenv TNS_ADMIN /local/apps/oracle32/product/12.1.0/client_1/network/admin
autouser.ACE/webserver/conf/wrapper.conf:set.TNS_ADMIN = /local/apps/oracle32/product/12.1.0/client_1/network/admin
autouser.ACE/autosys.sh.HOST1234:TNS_ADMIN=/local/apps/oracle32/product/12.1.0/client_1/network/admin ; export TNS_ADMIN
autouser.ACE/autosys.bash.HOST1234:TNS_ADMIN=/local/apps/oracle32/product/12.1.0/client_1/network/admin ; export TNS_ADMIN

 

Why is the TNS_ADMIN for 64bit Oracle not showing up in the files above? 

 

Environment

Release : 12.0

Component : CA Workload Automation AE

Resolution

This is expected behavior. 

Fresh install of 12.x asks for ORACLE_HOME (64bit) as well as TNS_ADMIN.

Upgrade on the other side, it does require 64bit ORACLE_HOME and does ask for it during upgrade.  However, it does not prompt for TNS_ADMIN, as it assumes that the existing TNS_ADMIN is OK.  One of the reasons is because, a custom TNS_ADMIN location was being used by many customers and not the one from ORACLE_HOME/network/admin.   

 

If TNS_ADMIN needs to be changed to 64bit ORACLE_HOME/network/admin or another custom location,  post upgrade the above scripts need to be manually adjusted accordingly to reflect the correct TNS_ADMIN location.