2.1.2.2 Activating Database Server Cores in Oracle Exadata Database Machine Eighth Rack

The following procedure describes how to activate database server cores.

Note:

This procedure applies to activating:

• Original database server CPU cores that are disabled.

• Additional CPU cores that are part of an approved CPU upgrade kit.

The following is not required where database server hardware resources are expanded by adding more database servers.

Perform the following on each database server. The database server may need to be restarted after enabling additional cores. If the database servers are part of a cluster, then they can be restarted in a rolling fashion.

1. Verify the number of active physical cores using the following command:

   DBMCLI> LIST DBSERVER attributes coreCount
   

2. Use the following command to increase the number of active physical cores:

   DBMCLI> ALTER DBSERVER pendingCoreCount=<new_number_of_cores>
   

   In the preceding command, <new_number_of_cores> is the total number of cores to activate. The value includes the existing core count and the additional cores to be activated.

   For a description of the supported core counts for each server model, see Restrictions for Capacity-On-Demand on Oracle Exadata Database Machine.

3. Verify the pending number of active physical cores using the following command:

   DBMCLI> LIST DBSERVER attributes pendingCoreCount
   

4. Restart the server (if required).

   You must restart the server to enable the new active cores if the output from the previous ALTER DBSERVER command states that a reboot is required or if the command provides no output about restarting the server.

   A server reboot is not required only if that is indicated in the output from the previous ALTER DBSERVER command.

   Note:

   If this procedure is done in a rolling fashion with the Oracle Database and Oracle Grid Infrastructure active, then ensure the following before restarting the database server:

   • All Oracle ASM grid disks are online.

   • There are no active Oracle ASM rebalance operations. You can query the V$ASM_OPERATION view for the status of the rebalance operation.

   • Shut down Oracle Database and Oracle Grid Infrastructure in a controlled manner, failing over services as needed.

5. Verify the number of active physical cores using the following command:

   DBMCLI> LIST DBSERVER attributes coreCount
   

6. If the database server was restarted, verify that Oracle Database and Oracle Grid Infrastructure services are active before proceeding to the next server.