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:

  • 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.

  1. Log in as the root user on the first database server.

  2. Activate the database server cores using the following dcli utility command on the database server group:

    # dcli -g db_group -l root  'dbmcli  -e    \
    ALTER DBSERVER pendingCoreCount = number_of_cores'
    

    In the preceding command, 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. The following command shows how to activate all the cores in Oracle Exadata Database Machine X5-2 Eighth Rack:

    # dcli -g db_group -l root 'dbmcli -e ALTER DBSERVER pendingCoreCount = 36'
    

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

  3. Restart each database server.

    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.

  4. Verify the following items on the database server after the restart completes and before proceeding to the next server:

    • The Oracle Database and Oracle Grid Infrastructure services are active.

      See Using SRVCTL to Verify That Instances are Running in Oracle Real Application Clusters Administration and Deployment Guide and the crsctl status resource –w "TARGET = ONLINE" —t command.

    • The number of active cores is correct. Use the dbmcli -e list dbserver attributes coreCount command to verify the number of cores.