# Database inconsistencies after upgrade to DT3.6.3

**URL:** <https://discourse.devontechnologies.com/t/database-inconsistencies-after-upgrade-to-dt3-6-3/62749>\
**Category:** DEVONthink\
**Created:** [March 6, 2021, 1:46pm UTC](https://discourse.devontechnologies.com/t/database-inconsistencies-after-upgrade-to-dt3-6-3/62749 "2021-03-06T13:46:53Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![BLUEFROG](https://discourse.devontechnologies.com/user_avatar/discourse.devontechnologies.com/bluefrog/32/135_2.png) [@BLUEFROG](https://discourse.devontechnologies.com/u/BLUEFROG)\
**Post date:** [March 6, 2021, 9:25pm UTC](https://discourse.devontechnologies.com/t/database-inconsistencies-after-upgrade-to-dt3-6-3/62749/12 "2021-03-06T21:25:14Z")

</div>

A ghost file isn’t necessarily from DEVONthink To Go or sync. With a few file formats filtered out as _acceptable_, zero-byte files are detected and reported as problematic.

---

_[View the full topic](https://discourse.devontechnologies.com/t/database-inconsistencies-after-upgrade-to-dt3-6-3/62749)._