ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

OEBS job fails with return code '2'.


Article ID: 223058


Updated On:


CA Automic One Automation


An OEBS job regularly fails with return code '2' caused by the following exception in the job report:

Release Captured Job 32818029 40168995 XLAACCPB(ErrorCode 60) (SQLState 61000) uc4_oae_pk.start_captured_job	0 appJobId : 40168995 : i : java.sql.SQLException: ORA-00060: deadlock detected while waiting for resourceORA-06512: at "XXAUTOMIC.UC4_OAE_PK", line 1025ORA-06512




Release : 4.x

Component : RA ORACLE EBS


This is caused by a wrong job type used in the capture job.

20210831/152935.131 -           Captured 40168995 XLAACCPB PXD GLB AP SCHEDULED JOBS NATH822 Tue Aug 31 15:29:35 CDT 2021
20210831/152935.162 - U00011673 Job 'XLAACCPB' could not be found or has a wrong type.
20210831/152935.162 - U02003012 An unknown message from partner 'AE_TST#CP002' could not be processed.
20210831/152935.162 - U0009909 TRACE: (Received 317 bytes from AE_TST#CP002)

Once the content of the capture job was corrected the job finished with return code '0'.