EBS jobs go to Waiting for host | DBCall.runSqlQuery () failed
Article ID: 395238
Updated On:
Products
Issue/Introduction
After a cutover activity or maintenance in Oracle E-Business Suite, many jobs stay in an Active state within Automic. Some go to a Waiting for host status and have the following last message: U02004006 Could not establish a connection to 'OEBS_AGENT' ('DBCall.runSqlQuery () failed').
One of the active jobs shows completed in the report, but is not finished on the Automic side. Some other errors appear:
20241216/060438.109 - U00045014 Exception 'java.lang.IllegalArgumentException: "Target routine is missing"' at 'com.automic.agent.protocol.NatMessage$Builder.build():190'.
20241216/060438.109 - U00003620 Routine 'com.uc4.ex.logging.LogService' forces trace because of error.
20241216/060438.294 - Internal Error
20241216/060438.294 - U00045014 Exception 'java.lang.IllegalArgumentException: "Target routine is missing"' at 'com.automic.agent.protocol.NatMessage$Builder.build():190'.
20241216/060438.294 - U00003620 Routine 'com.uc4.ex.logging.LogService' forces trace because of error.
20241216/060438.491 - Internal Error
When checking on the concurrent manager database, there were many jobs pending from Automic.ny time there is cutover of the EBS system/database, the queues in Automic should be stopped first as should the agents. This will prevent a build up of jobs from growing when the cutover is finished. The agent should also be stopped before the activity and restarted after the activity is finished so that no jobs run into problems.
Environment
RA Oracle EBS
Cause
Root cause:
This issue occurred due to the cutover on the EBS system. The error message:
U02004006 Could not establish a connection to 'OEBS_AGENT' ('DBCall.runSqlQuery () failed').
happens when the EBS database that the agent tries to connect to is unavailable. A restart of the agent should resolve the issues.
Resolution
Immediate solution:
Update concurrent manager to allow more jobs to go through as it looked like there was catchup being done due to the cutover activity.
A restart of the agent additionally should help in this situation
Plan for the future:
Any time there is cutover of the EBS system/database, the queues in Automic should be stopped first as should the agents. This will prevent a build up of jobs from growing when the cutover is finished. The agent should also be stopped before the activity and restarted after the activity is finished so that no jobs run into problems.
Feedback
