CPU_COUNT in V$SESSION_ENV is Different than CPU_COUNT Set for Database
(Doc ID 2741832.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle Database - Enterprise Edition - Version 19.6.0.0.0 and laterOracle Solaris on SPARC (64-bit)
Oracle Solaris on x86-64 (64-bit)
Symptoms
- V$ses_optimizer_env cpu_count is 32 but we have 64 cpu's and database system parameter cpu_count is 64, for example:
sqlplus / as sysdba
SQL> SHOW PARAMETER CPU_COUNT
NAME TYPE VALUE
------------------------------------ ----------- --------------------------
cpu_count integer 64SQL> column name format A20
SQL> column sql_feature format A30
SQL> select name, value, sql_feature from v$ses_optimizer_env where
sid=sys_context('userenv','sid') and name='cpu_count';NAME VALUE SQL_FEATURE
-------------------- ------------------------- ------------------------------
cpu_count 32 QKSFM_ALL
This is a server using SOLARIS OS and the problem is seen specific to SOLARIS OS and CPU_COUNT values in V$, GV$ views and the parameters derived on CPU_COUNT like DB_WRITER_PROCESSES.
Changes
Database was upgraded to 19c.
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |