Database - RAC/Scalability (MOSC)

MOSC Banner

Oracle Scheduler Agent to execute remote jobs shows - Abnormal behavior with jobs

edited Jun 10, 2020 3:42AM in Database - RAC/Scalability (MOSC) 3 commentsAnswered

Basically, we have Oracle Scheduler Agent installed which is used for executing remote scripts; especially shell scripts. We have set MAX_RUNNING_JOBS=5 in the schagent.conf config file. SO this is to allow a max of 5 jobs to run simultaneously.

Now, we have a scenario wherein around 80 remote jobs (scheduler jobs executing shell scripts on the remote server) are triggered through the database. Each job is designed to be stopped by the DB if the execution exceeds 300 seconds. Also, each job is designed to intentionally run atleast 360 seconds. Since the remote script server only allows 5 jobs to run a a time, all the remaining 75 jobs are kind of queued. Now, since jobs are designed to run for 360 seconds while the 300 sec timeout is set, the first 5 jobs which are running are killed

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center