Cross instance dependencies fails after the installation of a database update (RefreshAEDB)

Document ID : KB000031664
Last Modified Date : 14/02/2018
Show Technical Document Details


While applying a maintenance level to refresh the database, we observed that cross instance dependency jobs start to fail. On checking further we found that this was due to the anyone id losing its permission on the alamode table. 


Since AutoSys 4.5, we have strived to deprecate the use of the "anyone" database user. Some of our other customers consider the inclusion of the "anyone" database user as a security risk. Changes to legacy agents have been made to support user defined database users to access the alamode view. 

In this release of the product, the agent has no need for the "anyone" user since it no longer requires a database client. All references to the "anyone" user has thus been removed. The alamode view has been retained for compatibility with legacy agent. However, we have transferred responsibility for maintaining the "anyone" account to those customers that still require them. 

This means that you will have to add the maintenance of the "anyone account" status to your process of refreshing the database.

Please refer to the 4.5.1_Support_In_11.3.5.sql SQL file in <install path>/WorkloadAutomationAE/autosys/dbobj/ExtDep/<ORA|SYB>."