Autosys 12.1 SP1 WCC Issue after Ugrade from 12.1

[Alexander Liskow]

Hi Everyone,

we have some issues with the Autosys WebUI (WCC) after upgrading from Autosys 12.1 to 12.1.1 in our test environment.

We are running on RHEL 8 with an Oracle 19c database.

Our upgrade installation is done with the install.bin from the ISO Image and a response file for the silent installation.

After the Upgrade we get one of the following results in WCC:

1.  Scenario: Everything is ok and working as expected.
   
   
2. Scenario: The Tree View and FlowView as well as Quick View are not working anymore. The Tree View reports "Failed to load data" and Qucik View reports "Error: E131003 Error loading the job"
   In the ca-wcc.log we can see the folllowing error:

INFO   | jvm 1    | 2023/10/19 11:16:00 |      860 | @monitoring <192.168.172.1 ejmcommander ~DFA> [] ERROR ObjectTreeResource            (101) Error occurred while refreshing tree java.lang.RuntimeException: server -1 not found

INFO   | jvm 1    | 2023/10/19 11:16:00 |      860 | at com.ca.wcc.monitoring.service.impl.JobLevelSecurityServiceImpl.isJobLevelSecurityEnabledForServer(Unknown Source)

INFO   | jvm 1    | 2023/10/19 11:16:00 |      860 | at com.ca.wcc.monitoring.service.impl.JobLevelSecurityServiceImpl.isUserHasAccessToJobNode(Unknown Source)

...

INFO   | jvm 1    | 2023/10/19 11:16:00 |      860 | @tomcat-resource <https-jsse-nio-8443-exec-1> [[]]  WARN #WccReportErrorValve                #(130) returned status 500 for  /wcc/jsc-rest/tree/refresh from 192.168.172.1

Checking with the WCC DB we can see that there is an entry with a negative value in the tables MON_JOB and MON_JOB_VIEW for the column ID and JOB_ID.

The value is -2147483647 and every time the wcc services are being startet, this value is assigened to another job in the MON_JOB table. It seems that the wcc Collector is responsible for this behaviour during it's job task.

3. Scenario: The Quick Edit is not working anymore. We are receiving the following error in the Quick Edit log:

2023-10-18 14:04:08,140 @quickedit <192.168.172.1 ejmcommander ~C3C> []  WARN #AutoSysServiceWrapper              #(801) Exception in getJobDef() call to adapter: CAUAJM_E_10678 The requested server operation failed because specified attributes were invalid.  Operation ID = 299.
com.ca.uejm.adapter.AdapterException: CAUAJM_E_10678 The requested server operation failed because specified attributes were invalid.  Operation ID = 299.

 

For both error scenarios the issue seems to be in the database. We have created a DB Restore Point for a successful and working 12.1.1 Upgrade.

Restoring this Snapshot to a not working 12.1.1 Upgrade solved both errors.

In all 3 scenarios the install.bin ends with RC=0.

Is there a possibility to get information, what the wcc Services are executing when these errors occur? We have no idea which attributes may be invalid when trying to edit a job via WCC. The database contents is not changed except for the changes which the Upgrade itself is performing.

Autosys itself seems to be fine. autorep etc. are working fine.

Thank You for any hints to solve this issue. 

[Alexander Liskow]

Hi Everyone,

some kind of a little update on this issue.

It seems that it is possible to resolve the issue with the Monitoring/Tree & Flow View by executing the following commands:

1. Delete all defined Views in the WCC : $CA_WCC_INSTALL_LOCATION/bin/wcc_monitor.sh -u ejmcommander -p <password> -i /opt/rs/source/wcc_delviews.txt
2. Delete the defined Autosys Server in WCC: $CA_WCC_INSTALL_LOCATION/bin/wcc.config.sh -u ejmcommander -p <password> -i /opt/rs/source/wcc_delserver.txt -plainpwd
3. Stop all Autosys Services
4. Refresh the Autosys DB with the RefreshAEDB.pl: $AUTOSYS/dbobj/ORA/RefreshAEDB.pl "<ORA_SERVICENAME>" "aedbadmin" "<password>" "<autosys_inst_dir>/JRE_WA" "/tmp/aedb.log"
5. Start the Autosys Services.

This can solve the Tree View showing negative values for the job count and the Job Flow can be loaded again.

However instead we often end up  getting the issue in Quick Edit/View showing the "invalid attribute error for Operation ID 299" when trying to edit a command job:

Our job database contains about 17000 Jobs. 

Rerunning the RefreshAEDB.pl does not help resolving the error 299.

The perl script is being delivered with the Autosys 12.1.01 ISO File.

Does anyone know which sql query is being run against the Oracle Database when You click on Quick Edit of a command job or is there a way to raise the log level to see thi exact statement?

Note: You can run the same actions on a Autosys 12.1 env with no SP installed without running in any of the described issues.

Regards,

Alex

[Alexander Liskow]

Hi Everyone,

just a quick update.

We have been in contact with Tech Support regarding these issues.

Support has been able to reproduce these issues and is working on a fix for 12.1. SP1 .

Regards,

Alex.