OLTP should have priority over jobs

From: Woody McKay <woody.mckay_at_gmail.com>
Date: Mon, 29 Feb 2016 15:07:22 -0500
Message-ID: <CAAxONsTgdYecqOtP13WMNemJqDBoWnXqkxLZnumn+PAwcWqqbw_at_mail.gmail.com>

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

--

http://www.freelists.org/webpage/oracle-l Received on Mon Feb 29 2016 - 21:07:22 CET

This message: [ Message body ]
Next message: Ryan January: "Re: OLTP should have priority over jobs"
Previous message: Sayan Malakshinov: "Re: RANK+WINDOW NOSORT STOPKEY=> stopkey doesn't work"
Next in thread: Ryan January: "Re: OLTP should have priority over jobs"
Reply: Ryan January: "Re: OLTP should have priority over jobs"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

Original text of this message