Health check settings on CPU_COUNT

Hello all,

I am running a health check on my database and the cpu_count parameter options appears as RED as it sees my parameter as being cpu_count=8

Oracle calculates this setting and sets it as required other than 0 after the initial default setting of 0,

Why does it then appear in red ?

thank you

That’s a good point. I guess Toad is expecting the value to stay at zero, and returning a “bad” condition because it is non-zero. Sounds like a false alarm to me.

Oh, and I just tested setting mine to zero, and then saw Oracle change it on startup.

I found the same to be true of all of the “Let Oracle determine the value” health check items. These will be removed next version.