Skip Headers
Oracle® Database Appliance Getting Started Guide
Release 2.9 for Linux x86-64

E22692-35
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

B Core Count and Capacity-on-Demand

This appendix describes Oracle Database Appliance core count topics and the capacity-on-demand feature. This appendix contains the following topics:

Understanding CPUs and Core Count

Each Oracle Database Appliance includes two nodes.

Oracle Database Appliance X4-2 nodes each contain 2 CPUs and each CPU has 12 cores that are hyper-threaded. When you configure Oracle Appliance Manager on Oracle Database Appliance X4-2, all 48 cores (24 cores in each server) are active with hyper-threading enabled by default.

Oracle Database Appliance X3-2 nodes each contain two CPUs and each CPU has eight cores that are hyper-threaded. When you configure Oracle Appliance Manager on Oracle Database Appliance X3-2, all 32 cores (16 cores in each server) are active with hyper-threading enabled by default.

Oracle Database Appliance nodes each contain two CPUs, and each CPU has six cores that are hyper-threaded. When you configure Oracle Appliance Manager on Oracle Database Appliance, all 24 cores (12 cores in each server) are active with hyper-threading enabled by default.

Oracle Database Appliance Bare Metal licensing is determined by the number of licensed cores that you have on your system. The capacity-on-demand licensing feature enables you to change the licensed CPU core count as your system resource needs change.

Initially set the number of licensed cores to the level currently required by your applications. Later, increase the licensed core count as your applications require more capacity. Change the number of licensed cores by obtaining and applying a core key to configure one of the options listed in the following tables:

  • See Table B-1 for Oracle Database Appliance X4-2 CPU core licensing options

  • See Table B-2 for Oracle Database Appliance X3-2 CPU core licensing options

  • See Table B-3 for Oracle Database Appliance CPU core licensing options

Table B-1 Bare Metal License Options for Oracle Database Appliance X4-2

Licensed Cores for Each Node Active Cores for Oracle Database Appliance X4-2

4

8

8

16

12

24

16

32

20

40

24

48


Table B-2 Bare Metal License Options for Oracle Database Appliance X3-2

Licensed Cores for Each Node Active Cores for Oracle Database Appliance X3-2

4

8

8

16

12

24

16

32


Table B-3 Bare Metal License Options for Oracle Database Appliance

Licensed Cores for Each Node Active Cores for Oracle Database Appliance

2

4

4

8

6

12

8

16

10

20

12

24


For Oracle Database Appliance Virtualized Platform, license the number of cores you need for ODA_BASE. The number of licensed cores must be the same on both servers and can be any multiple of two, from 2 to the maximum number of CPUs for your platform, where the maximum is:

  • 24 on Oracle Database Appliance X4-2

  • 16 on Oracle Database Appliance X3-2

  • 12 on Oracle Database Appliance

After determining the performance requirements for you applications, reduce your system's initial core count to the level required, and increase them as your requirements grow.

Rules and Restrictions for Changing the CPU Core Count

