We don't use LOB fields in our databases so I can't give you any hands-on tips for using them. But I am aware of people who used BLOBs/CLOBs to store large amounts of unstructured data in their databases because they could and, in the long term, regretted it.
I think you should ask yourself: are you planning to use a database as a proxy for a file system? If so, it will be more time and money and hassle to manage. Do you have a policy for the life cycle of the data? If not, it is difficult to determine the management cost up front.
Do you actually need to execute relational queries on this data? If not I would think twice about storing it in a database. For example, I wouldn't put it in an OpenEdge database just because it needs to be secure. A modern OS/file system should provide access controls at least as granular and robust as you will get from an OpenEdge database.
If you need a full-blown document-management system, then the scope of this discussion changes. You could possibly build that with an OpenEdge back end, but designing and building it would be non-trivial. Purchasing a purpose-built solution, if you can find one to meet your needs, might be more economical and provide faster time to market than building it yourself.