Exadata X6 Machine Is Not Showing Increased Corecount Value (Doc ID 2269705.1)

Last updated on JUNE 20, 2017

Applies to:

Oracle Exadata Storage Server Software - Version 12.1.2.3.0 and later
Information in this document applies to any platform.

Symptoms

 After increasing the cores on Exadata the cpu_count parameter in database remains at old value

~]# dbmcli
DBMCLI: Release - Production on Wed May 03 08:52:02 CEST 2017

Copyright (c) 2007, 2014, Oracle. All rights reserved.

DBMCLI> LIST DBSERVER attributes coreCount
32/44
DBMCLI> LIST DBSERVER attributes pendingCoreCount
DBMCLI>

DBMCLI> list dbserver attributes pendingcorecount,corecount,cpucount
32/44 44/64


Server and Databases has been rebooted, but after restart of database the cpu_count takes automatically the old valus of 44


we can see below cpu offline errors in OS messages file at same time

kernel: CPU 11 is now offline
kernel: CPU b offline: Remove Rx thread
kernel: CPU 27 is now offline
kernel: CPU 1b offline: Remove Rx thread
kernel: CPU 43 is now offline
kernel: CPU 2b offline: Remove Rx thread

 

Changes

 Cpu core count increased on this Exadata machine by using DBMCLI,but it is not properly reflected at host and Database level

DBMCLI> LIST DBSERVER attributes coreCount
32/44
DBMCLI> LIST DBSERVER attributes pendingCoreCount

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms