I think I have another option here without touching the publication database ...

1. Stop the application (to ensure that no more data added to table)

2. Take full backup of mydb database

3. Restore the database as mydb_corrupt

4. Change the mydb_corrupt to Single_user mode

5. Repair the table TestTABLE in mydb_corrupt with allow_data_loss

6. Rename the table TestTABLE to TestTABLE_old in mydb database

7. Export the TestTABLE from mydb_corrupt to mydb database

8. Run DBCC Checktable

9. Start the application and verify

10. Once all ok, drop the table TestTABLE_old