Job Comparison Stops Responding

Problem: A job has successfully executed, but one or more of its comparisons (source or target) stops responding and shows a count of -1, 0 percent progress, and no error message.

Possible cause: DA server is waiting for the row count to complete. If the database table is not optimized for the select count query, it may take the database server a long time to execute the row count. While DA server is waiting, the command prompt shows a negative count, 0 percent progress, and no error message for the job.

Try either of these solutions:
  • Optimize the database table by creating a new index on the key column so the select count query executes faster.
  • Alter the job comparison to set enable_row_count to false.
Parent topic: Troubleshooting