Automation Engine Status not updated for finished OEBS Job
Article ID: 87946
Updated On:
Products
CA Automic Workload Automation - Automation Engine
AUTOMIC WORKLOAD AUTOMATION
Issue/Introduction
Error Message :
N/A
OEBS Jobs submitted from the RA Oracle EBS Agent finish in Oracle, but never get an ending status in the Automation Engine (AE).
The Job activates and the Concurrent request finishes successfully in Oracle, but the status in AE never gets updated to indicate that the job finished.
N/A
OEBS Jobs submitted from the RA Oracle EBS Agent finish in Oracle, but never get an ending status in the Automation Engine (AE).
The Job activates and the Concurrent request finishes successfully in Oracle, but the status in AE never gets updated to indicate that the job finished.
Cause
Cause type:
By design
Root Cause: You cannot have two Automation Engines accessing the same OEBS database or more than one OEBS agent per OEBS instance.
By design
Root Cause: You cannot have two Automation Engines accessing the same OEBS database or more than one OEBS agent per OEBS instance.
Environment
OS Version: N/A
Resolution
You cannot have two Automation Engines accessing the same OEBS database or more than one OEBS agent per OEBS instance.
If more than one OEBS agent is accessing the same OEBS database, one of the Agents must be stopped in order for the OEBS job to run successfullfy and correctly update the status in the Automation Engine.
Reference
RA Oracle EBS – Agent Guide 4.1 Documentation:
Fix Status: No Fix
Fix Version(s):
N/A
If more than one OEBS agent is accessing the same OEBS database, one of the Agents must be stopped in order for the OEBS job to run successfullfy and correctly update the status in the Automation Engine.
Reference
RA Oracle EBS – Agent Guide 4.1 Documentation:
Fix Status: No Fix
Fix Version(s):
N/A
Additional Information
Workaround :
N/A
N/A
Feedback
Powered by
