The post is in recovery and not comming out of it for days.
Show post detail output shows that the post state is in recovery.
Corruption in shareplex_trans table as the paramdb on a different port was pointing to the shareplex schema of this port causing the post of another port to write to this shareplex_trans table.
Make sure that Shareplex_trans table is not corrupt, query the v$session and look for the module, check to see that none other than the correct shareplex user (post) is accessing the shareplex_trans table.
Look at the paramdb file in $SP_SYS_VARDIR/data directory and verify that the parameter SP_ORD_OWNER_O.SID is set to the correct shareplex user. If there are more than one shareplex instance (port) then check the paramdb file for all the ports.