It will be faster overall to stop that one sincle table replicate, delete the rows on both servers in parallel, then reestablish the replicate. There is no need to stop replication completely for all tables. Take a look at my dbdelete utility. It is the fastest way to selectively delete large numbers of rows from a table without encountering long transaction rollback problems. Dbdelete is contained in the package utils2_ak which you can download for free from the IIUG Software Repository.
Art
Art S. Kagel
Advanced DataTools (
www.advancedatatools.com)
Blog:
http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.