Some Database Resource Properties cannot be set to higher (valid) settings through OE Console

Some Managed Database Resource Properties cannot be set to higher (valid) values through OE Console

When some Database Resource properties values are increased through Property file configuration (configuration), the property value change fails to save with:

• The database does not start
• The database can no longer be seen in the OpenEdge Console and needs to be Deleted from the config database
• Exception : com.progress.common.property.PropertyManager$PropertyException   
  Message (throw): Juniper: Failed to load.
  Message (excp):  The following errors occurred whilst loading a property file:  In group "configuration.<dbname>.defaultconfiguration":  Invalid property value: "<value>" for property: "<property_name>"

• The database starts
• Despite the error:
  [ConnectionManager]   * The following errors occurred whilst loading a property file:  In group "Configuration.<dbname>.defaultconfiguration":  Invalid property value: "<value>" for property: "<property_name>".  
• The changed database property value is set to the higher value confirmed in the lg file startup message related to that database startup parameter and PROMON views.

The value being configured for the database startup parameter is a valid value for the OpenEdge version in use

The juniper.schema file used to identify the min/max values for a parameter has not been updated to current min/max values of configurable database startup parameters in the OE Console Configuration UI.

Upgrade to OpenEdge 11.6.3, 11.7.0 or later, where the juniper.schema file used to identify parameter min/max values has been updated to current version min/max values of configurable database startup parameters in the Configuration UI.

To set a database startup parameter higher than the validation message allows:

First confirm that the required property value is within the value range:

• Value default, minimum and limits are found in:

• The Validation message may be correct, depending on the current OpenEdge version and which version parameter value limits were changed.

• Another means of confirming the database startup parameter value outside the AdminServer, is to start a test database with the required database startup parameter values configured in the conmgr.properties from the command line (proserve):
  • How to start a database using the startup values in the conmgr.properties file  

Use a buffer for the startup parameter value

1. In the OE Console, Configuration UI set the parameter within the Validation message values.
2. Set required value of the related database parameter in "otherargs"

If the parameter was greater than the validation value in the conmgr.properties before the AdminServer was started and was since started, don't delete the database resource:

1. Stop the AdminServer
2. Edit DLC/properties/conmgr.properties and change the parameter within the validation message values and set the required value of the related database parameter in "otherargs"s.
3. Restart the AdminServer

Example: Setting Maximum Servers higher than 512, the value changes fail to save with:
# conmgr.properties

[configuration.<dbname>.defaultconfiguration]
    maxservers=512 # <any value LE max_value errant validation message>
    otherargs=-Mn 513 # <required valid parameter value GT max_value errant validation message>

Progress Article:

Incorrect default database startup parameters are shown for a managed database