OEBS job is not finishing in Automic.

book

Article ID: 199506

calendar_today

Updated On:

Products

CA Automic Workload Automation - Automation Engine

Issue/Introduction

OEBS job is kicked off in OEBS, but does not finish in Automic.

The job report ends with this status:

2020-09-15 14:50:59             runId 30622222 wasRestarted null
2020-09-15 14:51:00             -----  prompts  -----
2020-09-15 14:51:00             userName : SYSADMIN
2020-09-15 14:51:00             application : SYSADMIN
2020-09-15 14:51:00             responsibility : System Administrator
2020-09-15 14:51:00             appShortName : FND
2020-09-15 14:51:00             language : 
2020-09-15 14:51:00             program : FNDSCURS
2020-09-15 14:51:00             printer : 
2020-09-15 14:51:00             printerStyle : 
2020-09-15 14:51:00             copies : 
2020-09-15 14:51:00             saveOutput : N
2020-09-15 14:51:00             printTogether : N
2020-09-15 14:51:00             xmlAppShortName : 
2020-09-15 14:51:00             xmlTemplate : 
2020-09-15 14:51:00             xmlLanguage : 
2020-09-15 14:51:00             xmlOutputFormat : 
2020-09-15 14:51:00             operatingUnit : 
2020-09-15 14:51:00             checkTriple : N
2020-09-15 14:51:00             warningEndOk : false
2020-09-15 14:51:00             RA_CAPTURED_APPLICATION_JOBID : not defined
2020-09-15 14:51:00             -----  prompts  -----

It never reaches the completion that looks like:

 

2020-09-15 14:50:59             runId 30622222 wasRestarted null
2020-09-15 14:51:00             -----  prompts  -----
2020-09-15 14:51:00             userName : SYSADMIN
2020-09-15 14:51:00             application : SYSADMIN
2020-09-15 14:51:00             responsibility : System Administrator
2020-09-15 14:51:00             appShortName : FND
2020-09-15 14:51:00             language : 
2020-09-15 14:51:00             program : FNDSCURS
2020-09-15 14:51:00             printer : 
2020-09-15 14:51:00             printerStyle : 
2020-09-15 14:51:00             copies : 
2020-09-15 14:51:00             saveOutput : N
2020-09-15 14:51:00             printTogether : N
2020-09-15 14:51:00             xmlAppShortName : 
2020-09-15 14:51:00             xmlTemplate : 
2020-09-15 14:51:00             xmlLanguage : 
2020-09-15 14:51:00             xmlOutputFormat : 
2020-09-15 14:51:00             operatingUnit : 
2020-09-15 14:51:00             checkTriple : N
2020-09-15 14:51:00             warningEndOk : false
2020-09-15 14:51:00             RA_CAPTURED_APPLICATION_JOBID : not defined
2020-09-15 14:51:00             -----  prompts  -----
2020-09-15 14:51:13             7583875 Completed
2020-09-15 14:51:13             MultiNode, output files on: VWASOEBS01 agent007
2020-09-15 14:51:13             register output: /u01/install/VISION/fs_ne/inst/EBSDB_vwasoebs01/logs/appl/conc/log/l7583875.req
2020-09-15 14:51:13             register output: /u01/install/VISION/fs_ne/inst/EBSDB_vwasoebs01/logs/appl/conc/out/o7583875.out
2020-09-15 14:51:13             registerOutputFile: /u01/install/VISION/fs_ne/inst/EBSDB_vwasoebs01/logs/appl/conc/out/o7583875.out 

Cause

Configuration: Some of the stored procedures, indexes, packages, views or triggers created by the agent might be corrupt.

Environment

Release : 4.x

Component : RA ORACLE EBS

Resolution

Delete the existing configuration with the two sql files provided in the sql folder. OAE_AW_DROP.sql and OEBS_DROP.sql.

Once done restart the OEBS agent and check the checkbox on the OEBS agent object in client 0. 'Update Database after Agent Restart'.

This will recreate all the definitions on the OEBS database.

Attachments