Noticed the below error in SharePoint 2013 health analyzer .
In some situations, a content database that is used by Microsoft SharePoint Foundation may become corrupted. The corrupted database may contain orphaned items. For example, a document may not have a parent document library or a list may not have a parent Microsoft SharePoint Foundation Web site. Consequently, you may be unable to create new items with the same URL as the orphaned items, and space in the content database will be consumed unnecessarily.
This reported content database has one large site with 150Gb data and one small orphaned site . This small site size is 4GB.
Clicking on automatic repair is not resolving the issue.
Will the content database become corrupted over a time in production?
Is this some thing risk to application?
How can we resolve this issue with any other approach?