Ron Boggs wrote:
> I am interested in methods used to give priority to one database (or
> schema, or set of users, or application, etc) over another.
>
> We have a critical switch database running on one host which feeds
> data to a reporting database on another host. For smaller
> environments, we are looking at ways those two database could reside
> on the same host. The issue is giving the switch a higher priority
> over the sessions working on the reporting side.
>
> First of all, we tried resource manager and it was not applicable.
> These servers rarely exceed 100% of CPU capacity and resource manager
> does not become effective at allocating CPU util the load is 125% (or
> beyond).
>
> In plain English, what we need is a way to give sessions at the switch
> database priority over those at the reporting database. IOW...switch
> sessions should never (ok...rarely) wait for CPU time behind a
> reporting session. I can't see where the future RM feature of fixed
> CPU allocation will address this in the way we need it to either. If
> the server has 4 CPU's and the switch needs all 4 of them...that's
> what we want it to get.
>
> Has anybody had any success with a similar requirement? Any way to
> 'nice' the server processes down for the reporting database and have
> it remain effective until the database is shutdown?
>
> FYI...our database environments (typically) are Solaris 8.
>
> I appreciate any feedback.
>
You are not giving us much to go on here. What version/release of
Oracle. If you are not using 100% CPU what is your problem? You cannot
force Oracle to use 100 (or any) percent CPU it does not need. Are you
talking about two SIDs reporting and switch, or are they two
applications accessing the same db, or are they seperate scheams?
--
AjA
Received on Mon Feb 24 2003 - 16:50:30 CST
