Upgrading Shareplex from 4.0 to 5.1. Supplemental logging was not on. Ora_setup looked as if it were hanging on shareplex_rowidmap table. Looked inside Oracle, saw that ora_setup was doing selects and creating an index on shareplex_rowidmap table. So ora_setup was doing something in the background, but it was taking a long time.
shareplex_rowidmap table had 8 million rows because supplemental logging was off and there was a lot of row chaining. This is why it was taking a long time to create an index.
ora_setup was not really stuck, it was taking a long time to create an index due to the size of shareplex_rowidmap. The only resolution is to wait while oracle creates the index.
This issue can be avoided by running ora_cleansp, then running ora_setup and then activating the config file. This will work because ora_cleansp will remove data from all shareplex internal tables and ora_setup will be able to quickly build the required indices. Enabling supplemental logging will also prevent this issue because shareplex_rowidmap table will not need to be maintained. However, these may not be viable solutions for some customers.