How to cancel agent executions

Paula Jaime

Hi! I need to run an agent, but I get the error

[nQSError: 67020] The maximum number of concurrent instances of a scheduled job has been exceeded. The maximum limit is 1.

I see the same agent that I need to run in the Manage Agent Session view, so I want to cancel it. How can I do this?

Sumanth V -Oracle

@PVJ - This error occurs when an agent is run and a prior job for the same agent has not yet completed.

- Wait for the first Agent job to complete.
- Once it is completed, another job can then be initiated for the Agent.

Paula Jaime

Hello @Ashish-Oracle

I have seen this doc, but I would like to cancel the agents, because they have been running for more than 5 hours, and they do not finish, and I need to get the results of the their execution.

Sumanth V -Oracle

Hi @PVJ - You can use job manager client tool to cancel the jobs. Please refer the below document for details:

https://docs.oracle.com/middleware/1221/biee/BIESJ/schedjobmgr.htm#i1023231

You can restart the OBISCH component and that should also kill all the running or queued jobs at the time. Job manager is the recommended approach.

Ashish-Oracle

@PVJ Apart from what @Sumanth V -Oracle has suggested, below KM notes also talks about "Steps to Kill an Active Query". Please check if it helps:-

What Are the Steps to Kill an Active Query When an Agent Keeps Running
And It Prevents Scheduled Agent To Run (Doc ID 2783635.1)

Paula Jaime

Thank you for your answers!

I'm using OAC.

Is the Scheduler Job Manager available in OAC? Is it a different tool from the Admin Tool?

and in the admin tool, I open the repository in cloud mode, so Manage > Sessions is not able to select (the option is disabled)

Paula

SivaB -Oracle

@PVJ

Users can cancel any delivery that they own.

Admin user can suspend temporarily the agents which are created by other users

Console> >Monitor Deliveries >Action menu

Paula Jaime

Thank you @SivaB -Oracle, but that doesn't work either.

We have restarted the OAC service, but the agents are still visible in the Manage Agent Session view:

and I get the same error when I try to run the agent:

Harriet Huang-Oracle

@PVJ,

Probably raise a SR to support team to assist on this.

User_TQH9C

@Paula Jaime Do you still have this issue with the OAS agent. I had this issue in OAS and restarting OAS services resolved the issue for me.