What are the limitations when an Oracle instance is managed by Suns processor sets, dynamic system domains or dynamic reconfiguration (DR)?
Processor sets & dynamic system domains with the Oracle database work well. Instance re-boot may be required solely when the number of CPU’s is changed. Oracle discovers the number of CPU’s when booting, and uses this for a number of algorithms for allocating resources (latches, lots of others). So if the number of CPU’s changes (i. e., not a maintenance swap resulting in no change in the number of CPU’s), rebooting may be required if performance suffers. Dynamic Reconfiguration (DR) CPU DR: Oracle can tolerate DR CPU changes. As with processor sets, a reboot may be required if the number of CPU’s changes and performance suffers suffers as a result. Memory DR: The Solaris DR-detach process that migrates memory is not supported.
Related Questions
- What are the limitations when an Oracle instance is managed by a resource manager such as HPs Process Resource Manager or Suns Solaris Resource Manager?
- What are the limitations when an Oracle instance is managed by Suns processor sets, dynamic system domains or dynamic reconfiguration (DR)?
- Where did Oracle put all Suns processor manuals?