Interaction with Operating-System Resource Control - Oracle 10g

The Oracle Database server expects a static configuration and allocates internal resources, such as latches, from available resources detected at database startup. The database might not perform optimally and can become unstable if resource configuration changes very frequently.

Guidelines for Using Operating -System Resource Control

If you do choose to use Operating -system resource control with Oracle Database, then it should be used judiciously, according to the following guidelines:

  1. Operating-system resource control should not be used concurrently with the Database Resource Manager, because neither of them are aware of each other's existence. As a result, both the operating system and Database Resource Manager try to control resource allocation in a manner that causes unpredictable behavior and instability of Oracle Database.
    • If you want to control resource distribution within an instance, use the Database Resource Manager and turn off operating -system resource control.
    • If you have multiple instances on a node and you want to distribute resources among them, use operating -system resource control, not the Database Resource Manager.
  2. In an Oracle Database environment, the use of an operating -system resource manager, such as Hewlett Packard's Process Resource Manager (PRM) or Sun's Solaris Resource Manager (SRM), is supported only if all of the following conditions are met:
    • Each instance must be assigned to a dedicated operating-system resource manager group or managed entity.
    • The dedicated entity running all the instance's processes must run at one priority (or resource consumption) level.
    • Process priority management must not be enabled.
  3. If you chose to use operating-system resource control, make sure you turn off the Database Resource Manager. By default, the Database Resource Manager is turned off. If it is not, you can turn it off by issuing the following statement:

    Also remember to reset this parameter in your initialization parameter file, so that the Database Resource Manager is not activated the next time the database is started up.

Dynamic Reconfiguration

Tools such as Sun's processor sets and dynamic system domains work well with an Oracle Database. There is no need to restart an instance if the number of CPUs changes.
The database dynamically detects any change in the number of available CPUs and reallocates internal resources. On most platforms, the database automatically adjusts the value of the CPU _COUNT initialization parameter to the number of available CPUs.

All rights reserved © 2020 Wisdom IT Services India Pvt. Ltd Protection Status

Oracle 10g Topics