Resource Manager
At this moment, it is not possible to use Resource Manager for remote external jobs. But this is going to change for sure. We can put the jobs in a job class that has a resource consumer group mapped on it. But for remote external jobs, these definitions are ignored. For regular jobs, we can find the job class that was used when the job ran in the *_scheduler_job_log views. For remote external jobs, that column contains a NULL value indicating that Resource Manager settings were not applied on them. An enhancement request has been filed for this. The Resource Manager integration for the remote Scheduler Agent needs at least the active session pool. This enables the database to limit the number of parallel jobs submitted to the agent. There is a very limited configuration in the schagent.conf file (MAX_RUNNING_JOBS). This file is not flexible enough and is invisible to the database administrator.
