During Upgrade, thefollowing error occurs:
Error setting Multi-threaded post for SP_COP_PORT 8765 and SP_SYS_VARDIR /splex/SharePlex-5.1.7.575up/var9i_secondvar
Invalid entries in the vardirs.log will cause the upgrade to fail and the user will be instructed to contact Technical Support.
For example: Two entries for the same vardir in this situation
There may also be embedded characters in the vardirs.log and/or the shareplex.mark entries not visible that could cause the error.
RESOLUTION 1:
Check vardirs.log and make sure it contains valid entries before performing Upgrade.
For Example two entries of vardir in this situation
============= Vardirs.log============
o920v64a@irvqasu09 > cat vardirs.log
9765 /splex/SharePlex-5.1.7.575up/var9i
2100 /splex/SharePlex-5.1.7.575up/var9i_secondvar
8765 /splex/SharePlex-5.1.7.575up/var9i_secondvar
RESOLUTION 2:
If the vardirs.log and shareplex.mark files seem correct, there may be either invisible embedded characters in those files or those files may be corrupt. If you check these files and they seem correct but still get the error, do the following:
1) Rename the shareplex.mark
2) Rename the vardirs.log
3) Export appropriate SharePlex environment variables to overwrite the shareplex.mark file (SP_SYS_VARDIR, SP_COP_UPORT, SP_COP_TPORT , ORACLE_SID, ORACLE_HOME, etc)
RESOLUTION 3:
1) vi $SP_SYS_VARDIR/data/paramdb file
2) look for SP_OPO_TYPE parameter
3) IfSP_OPO_TYPE set to 0 (single threaded post), comment this line and save the file
NOTE: in 5.3, the default value for SP_OPO_TYPE has been changed to 1, causing the multi-threaded post to be launched by default. If using single threaded post prior to the upgrade, this error occurrs.
4) retry the upgrade.
