At first, this answer does not seem logical – but because of that I will explain in detail.
<b>To clear deletion stubs, first discover how many deletion stubs there are. </b>
1. Open the Admin Client.
2. In the Server > Server Console window, Issue the command <i>show database databasefilepath.nsf</i>
3. Document the output. The number of deletion stubs will be very near the top.
Note: Sizes of built views will also be displayed.
<b>Now make changes that purge the deletion stubs.</b>
5. In the Database properties, edit select the Replication Settings > Space Savers tab.
6. In the top section called “Remove documents not modified in the last (days)” there is a checkbox that is blank. IMPORTANT NOTE: DO NOT PUT A CHECK IN THIS BOX.
7. Document the number in the box in this same line of the dialog window.
8. Change the number to 0. This value is now changed, but it has not taken affect on the application.
9. Exit the Database properties. Ensure no other database views or documents are open in other Workspace tabs.
10. Click on a different database icon, then back on the database. Do this several times. Thes access actions should force the new zero-days purge interval to evaluate and deletions stubs will be removed.
11. In the Admin Client, issue show database command again. TIP: If you have not closed the admin client in the intervening steps, this command will still be in your list of recent commands.
12. Document the output. The Deletions stubs value should be 0.
<b>Restore the Purge Interval</b>
13. Edit the Space Saver tab of the Replication settings and change the “days” value back the amount you documented in a previous step.
NOTE: Any documents that were previously deleted in this replica, but still exist in other replicas of the file, will come into this file the next time replication occurs.
<b>Other information about IMPORTANT NOTE, above.</b>
If you do check the box, any document that has not been modified in the last whatever number of days listed WILL BE DELETED – this is not what you want to happen. The number on this selection has a two-fold purpose. When it is checked, it deletes documents that have not been modified in that number of days. OTHERWISE, the number is used to calculate the purge interval, which is what the server uses to purge deletion stubs. How that interval works is this:
You take 1/3 of the number set on this value (we’ll use 90 since that is the default), so 30 days, and add it back to the number – so 120 days. So the purge interval is between 90 and 120 days. So when the purge process runs, any deletion stubs that exist that are between 90 and 120 days old will be purged.
Hope that makes sense, if not, let me know and I will explain further.