It means that there was an ambiguity in issuing the compare command where the value for threads was set by both the ‘threads’ option at command level and by setting of the parameter SP_DEQ_THREADS. The values stated via these two routes were different so the value set at command option route took precedence.
As an example the following compare parameter was set at the sp_ctrl level prior to running a compare:
sp_ctrl>set param sp_deq_threads 10
However, when compare was run, the compare command specified the “threads” option via sp-ctrl but specified a thread value of 5 instead of the one set by “set param”:
sp_ctrl>compare owner.table_name threads 5
The command level setting took a higher precedence as shown below:
desvr 2014-04-28 14:13:47.849704 17984 1 Note: user overrode parallelism to 5
desvr 2014-04-28 14:13:47.849714 17984 1 Note: reset thread count to 5