I don't see anything to be very concerned with. The thing to understand is that 'filenames' is not a fixed value that you are in danger of exceeding. The IDB is dynamically expandable, although it does have some limits, which you can see in the output from 'omnidbutil -extendinfo'. As your tablespaces become full, you can just create a Tablespace extension in the IDB context of the GUI
I don't see anything in your tablespaces that require immediate attention
What you are looking at in the iDB_report is a ratio. The Red is records used, the Green is Records TotalI usually have folks run
omnidbutil -info
which shows the same results, except in 'text' format
A high ratio is a sign of a healthy IDB, we like the ratio to be as close to 100% as possible, so, in my opinion, you are in pretty good shape
As ongoing maintenance, I advise that you check the IDB context for old sessions, if you see any, find out what media was used for that old session, and export it. Run the 'omnidbutil -extendinfo' (contained in the file you sent 'procedures') about once a month, if any tablespaces are getting full, pro-actively create new extensions. About once every 6 months, do a 'writedb/readdb' to purge the IDB and recover disk space. I would probably skip these steps in the procedure as being unnecesary
7. omnidbutil -cdbsync <Cell_server_Hostname>
8. omnidbutil -fixmpos
and I usually don't advise that these steps be done, although it is not going to hurt you
2. omnidbutil -purge -filenames -force
(perhaps you need to wait some time before the next step)
3. omnidbutil -purge -dcbf
Finally, whenever you manipulate the IDB, I strongly advise that you stop DP and make a copy of 'db40', and restart DP. Things don't often go bad when doing any of this, but, when they do, they go really bad, and you always want to give yourself a return point