Let’s say I notice a 4GB nlo file. I would like to know where this is used to ask the user to consider deleting this document.
How do I generate a where used list of that nlo file?
I didn’t notice an applicable daosmgr option at IBM Documentation https://www.ibm.com/support/knowledgecenter/en/SSKTMJ_9.0.1/admin/admn_daosmanagertellcommands_r.html
Subject: no mechanism to do this but a suggestions
DAOS does not know which databases use a particular object, it only knows how many total references the object has.
you could use sh dir -daos (e.g. sh dir mail -daos) to see how many objects and bytes each database has and look for a files with > 4GB of total daos usage and then do a “tell daosmgr listnlo -o <filename.lst> <filename.nsf>” for databases you suspect might be holding this reference and then search the listing files for the nlo in question but this sounds tedious.
a) look for suspects with large bytes used or high average DAOS object size
sh dir mail -daos
DbName Version Log NIFNSF PIRC —Modified Time---- State Objects Total Bytes —Last Synchronized—
/local/notesdata/mail/maybe.nsf V9:52 Yes No Off 03/08/2018 09:15:43 AM Read/Write 2066 16332896 03/08/2018 09:15:43 AM
/local/notesdata/mail/nothere.nsf V9:52 Yes No Off 03/08/2018 09:15:43 AM Read/Write 1 13329 03/08/2018 09:15:43 AM
b) dump the list of objects for the suspectdatabases
tell daosmgr listnlo -o maybe.lst maybe.nsf
03/08/2018 09:48:16 AM DAOSMGR: ListNLO started for NSF:/local/notesdata/mail/maybe.nsf
03/08/2018 09:48:16 AM DAOSMGR: ListNLO output file: /local/notesdata/maybe.lst
03/08/2018 09:48:16 AM DAOSMGR: ListNLO completed - 2066 entries processed
b) search for the nlo in question
grep -c A42C8C2D26980BDFB10CCCEB171BCB24900CF20F00400000 *.lst
maybe.lst:1 << we have a winner !
In general, administrators try to control this type of occurrence by configuring a maximum message size in the server configuration or using a policy
http://www-01.ibm.com/support/docview.wss?uid=swg21569887 http://www-01.ibm.com/support/docview.wss?uid=swg21569887