Review the following rules and restrictions before changing the CPU core count:

  • Obtain keys for the number of hyper-threaded active cores that you want, based on the version of the hardware you are licensing:

    • For Oracle Database Appliance X4-2, you must select 4, 8, 12, 16, 20, or 24 for each server

    • For Oracle Database Appliance X3-2, you must select 4, 8, 12, or 16 for each server

    • For Oracle Database Appliance, you must select 2, 4, 6, 8, 10, or 12 for each server

  • Changing the core count On Oracle Database Appliance depends on your configuration. For bare metal installations, after you initially change the CPU core count to a lower number of active cores, you may subsequently only increase the CPU core count, whereas on Oracle Database Appliance Virtualized Platform, you may increase or decrease the core count at any time. The following scenarios provide more details.

    • On Oracle Database Appliance X4-2, if you change to CPU core count to 16 for each server node, then you may subsequently change the CPU core count to 20 or 24. If you later change the CPU core count to 20, then you may subsequently change the CPU core count to 24.

    • On Oracle Database Appliance X3-2, if you change to CPU core count to 8 for each server node, then you may subsequently change the CPU core count to 12 or 16. If you later change the CPU core count to 12, then you may subsequently change the CPU core count to 16.

    • On Oracle Database Appliance, if you change the CPU core count to 6 for each server node, then you may subsequently change the CPU core count to 8, 10, or 12. If you later change the CPU core count to 8, then you may subsequently change the CPU core count to 10 or 12.

    • On Oracle Database Appliance X4-2 Virtualized Platform, if you change your ODA_BASE CPU count to 8 on each server, then you may subsequently change ODA_BASE count on each server to 2, 4, 6, 10, 12, 14, 16, 18, 20, 22, or 24. You may later change your ODA_BASE CPU count on both nodes to any of the valid values, which include all multiples of between 2 and 24 inclusive.

    • On Oracle Database Appliance X3-2 Virtualized Platform, if you change your ODA_BASE CPU count to 8 on each server, then you may subsequently change ODA_BASE count on each server to 2, 4, 6, 10, 12, 14, or 16. You may later change your ODA_BASE CPU count on both nodes to any of the valid values, which include all multiples of between 2 and 16 inclusive.

    • On Oracle Database Appliance Virtualized Platform, if you change your ODA_BASE CPU count to 8 on each server, then you may subsequently change ODA_BASE count on each server to 2, 4, 6, 10, or 12. You may later change your ODA_BASE CPU count on both nodes to any of the valid values, which include all multiples of between 2 and 12 inclusive.

  • You require the hardware Support Identifier (SI) to modify the core key on bare metal installations.

  • You may have more than one product under a single SI, but core key generation is unique for each Oracle Database Appliance, and is registered for the serial number of that Oracle Database Appliance.

  • If you want the maximum possible CPU core count for each server node, then use the default configuration and do not change the core count.. If you have more resources than you need, then you may lower the core count at that time. The maximum CPU core count on Oracle Database Appliance is dependent on the hardware version:

    • On Oracle Database Appliance X4-2, the maximum CPU core count is 24

    • On Oracle Database Appliance X3-2, the maximum CPU core count is 16

    • On Oracle Database Appliance, the maximum CPU core count is 12

    Note:

    If you followed the procedure to set your CPU core count to its maximum value, then you may no longer decrease your CPU core count on bare metal installations. If the error is caught immediately, contact Oracle Support Services for assistance correcting the error.

    See Also:

    Oracle Database Appliance Licensing Information for more information about core licensing

Changing the CPU Core Count

Note:

If you change the core count after the initial deployment, both servers restart. After the initial deployment, change the core count at a suitable time to minimize downtime for users.

To change the CPU core count on bare metal platforms:

  1. Gather the following information:

    • Support Identifier (SI)

    • Oracle Database Appliance serial number

    • Core count value that you want to configure

  2. Log in to My Oracle Support:

    https://myoraclesupport.com
    
  3. Click the Settings tab and select Assets from the menu.

  4. Search for the serial number of Oracle Database Appliance in the asset list.

    If you cannot locate the serial number, then contact Oracle Support Services.

  5. Select the serial number of Oracle Database Appliance.

  6. Select Manage Key... from the available actions.

  7. In the Manage Cores Configuration Key dialog box, view the serial number of Oracle Database Appliance. If a key was previously generated, then you may view the current configuration.

    1. In the Cores Per Server list, select the number of active CPU cores for each server that you want. The value that you select applies to both servers on Oracle Database Appliance and the valid values depend on the hardware version:

      On Oracle Database Appliance X4-2, initially select 4, 8, 12, 16, 20, or 24 CPU cores.

      On Oracle Database Appliance X3-2, initially select 4, 8, 12, or 16 CPU cores.

      On Oracle Database Appliance, initially select 2, 4, 6, 8, 10, or 12 CPU cores.

      Subsequently, you may only select a number that is greater than the current number on bare metal installations.

    2. Click Generate Key to generate the key.

    3. Click Copy Key to Clipboard to copy the key to the clipboard.

  8. Paste the key into an empty text file and save the file to a location on Oracle Database Appliance.

  9. Log on as root to one of the Oracle Database Appliance server nodes.

  10. Note: The command in this step restarts both Oracle Database Appliance server nodes to complete the reconfiguration.

    Run the following command where key_file_location is the full path name of the text file that you created in Step 8:

    /opt/oracle/oak/bin/oakcli apply core_config_key key_file_location
    

    For example:

    /opt/oracle/oak/bin/oakcli apply core_config_key /home/myfile.txt
    

After the system restarts, Oracle Database Appliance is reconfigured, and both servers are running with the specified CPU core count.

Note:

The procedure for changing the CPU core count is also documented in Oracle Database Appliance Licensing Information.

To change the CPU core count on Oracle Database Appliance Virtualized Platforms, follow the steps documented in the section "Resizing ODA_BASE" found in Chapter 6, "Managing Virtual Machines on Oracle Database Appliance."

See Also:

My Oracle Support note 1447093.1, "Oracle Database Appliance - Generating a Key via MOS to change your CORE Count" for additional information about requesting a key to change the core count, available from the following URL:

https://myoraclesupport.com