AutoSys jobs are failing on CA WA System Agent servers with the following error: <Error reading Env profile>
Article ID: 4818
Updated On:
Products
Issue/Introduction
CA AutoSys job fails with the following error: <Error reading Env profile>. The job does not include a profile.
Example:
Job detail report
# autorep -J ora_rman_db_sync_cmd -d
Job Name Last Start Last End ST/Ex Run/Ntry Pri/Xit
_____________________ ____________________ ___________________ _____ ________ _______
ora_rman_db_sync_cmd 12/06/2016 10:23:29 12/06/2016 10:23:29 FA 19/1 1
Status/[Event] Time Ntry ES ProcessTime Machine
-------------- --------------------- -- -- --------------------- ----------------------------------------
STARTING 12/06/2016 10:23:29 1 PD 12/06/2016 10:23:29 aporadb
RUNNING 12/06/2016 10:23:29 1 PD 12/06/2016 10:23:30 aporadb
FAILURE 12/06/2016 10:23:29 1 PD 12/06/2016 10:23:30
<Error reading Env profile>
[STARTJOB] 12/06/2016 10:24:50 0 PD 12/06/2016 10:24:50
CA WCC -> Quick View -> Job Details section shows the same error against the Agent Status field under Run Time
There are no job or spool logs created on the CA WA System Agent host.
Environment
CA Workload Automation AutoSys Edition (AE) 11.x and 12.x on all supported platforms.
Resolution
On the CA WA System Agent host, check the following parameters' values in the agentparm.txt file under the System Agent installation path and ensure that the files, assigned to each of these parameters, do exist.
oscomponent.environment.variable
oscomponent.environment.variable_manager_manager_id
and
oscomponent.environment.variable_user_user_id
Example from a Linux CA WA System Agent installation:
If any of the files are missing, then either comment the corresponding parameter out in the agentparm.txt file and restart the WA System Agent service, or copy the missing environment file from another working CA WA System Agent host.
Additional Information
Attachments
Feedback
