The status shows that post is running but messages are not posted . Show post detail indicates that it is in a recovery state.
An incorrect SharePlex Database user can cause the post process to be stuck in the recovery process, as the qseq of the queue and the shareplex_trans table do not sync up .
Check the paramdb file in $SP_SYS_VARDIR/data directory for this sp_cop instance, to see if the correct SharePlex user (SP_ORD_OWNER_O.SID) is being used . If the SharePlex user is incorrect then perform the following steps:
1. Stop post (sp_ctrl>stop post)
2. Shutdown SharePlex
3. Set env for this sp_cop and run ora_setup using the correct splex username
4. Restart sp_cop
5. Start post (sp_ctrl>start post)