Sometimes one may inadvertently leave parameter(s) at non-default value. This could be a result of a number of factors including, but not limited to, setting of debug on a process for investigation, tuning a process, bypassing posting on an object, bypassing an Oracle error, etc. Once the purpose has been served, one may forget to unset the parameter to undo the change. This can result in unintended consequences including slower process execution, unwanted bypassing of Oracle errors, etc.
Change management of Shareplex parameters.
There are two ways to determine the parameter change:
1. The most authoritative way to tell what parameters have been set to a value other than their default is to issue "list param modified" from sp_ctrl. This will list out all such parameters. Its output may include parameters such as license key, login info, etc, which will obviously be present in every Shareplex instance as non-default since the default for this information is NULL. But barring these, all other parameters would be of significance.
2. Another way to determine the parameter change is to view the file paramdb located in $SP_SYS_VARDIR/data directory. This file contains the login information for Shareplex user in the database and license key but also logs any parameter change. NOTE: Some parameters can only be set at the environment level at the OS, (for example, SP_OCF_SKIP_ANALYZE) and therefore will not show in the paramdb file.
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center