Recently, I had an opportunity to deployment eight rack Exadata Machine. As you might already know that it will require reducing active CPU cores on both compute nodes and storage nodes. As per Oracle documentation , this can all be done during Exadata deployment. Make sure you have reduce active CPU cores during OEDA process using capacity on demand section. In my case , Exadata deployment (OEDA) didn’t reduce active cores and i had to manually reduce cores on both DB nodes.
Problem Description : You can clearly see below Exadata deployment process just skipped compute nodes and only reduced CPU cores on storage nodes.
[root@node1 linux-x64]# ./install.sh -cf Intellitrans-ex.xml -s 2 Initializing Executing Update Nodes for Eighth Rack Skip Eighth rack configuration in compute node node1 running setup on: celadm01 running setup on: celadm03 running setup on: celadm02 cellnode3 total CPU cores set from 20 to 10 cellnode2 needs total CPU cores set from 20 to 10 cellnode31 needs total CPU cores set from 20 to 10 Skip Eighth rack configuration in compute node node2 Successfully completed execution of step Update Nodes for Eighth Rack [elapsed Time [Elapsed = 36051 mS [0.0 minutes] Fri Jul 13 20:31:36 EDT 2018]] [root@node1 linux-x64]# dbmcli -e LIST DBSERVER attributes coreCount 24/24
Solution : alter dbserver pendingCoreCount=10 force ( repeat on all db nodes )
[root@node1 linux-x64]# dbmcli -e alter dbserver pendingCoreCount=10 force Note :- reboot Exadata nodes [root@node1 linux-x64]# dbmcli -e LIST DBSERVER attributes coreCount 10/24