After upgrade how does Shareplex deal with deprecated parameters that exist in paramdb file (4297062)

Shareplex parameters are deprecated at times. Since any parameter setting that is different from the default is stored in the paramdb file, when a Shareplex instance is upgraded, such entry may still sit in paramdb file since upgrade preserves the paramdb file. The question is, how does Shareplex behave when a deprecated parameter exists in the paramdb file.

General information.

When Shareplex is upgraded, upon restart it will ignore any deprecated parameter still existing in the paramdb file. Though the parameter’s existence will not interfere with the running of Shareplex, it can be removed from paramdb, if it serves as a distraction. To remove it, shutdown Shareplex, edit the paramdb file by inserting the ‘#’ character (Pound character) as the first entry in the line that holds the deprecated parameter, save the file and restart Shareplex. The paramdb can be backed up, just in case it is required to revert to the old one.