Oracle Analytics Cloud and Server

Home› Oracle Analytics› Oracle Analytics Forums› Oracle Analytics Cloud and Server› Oracle Analytics Cloud and Server

Categories

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

nQSError: 67020: One user is getting error while scheduling any report

Received Response
846
Views
6
Comments
Ramprapanna Bhattacharya-Oracle
Ramprapanna Bhattacharya-Oracle Rank 2 - Community Beginner
in Oracle Analytics Cloud and Server

Hi,

We are using OACS. One particular user is facing the following error while running agents:

[nQSError: 67020] Exceeded max concurrent instances of scheduled job. Max limit is 1.

No other user is getting this error while running the same or different agents.

We have checked when the user is getting the error (Admin -> Manage Agent Sessions), no other agent is running.

Any clue to the root cause / resolution of this error will be extremely helpful.

Regards

Ram

Tagged:

Answers

  • Anirban Basu-133546
    Anirban Basu-133546 Rank 5 - Community Champion

    Hi Ram ,


    Can you check this link -

    Error "Exceeded Max Concurrent Instances Of Scheduled Job. Max Limit Is 1" When Running Agents (Doc ID 2777480.1)

    Thanks

    Anirban

  • SiddharthDang-Oracle
    SiddharthDang-Oracle Rank 5 - Community Champion

    Hi Ram,

    OAC is a multi-noded environment and sometimes the agent session does not show all scheduled or running sessions from all nodes. Try checking after sometime.

    Regards,

    Siddharth Dang

  • Ramprapanna Bhattacharya-Oracle
    Ramprapanna Bhattacharya-Oracle Rank 2 - Community Beginner

    Hi @Anirban Basu-133546 /@SiddharthDang-Oracle

    We tried these options already and did not work.

    Surprisingly only one user is facing this issue while running agents, no other use is facing this.

    Hence, it looks like no other agent runs in the background when the particular user gets the error.

  • SiddharthDang-Oracle
    SiddharthDang-Oracle Rank 5 - Community Champion

    Hi Ram,

    Try this please at your end. Check if the agent that is being scheduled is already scheduled or not by any other user. If yes, then check run as user value. If it is a particular user set, then change it to whosoever is running the agent.

    I remember we also faced a similar issue. We tried a bunch of different things and it got resolved. Don't know exactly which solved it, but I strongly feel it is related to Run as user only.

    Regards,

    Siddharth Dang

  • Ramprapanna Bhattacharya-Oracle
    Ramprapanna Bhattacharya-Oracle Rank 2 - Community Beginner

    Hi @SiddharthDang-Oracle

    The problematic agent which is currently being tested by the user, is present in his "My Folder".

    Hence no other user can schedule the same other than him.

    Regards,

    Ram

  • SiddharthDang-Oracle
    SiddharthDang-Oracle Rank 5 - Community Champion

    Hi @Ramprapanna Bhattacharya-Oracle ,

    Did you check the run as user option? What is configured in his agent?

    Regards,

    Siddharth Dang