Re: OLTP should have priority over jobs

  • From: Hans Forbrich <fuzzy.graybeard@xxxxxxxxx>
  • To: oracle-l@xxxxxxxxxxxxx
  • Date: Mon, 29 Feb 2016 19:33:57 -0700

Basically:

- Define one or more consumer groups
- Assign a session to a consumer group
- can be done by a variety of things (logged in user, IP address, client s/w ...)
- Create a plan that fills your needs
- Activate the plan.

Oracle provides free resources on the net to help you. Search for "oracle obe resource manager". Two useful resources are https://www.oracle.com/technetwork/database/performance/resource-manager-twp-133705.pdf and (not quite on the mark, but useful) https://www.youtube.com/watch?v=NlgxhV5cTRc

HTH
/Hans

On 29/02/2016 1:07 PM, Woody McKay wrote:

Hi,

Is there a best practice for having oltp application connections to have priority over running jobs?

Mgmt wants to ensure that the user application isn't slowed down by jobs running in the background.

I have thought about using different resource plans (rather than default_maintenance_plan for all, but I'm not sure how to implement that. If the solution is using different plans, how do you know what jobs and scheduled jobs run as who? By the job owner?

Win 2012R2, 32cpu, 512g ram, 26 SIDs, oracle 12.1.0.2.7
--
Sincerely - Woody

--
//www.freelists.org/webpage/oracle-l


Other related posts: