Compare takes a very long time after the first activation (75938)

The sp_ctrl prompt does not come back after the compare command is issued, it looks like compare is hanging.

The event_log and compare log show no errors.

This is the first compare after activation , so compare has to build a file in state directory based on each entry in the config file. If the config file is huge with lots of tables then compare would take time to build this file.

The file is *deq*<pid of compare>.

Wait for the compare to finish.

The progress of compare can be monitored by looking at the file *deq*<pid of compare> in the SP_SYS_VARDIR/state directory. Compare reads the config file sequentially and writes the related information into the *deq*<pid of compare> file, so the last entry in the *deq*<pid of compare> file will give an estimate as to at which point the compare is reading in the config file and how many table entries are left to be read and written to the *deq*<pid of compare> file.