Incorrect default database startup parameters are shown for a managed database

OpenEdge Console shows wrong default values for database startup parameters

While default values exist for unspecified startup parameters they are never written to the configuration file: conmgr.properties
The database is started with the correct default values for unspecified startup parameters

When the wrong default values are configured the changed value is written to the conmgr.properties configuration file and are used the next time the database is started

If an incorrect default value is explicitly entered, it is taken literally and the database may fail to start.

OpenEdge 11.7.4: List of incorrect default startup parameter values:

 

Database Startup Parameter	Default Value shown	Documentation link / additional Comment	real default value
Before image cluster age (-G)	60	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fbefore-image-truncate-interval-(-g).html%23	0
Group delay (-groupdelay)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fgroup-delay-(-groupdelay).html%23	0
After image buffers (-aibufs)	5	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fafter-image-buffers-(-aibufs).html%23	20
Database service communication area size (-pica)	64	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fdatabase-service-communication-area-size-(-pica).html%23	16 (in multi user)
Maximum number of database areas (-maxareas)	1	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fmaximum-area-number-(-maxareas).html%23	32000
Nap time increment (-napinc)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fnap-time-increment-(-napinc).html%23	10
Nap max interval (-napmax)	1	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fnap-maximum-(-napmax).html%23	250
Nap time steps between nap time (-napstep)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fnap-time-steps-(-napstep).html%23	5
Semaphore sets (-semsets)	1	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Fsemaphore-sets-(-semsets).html%23	3
Maximum shared-memory segment size (-shmsegsize)	128	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dpspr%2Fshared-memory-segment-size-(-shmsegsize).html%23	the value should be at least 1024 when using a 64 Linux OE installation, real default value depends on the database installation
Number of open SQL cursors (-SQLCursors)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dpspr%2Fsql-open-cursors-(-sqlcursors).html%23	50
SQL stack size (-SQLStack)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dpspr%2Fsql-stack-size-(-sqlstack).html%23	1
SQL statement cache size (-SQLStmtCache)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dpspr/sql-statement-cache-size-(-sqlstmtcache).html	100
SQL sorting memory (-SQLTempBuff)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dpspr%2Fsql-sorting-memory-(-sqltempbuff).html%23	1000
Blocks in database buffers (primary) (-B)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm/blocks-in-database-buffers-(-b).html#wwID0E16IV	calculated by Maximum of (8 * users) or 3000
Alternate buffer pool (-B2)	0	By default B2 is not enabled or used therefore should not be 0 but empty
Before image threshold (-bithold)	3	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Frecovery-log-threshold-(-bithold).html%23	no default value should be shown as by default bithold is not set
Hash table entries (-hash)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm/hash-table-entries-(-hash).html	approximately 1/4 of the -B value
Lock table hash table size (-lkhash)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dmadm%2Flock-table-hash-size-(-lkhash).html%23
TXE commit lock skip limit (-TXESkipLimit)	0	Is there a parameter for TXE commit lock skip limit ?	10000
Shared memory overflow size (-Mxs)	0	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dpspr/shared-memory-overflow-size-(-mxs).html	If your system uses a 4 byte integer, then the formula is: 16KB + (n*300). For all other systems, the formula is: 16KB + (n*400).
Maximum shared-memory segment size (-shmsegsize)	128	https://documentation.progress.com/output/ua/OpenEdge_latest/index.html#page/dpspr%2Fshared-memory-segment-size-(-shmsegsize).html%23	value of at least 1024 on a 64 bit OE installation on Linux
SQL sorting on disk (-SQLTempDisk)	0	What are the new SQL-92 Startup parameters for Progress 9.1D?	500000
SQL temporary data page size (-SQLTempPgSize)	0	What are the new SQL-92 Startup parameters for Progress 9.1D?	7
Maximum number of JTA transactions (-nmaxxids)	0	What new database startup parameters have been introduced in OE 11 ?	100

 

Databases managed by the AdminServer show all database startup parameters OpenEdge Explorer/Management web interface under the Configuration Properties view:

While considered a cosmetic defect, the OpenEdge Console properties initial field display values need to be reviewed.  Enhancement ADAS-11160 was raised, but has not been implemented in the product to date (OpenEdge 12.2). 

Ignore the default values for unspecified database startup parameters shown in the OpenEdge Console Configuration Properties view.

While incorrect, these are initial field display values only and have no effect on the true default value used when the database is started and shared-memory is initialised with required parameter values. 

Any startup parameter that is not present for the managed database in the conmgr.properties are initialised with their default or calculated value by the Database Manager when shared-memory is initialised, not the AdminServer 

As an example: refer to the following Article which explains the incorrect default value for the Before image threshold (-bithold)

• 000029003, In Database Configuration Properties, why does the value 3 for "bi threshold" have no effect?