At times Shareplex may run into issues or limitations. One-off binary may be provided to address them. The one-off binary replaces the original binary to either run perpetually or to run for a finite period pending the outcome of the results from the one-off. In either case certain steps need to be undertaken to deploy the one-off. Starting with Shareplex 6.0 and up,there has been a material change in the structure of the product directory (proddir) of Shareplex. Consequently the procedure to apply the one-off has also changed. This solution delves on the changes.
The following instructions apply to Unix and Linux.
The instructions for deployment of one-off are usually provided by Support/Development when furnishing the one-off. The instruction provided by development may supersede the instruction provided below. When deploying a one-off, regardless of the purpose of one-off, perform the following:
1. Make sure that the one-off has been downloaded in proper mode (ascii or binary) depending on the file type of one-off. Any compiled oneoff, such as sp_ocap will need to be transferred using binary mode. Any text file will need to be transferred in ascii.
2. Check the checksum of the one-off. For most OS, the command to check it is cksum. Verify that it matches with the value provided by Support as a part of deployment instructions.
3. The file provided is usually meant to replace a binary in /proddir/.app_modules, (although there is a link to this file from proddir/bin which makes it seem like the file resides in proddir/bin). If the file provided contains a link from /proddir/bin directory, then go to the /proddir/.apps-modules directory, save the original binary by copying it to some other name and deploy the one-off binary by renaming it to the original name of the binary. The reason for this is that the binaries do not reside in /proddir/bin but do so in /proddir/.apps-modules and have a soft-link created from former to latter.
At times, the oneoff may be a library meant to replace a Shareplex library located in /proddir/lib directory.
Though very rare, it can also be a param-default file containing some customized parameter and is meant to replace the original param-default file located in /proddir/data directory.
If the file provided forms a part of either /proddir/lib or /proddir/data directory, then simply save the original file by copying it to some other name and deploy the one-off by renaming it to the original name of the file (which happens to be a library or a param-default file).
4. Make sure that the ownership/permissions of the deployed file are appropriate. Compare it to that of the original file as it existed prior to deployment of the one-off and make sure that it is identical.
5. In case of any debug one-off, if any debug needs to be set along with the deployment, then the instructions should be there in the email from Support. Sometimes the one-off has debug feature built into it inherently and therefore do not have to set explicitly. In either case please collect the debug logs.and forward them to Support.
Instructions for applying a oneoff on WindowsNT are different. In most cases development will provide an .exe binary, which will be an entire build. To apply the patch on WindowsNT
1. Shutdown Shareplex.
2. Make sure Shareplex services are down.
3. Double click on the .exe and follow the instructions on screen.
4. Start shareplex.