The monitoring scripts are provided in Shareplex as a template and need to be customized. The scripts are located in /proddir/util directory (where proddir refers to Shareplex Product directory). Chapter in Admin Guide titled "Unattended Shareplex Monitoring" delves on setting up the monitoring script. At times the customers upgrade and have this question about whether it is possible to seamlessly port these customized monitoring scripts from an older version on a newer version of Shareplex.
Need to migrate/port the monitoring script from the older version to the new version of Shareplex.
For the most part it is possible to port the scripts from older version to the newer version. However, if the newer version introduces new features, then the monitoring scripts will need to be modified to accomodate the changes. In addition, the following considerations need to be kept in mind when doing so:
1. Be sure to always test any customized code prior to putting it into production.
2. Since the version change may be accompanied by changes to server names, domain names, Oracle SID names, etc, the testing will be able to expose any shortcomings that need to be rectified.
3. The scripts may fail in newer version of Shareplex due to features added in newer versions of Shareplex. By the same token they may also fail if some features are deprecated.
4. Introduction of bugs, though very rare, can also result in failure of scripts. So testing helps.
5. It may be worth sifting thru the script templates provided in newer version of Shareplex since they may have valuable modifications due to a continuing evolution of the product and addition of new features. Simply porting the older scripts by replacing these newer templates may deprive users of these modifications or make the script inoperable.
6. Upgrade provides an opportune moment to revisit these scripts since they were last customized. Typically the scripts are overlooked once they are deployed. By sifting thru the older scripts one can find out if the parameters such as queue threshold, errors to be monitored, etc, need to be looked into and modified to reflect the current state of replication.
It may be worth noting that the scripts are provided as template only and the customers need to tailor it to suit their requirement. Another thing to note is that the monitoring scripts can be overwritten by the upgrade process so one may want to back them up before upgrade.