Are there any implications due to the paramdb file still retain the default values for Shareplex (4300806)

Normally the paramdb file located in $SP_SYS_VARDIR/data directory only contains Shareplex parameter values which are set other than the default. At times the paramdb file may contain default values for certain parameters. This solution addresses questions on implications of such parameter entries in paramdb file. The following is a sample portion of paramdb containing such residual values:

For example:

SP_OPO_DEBUG_FLAG 0x00000000 # Poster dynamic debug flag
SP_OPO_DISABLE_OBJECT_NUM  # disable an object by object number

General information.

When a Shareplex parameter is set by the command set param <parameter_name>, a new entry is appended to the paramdb file that contains the new value for that parameter, which happens to be something other than the default. This value did not exist in paramdb when Shareplex was first installed. From this point on the parameter is referred to by Shareplex instead of the default. When a Shareplex parameter is reset by using the command reset param <parameter_name>, the parameter is set back to its default value which is also reflected in the entry for such parameter in paramdb. So even a residual entry for the parameter remains in paramdb, it only contains the default value and there should be no cause for concern. It just increases the size of the paramdb file.