Friday, July 18, 2014

Capacity-On-Demand on Oracle Exadata Database Machine



Вышел квартальный Июльский патч на Экзадату (версия образа 12.1.1.1.1), в котором включена возможность
«Capacity-On-Demand on Oracle Exadata Database Machine»
Т.е. появилась возможность включить не все ядра в Экзадате, и таким образом сэкономить на лицензиях на СУБД. Условия, на которых оно возможно:
  • Capacity-on-demand is available for Oracle Exadata Database Machine X4-2 and Oracle Exadata Database Machine X4-8 Full Rack systems.
  • Oracle Exadata Database Machine X4-2 Eighth Rack is excluded from capacity-on-demand.
  • Reducing the number of active cores lowers the initial software licensing cost. It does not change the hardware cost.
  • The minimum number of processor cores that must be enabled is half of the physical cores on each processor. For Oracle Exadata Database Machine X4-2 systems, the minimum is 6 per processor (12 per database server). For Oracle Exadata Database Machine X4-8 Full Rack, the minimum is 8 per processor (64 per database server).
  • Additional cores are increased in 2-core increments per server on Oracle Exadata Database Machine X4-2, and in 8-core increments on Oracle Exadata Database Machine X4-8 Full Rack. Database servers in the same system can enable a different number of cores.
  • Capacity-on-demand may only be used to decrease the number of active processor cores during initial installation. After initial configuration, the processor core count can only increase on a system, up to the maximum. It is the customer's responsibility to acquire the additional software licenses.
  • Oracle Exadata Database Machine must use Oracle Configuration Manager or Oracle Platinum Services to qualify for capacity-on-demand.
  • Oracle Exadata Database Machine purchased under Infrastructure as a Service (IaaS) is not eligible for capacity-on-demand.

No comments:

Post a Comment

Note: Only a member of this blog may post a comment.

Does DEALLOCATE UNUSED or SHRINK SPACE will free space occupied by LOB segment?

Lets check how it works. My env is DB 19.20@Linux-x64 1) I created the table with 4 LOB columns of 4 different LOB types: BASICFILE BLOB, BA...