| DRM - Dynamic Resource management [ID 390483.1] | |||||
|
|
|||||
| 修改时间 21-OCT-2010 类型 BULLETIN 状态 PUBLISHED | |||||
In this Document
Purpose
Scope and Application
DRM - Dynamic Resource management
DRM - Dynamic Resource Mastering
References
To describe the concept of DRM (Dynamic Resource Mastering)
This note in intended for experienced Real application cluster DBA's
When using Real application Clusters (RAC), Each instance has its own SGA and buffer cache. RAC will ensure that these block changes are co-ordinated to maximize performance and to ensure data intergrity. Each copy of the buffer also called as a cache resource has a master which is one of the nodes of the cluster.
In database releases before 10g (10.1.0.2) once a cache resource is mastered on an instance, a re-mastering or a change in the master would take place only during a reconfiguration that would happen automatically during both normal operations like instance startup or instance shutdown or abnormal events like Node eviction by Cluster Manager. So if Node B is the master of a cache resource, this resource will remain mastered on Node B until reconfiguration.
10g introduces a concept of resource remastering via DRM. With DRM a resource can be re-mastered on another node say from Node B to Node A if it is found that the cache resource is accessed more frequently from Node A. A reconfiguration is no longer the only reason for a resource to be re-mastered.
In 10gR1 DRM is driven by affinity of files and in 10gR2 it is based on objects.
Sample LMD trace file during a DRM operation
DRM attributes are intentionally undocumented since they may change depending on the version. These attributes should not be changed without discussing with Support.
It is important to note that
Disable DRM
Generally DRM should not be disabled unless Oracle Support/Development has suggested turning it off due to some known issues.
来自 “ ITPUB博客 ” ,链接:https://blog.itpub.net/23135684/viewspace-706814/ ,如需转载,请注明出处,否则将追究法律责任。