My Oracle Support Banner

SSSCTUNER still reports "Memory Resource Capping should not be enabled" though no memory capping is set (Doc ID 2630694.1)

Last updated on JUNE 18, 2020

Applies to:

Oracle SuperCluster Specific Software - Version 1.x to 3.x [Release 1.0 to 3.0]
Oracle Solaris on SPARC (64-bit)
Oracle Super Cluster

Symptoms

The scctuner still showing messages for "Memory Resource Capping" even after removing the Memory Capping for Solaris Zones ::


BEFORE UPGRADE ::
Sep 10 09:56:42 sscdbclient01 ssctuner: [ID 702911 local0.error] critical: Memory Resource Capping should not be enabled.

 

AFTER UPGRADE ::
Sep 14 15:20:21 sscdbclient01 ssctuner: [ID 702911 local0.error] critical: Memory Resource Capping should not be enabled.

Manual checking if there is capped-memory setting is in place turned out no such thing set :


root@sscdbclient01:~# clzc show -v fps-zc | grep capped-memory
root@sscdbclient01:~#

Changes

 

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


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