At times the one-off binary (or binaries) are packaged in the form of a complete build of Shareplex. It is provided in the form of a .tpm file. This solution delves on a couple of different ways to apply the one-off.
The one-off is not provided as individual binary but is rather packaged, so applying it may need special considerations.
First of all ensure that the checksum of .tpm file matches the one provided by Support or Development as a part of deployment instructions. The command to determine the checksum is cksum. Also, make sure that the OS, Oracle and Shareplex version mentioned in deployment instructions matches with your environment.
There are two different ways to apply such one-off. First and foremost, it depends on whether the Development has specified what binaries have changed from the mainstream Shareplex version in this build. Second, the user has to decide whether he/she is interested in extracting those one-off binaries and then deploying them in place of the original binaries. The following are the two approaches that can be followed:
A. Re-installing Shareplex using the one-off build as if it were a patch upgrade:
The following steps are involved:
1. Shutdown Shareplex.
2. As root, do the chmod 555 on the .tpm file to make it executable.
3. Make sure that the session has the correct setting for the environment variables SP_SYS_VARDIR, ORACLE_HOME, ORACLE_SID, SP_COP_TPORT, SP_COP_UPORT, among others.
4. As root or any appropriate user (which was earlier used to install this instance of Shareplex), run the .tpm file, and respond to the prompts as appropriate. Make sure to specify the existing product directory when prompted. This will result in overlaying of existing binaries with the binaries contained in the package (or build). Not all binaries in the package are one-offs but the user need not be concerned about extracting the one-offs selectively and applying them. Rather, the installation process applies all binaries in the package including the one-offs.
5. As the correct user start sp_cop. It could be root or non-root depending on how Shareplex was configured to be started.
B. Extracting the one-off binary (or binaries) only and deploying them in place of the original binary/binaries:
1. As root, do the chmod 555 on the .tpm file to make it executable.
2. Do another fresh install of Shareplex that is different in terms of vardir, proddir and port numbers of the existing install. Make sure that the session has the correct setting for the environment variables SP_SYS_VARDIR, ORACLE_HOME, ORACLE_SID, SP_COP_TPORT, SP_COP_UPORT, among others . Ensure that the environment variables SP_SYS_VARDIR, SP_COP_TPORT, SP_COP_UPORT and the one for Product Directory do not clash with the original Shareplex instance running on this server. Run the .tpm file, and respond to the prompts as appropriate.
3. Once the new installation is complete, get the one-off binary/binaries from it and deploy these in original installation of Shareplex. Shutdown Shareplex, save the original binary in the bin directory of Shareplex, then deploy the one-off binary after making sure that the ownership/permission is appropriate. See SOL53506 for details on the directory structure of product directory, etc. As mentioned above, the approach in para B depends on whether the one-off binaries contained in the build have been separately identified by Support/Development.
