When SharePlex 9.0.243 (which was a Beta version) was already installed and it was attempted to be upgraded to SharePlex 9.0.0.6 (a mainstream version), the following errors were seen:
bash-3.00$ ./SharePlex-9.0.0-b6-oracle110-sun-10-x86-m64.tpm
Unpacking ..................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
..........................................................................
.......................................................................
SharePlex installation program:
SharePlex Version: 9.0.0
Build platform: sun-10-x86
Target platform: sun-10-x86
...Installation failed...
Installation log saved to: /export/home/oracle/.shareplex/INSTALL-SharePlex-9.0.0-1705291752.log
ERROR: tpm: spo-collect-legacy-instances: closed stream
bash-3.00$
SharePlex cannot be upgraded to the newer version due to incompatibility in upgrade path. In our case it is from a Beta to a mainstream version.
There could be many reasons an upgrade is not permissible from one version to another. Some of them are:
There is no upgrade path from previous version to the newer version.
The previous build is a special build, like Beta, one-off, etc.
If a fresh installation is acceptable, then do a fresh install on an entirely new proddir and vardir. If this is not acceptable, then contact Support for further help.
© 2022 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy