My Oracle Support Banner

CPU_COUNT Causes ORA-00068 (Doc ID 1914172.1)

Last updated on FEBRUARY 26, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 11.2]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.


If a system has a high CPU count and there is no value set for parallel_max_servers then the system may try to set the default value of the parallel_max_servers parameter higher than is allowed, the following errors could be generated in both alert.log and trace files:

ORA-02097: parameter cannot be modified because specified value is invalid
ORA-00068: invalid value 6360 for parameter parallel_max_servers, must be between 0 and 3600
CKPT (ospid: 22135): terminating the instance due to error 2097

This can cause an instance shutdown if the number of system CPUs alters dynamically.

CPU_COUNT is not explicitly set in init.ora file

stack trace: ksbcpu_mod()->ksbcpcb()->kxfpCPUCountUpdate()




To view full details, sign in with your My Oracle Support account.

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

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.