Lotus Nut

The second "Total Duplicate Attachments found" line does precede the accurate statistic that was formerly labeled "Total DAOS Eligible Attachments." I've created SPR CSCT7PKM8R to correct this. The big thing to remember is that the data is still good. Just remember that the second line is the number of DAOS-eligible attachments.

The problem is not just the wording. The method for determining if an attachment is duplicated IS flawed. You're right that it is using the file name and the size, but that's it. In my case the attachments are auto generated PDFs and almost all of them have the same size but never the same creation data/time and this is not being taken into account.
Here's a line from the verbose output:

Attachment Name Size Compr Size Compr Type Refcount
CUSTOMER.pdf 4218 4218 None 4

All these files are different.

Just a note - I have seen what Vitor is referring to in his comment on my initial post and have verified that there are cases where if the file name is the same as well as the size reported in the DAOS Estimator report that the files are treated as the same object by the Estimator. But after enabling DAOS on the database and compacting it, the two attachments were treated as separate objects by DAOS even though the tool did not see them as different.

This means that you may save less space than the Estimator thinks due to some edge cases where you may possibly have attachments with the same name and physical file size but with different internal data. In Vitor's case with auto-generated files, the results may be very skewed. Again, each environment is different and ymmv. IBM is already aware of these findings above. :)

DAOS Estimator only compares the file name and file size to identify duplicates. This was a deliberate decision to maximize performance. The tool is only meant to estimate disk savings and not to provide a 100-percent accurate report.