During Mammoth 4.5 to 4.8 Upgrade "Maximum Non-Java Memory of Service Monitor" Gets Reset to 0 From the Existing Value (Doc ID 2303033.1)

Last updated on SEPTEMBER 01, 2017

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Symptoms


During Mammoth 4.5 to 4.8 Upgrade "Maximum Non-Java Memory of Service Monitor" gets reset to 0 from the existing value. The existing value can be the default or a custom setting.  An error message indicating the value reset is raised.

Navigating in CM: mgmt > Instances > Service Monitor > Configuration > Search: Maximum Non-Java Memory of Service Monitor, shows that instead of the default value or custom value, the value is incorrectly set to "0" GB.

 

 

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