AE Known Issues

This article documents known issues in CA Workload Automation AE Release 11.3.6 (including service packs).
wcc114sp5p
This article documents known issues in CA Workload Automation AE Release 11.3.6 (including service packs).
Contents
Agent Upgrade Fails (UNIX Only)
If you are installing an agent using the wa_setup.sh script on a computer where the r11.3 agent is already installed, a message similar to the following is displayed:
There is already an agent installed with the name you specified. To
use the existing agent for this install, select Use an Existing 
Agent. Otherwise, specify another agent name.
[ OK ] [ Abort installation ]
When you try to upgrade the agent from r11.3 to the current release using the wa_setup.sh script, the upgrade fails if the r11.3 agent was installed using the agent_setup.sh script. This happens because the Product Interchange Format (PIF) considers the agent_setup.sh and wa_setup.sh scripts as two different components.
To upgrade the agent from r11.3 to the current release successfully, you must use the same script that you used to install the r11.3 agent. For example, if you used the agent_setup.sh script to install the r11.3 agent, you must use the agent_setup.sh script to upgrade the agent from r11.3 to the current release.
Application Server Stops Responding (UNIX Only)
If you installed CA Workload Automation AE on a UNIX computer, the application server may stop responding if the /etc/hosts file contains the ::1 entry (IPv6 loop back entry) that includes the host name. To resolve this issue, remove the host name from the ::1 entry in the /etc/hosts file.
Behavior of Jobs with Load Balancing and Resource Attributes
CA Workload Automation AE Release 11.3.6 SP5 introduced an unintended change in the scheduling behavior for jobs having a job_load of 0 (zero) that specify both a priority and a virtual resource dependency. Due to the strict priority enforcement, jobs with resource requirements and no load can now delay or even block lower priority jobs having load units that are scheduled to the same machine, although these jobs do not utilize virtual resources.
CA Workload Automation AE Processes Fail to Start on Red Hat Linux Enterprise 6 (UNIX Only)
CA Workload Automation AE processes exit with Signal SEGV error if the CA Workload Automation AE user does not have read and execute permissions to the $ORACLE_HOME directory. The CA Workload Automation AE processes exit without displaying any error messages.
As a workaround, the CA Workload Automation AE user must be granted read and execute permissions to the $ORACLE_HOME directory.
Database Connection Tests Issue During Installation (UNIX Only)
During the CA Workload Automation AE installation, if the database connection tests take more than 90 seconds, the following message is displayed:
No further dialog defined  -  script returned no result.
To fix this issue, tune the network or the database such that the database connection test is performed within 90 seconds.
Database Creation Fails if the Database Server Resides on a Windows Computer (UNIX Only)
Symptom:
The CA Workload Automation AE installation fails to create the database if the database server resides on a Windows Computer, and the data file path contains special characters like \n, \t, and so on. For example, if you specify the data file path as C:\newdata, C:\tabdata, and so on.
Solution:
This problem occurs due to the UNIX/Linux shell interpretation of strings containing special characters.
<