The Shareplex documentation covers Oracle version upgrade in detail. However, such elaborate steps are not needed while upgrading Oracle from one patch to another within the same version.
When upgrading Oracle patch, say from 10.2.0.2 to 10.2.0.3, you do not need new Shareplex binaries as they binaries for any given Shareplex version are same for various Oracle patch in a given Oracle version. However, since the ORACLE_HOME can change, there are certain steps one needs to undertake after an Oracle patch upgrade. They are as follows:
1. Shutdown Shareplex gracefully before Oracle patch upgrade.
2. After the patch has been successfully applied, and if the ORACLE_HOME has changed, do the following:
a. Make sure that the environment variables ORACLE_HOME, LIBPATH and LD_LIBRARY_PATH are set correctly for the session that starts Shareplex.
b. Make sure that the var/adm/.splex /<Shareplex Version>/libxx links are correctly pointing to the new $ORACLE_HOME/lib32/libclntsh.so after the upgrade before starting up shareplex. (where substitute libxx with the appropriate string for your Oracle version and the same goes for <Shareplex Version>).
c. If you have multiple ORACLE_HOME for the same Oracle version, then in step b above, make sure that the links are correctly pointing to the $ORACLE_HOME/lib32/libclntsh.so for the lowest of the Oracle patches for that version.
3. Start Shareplex.
You do not need to run ora_setup although running it will not do any harm. The ora_setup will update structures of shareplex internal tables and is a necessary step during Oracle version upgrade but not during Oracle patch upgrade (under the same Oracle version). If you do choose to run ora_setup, make sure not to change the Shareplex user as doing so on source will require reactivation.