Comments for Ytria Tech Lab

Comment on When the dreaded “Field is too large (32K)” Lotus Notes error strikes… by Michael N

Michael N — Thu, 01 Dec 2011 17:55:33 +0000

Fixup -V helps (Domino 8.5.2FP3), all other tips failed, even ScanEZ couldn’t delete the document.

12/01/2011 06:32:41 PM Remote console command issued by Michael Niermann/415/INT/EEC: Load Fixup “database.nsf” -V
12/01/2011 06:33:17 PM Queuing compact command for database.nsf by Michael Niermann/415/INT/EEC

12/01/2011 06:33:18 PM Document NT000216C6 in database D:\Lotus\Domino\Data\database.nsf is damaged: Field is too large (32K) or View’s column & selection formulas are too large
12/01/2011 06:33:18 PM Document (UNID OF3E4B8880:85F8FDB7-ONC1257952:00348576) in database D:\Lotus\Domino\Data\database.nsf has been deleted
12/01/2011 06:33:29 PM Completed consistency check on database.nsf

12/01/2011 06:33:29 PM Database Fixup: Shutdown

Comment on A fast way to change NSF Replica IDs: Often a handy time-saver (and occasionally a life-saver) by Don

Don — Fri, 25 Mar 2011 17:25:23 +0000

If anyone out there can use these replica id switching tools to build a self migration tool for LotusLive, you’d be a hero! Is anyone in the Notes world working on one?

Comment on Are your Lotus Notes databases bloated with view indexes? Here’s a trick to help you cut file sizes by Morten

Morten — Fri, 28 Jan 2011 08:59:11 +0000

Another caveat: if your database is largish your users will kill you for purging the views. The wait introduced by forcing them to wait for the first view update is not a very nice thing to do to users and the procedure can seriously disturb the servers for hours the first morning after purging.

Besides, this doesn’t show you how many users are using a given view. If you have 2000 users and just one of them uses a specific view, that view creates nearly as much load on the server as the other used views and should be marked for deletion unless that user has no other options or is buying donuts for the admin team. Or is the CEO.

Then again, having many users in few views in a large database is a recipe for disaster. This is bound to cause semaphore locks and flatline all clients and the server at 0% throughput. Spread out the activity across many views if at all possible. Many databases is much better if you can do it.

The best option for reducing overall database size is to ensure that “Discard if unused” is set properly. Turn the number of days before purging down if you can. This will let Domino decide what to do based on the real usage pattern. Check your use cases first though, someone using a view for monthly reports is not going to be happy if s/he has to wait for a complete rebuild every time.

Also, the 7 day period for keeping views fresh can be set globally on the server with the proper INI incantations so there’s plenty of room for improving server performance without bothering the users.

Even with all these options tweaked don’t expect your databases to shrink much. Very large databases will, even with proper care and feeding, spend up 80 or 90% of their space on view indexes. This is not necessarily a problem that must be fixed. Remember: a large but mostly quiet database is not a problem for Domino, only for the person in charge of buying disks. A large database constantly needing view updates is.

Comment on Un-dead Lotus Notes Documents: How ‘ghosts’ can haunt your databases by MIke Driver

MIke Driver — Tue, 02 Nov 2010 16:39:51 +0000

Um… aren’t ghost docs (officially) the docs that get created to represent parent docs that have been deleted, so that if you do a “Set parentdoc = db.GetDocumentByUNID(doc.ParentDocumentUNID)” the retuned parent doc will be a ‘ghost’ of the deleted so that the orphan has a representation. This is very different to deletion stubs as these ghost will not get purged.
Yes, the parent doc that has been deleted will have a deletion stub also; as well as the ghost. Check it out with the bit of LS above.

Comment on How to Deal with “Private” and “Private on First Use” Views by Mark

Mark — Wed, 20 Oct 2010 13:00:19 +0000

There is also a 3rd way of simulating this private view type functionality. This 3rd way is with folders.
You can create a folder for each user and put and remove documents from the folders as needed with a bit of script. If you want to manage when these user folders get updated , you can check “do not allow refresh replace design to modify..” and user the undocumented function @UpdateViewDesign to update these views with a scheduled agent. So you would have one master view and @UpdateViewDesign would update all the folders based on the master view you pass as an argument to the function. This is userful if you have many folders and do not want to have to update each one manually if the folder design needs to be changed.
You only have to update the master view and the scheduled agent would update all the folders for you.

Comment on How hiding views from the Lotus Notes client can bring a Domino server to its knees by erichd

erichd — Fri, 01 Oct 2010 15:44:57 +0000

Here’s the link to the document given by Jérôme: http://www-01.ibm.com/support/docview.wss?uid=swg21238778

Comment on How hiding views from the Lotus Notes client can bring a Domino server to its knees by Jérôme Deniau

Jérôme Deniau — Fri, 01 Oct 2010 14:08:45 +0000

@ Rich
It’s not a fud to sell the product. That’s something we faced on many web apps we migrated from r5 to nd6 .
You can now access IBM information. Doc number is: 1238778 in IBM public kb!

Comment on How hiding views from the Lotus Notes client can bring a Domino server to its knees by Rich Wheadon

Rich Wheadon — Fri, 01 Oct 2010 13:01:52 +0000

I am having trouble believing this is true. Do you have something to prove this statement?

If you can prove this then it should be reported to IBM as a bug, did you report the bug?

Please elaborate since this sounds more like a FUD effort to sell your product.

Comment on How hiding views from the Lotus Notes client can bring a Domino server to its knees by Chris Hudson

Chris Hudson — Thu, 30 Sep 2010 23:33:24 +0000

I can’t understand why that checkbox option says “Notes” and “Client” yet the problem is impacting “Domino” and “server”. Surely Lotus should be able to fix that relatively easily. The server should be able to see these sort of views to replicate them, so being able to see them to update them should be possible.

Comment on Back from the NSF grave: How you can (sometimes) restore deleted Lotus Notes documents by Tweets that mention Back from the NSF grave: How you can (sometimes) restore deleted Lotus Notes documents | Ytria Tech Lab -- Topsy.com

Fri, 24 Sep 2010 17:58:30 +0000

[...] This post was mentioned on Twitter by Ytria and giuseppe grasso, andrehau. andrehau said: Reading Ytria Tip: How to restore deleted documents in Lotus Notes: http://bit.ly/c8h2Q6 – Great write up Peter! [...]