I’ve search the forum a lot over the past few weeks and have been in contact with IBM on two different occasions but have not found anything that could help me with this issue so I created a login and put this out there for all to see hoping that someone has experienced this and possibly have figured out the cause. I hope someone can help because we’re really struggling with this issue and we’re usually a very self-sufficient crew.
[Problem and a little History]
We are currently running 6.51 Domino server on a single AS/400 server running v5R2. We have about 250 clients most of whom are running 6.02. About 10 remote users who hav not run the upgrade and are still running 5.11…every company has “those guys”
We upgraded to 6.02 in December 2003 and began experiencing problems when Domino would restart after backups ran. It seemed the server would begin to hit “Insufficient Memory” errors. At first the error would appear sporadically in the logs but they would increase in frequency until everything would come to a screeching hault. We contacted Lotus/IBM technical support and quickly upgraded to 6.51 after they recommended we do so. But this past weekend after restarting the Domino it started again. Here are a few lines out of the log file that demonstrate what we’re experiencing. It doesn’t seem to care what the file is so I’ve made all the actual file names generic.
[…it begins…]
04/04/2004 03:03:21 Updated database filename.nsf in catalog
04/04/2004 03:03:21 Unable to update entry in catalog (for filename.nsf): Insufficient memory.
[…then a little later…]
04/04/2004 04:30:43 Document NT00001716 in database /notes/domino01/data/HELP/help5_designer.nsf is damaged: Document has invalid structure
04/04/2004 04:30:43 Document (UNID OF035DAE8D:D990C466-ON8525687E:00587710) in database /notes/domino01/data/HELP/help5_designer.nsf has been deleted
[…still later…]
04/04/2004 04:31:16 NIF: DETECTED STORAGE CORRUPTION ERROR ‘B-tree structure is invalid’
04/04/2004 04:31:17 Error fixing view 4910 in filename.nsf: Insufficient memory.
04/04/2004 04:31:17 Error fixing view 314 in filename.nsf: Insufficient memory.
[…still later…]
04/04/2004 04:40:58 Completed consistency check on Address Book/filename.nsf
04/04/2004 04:40:58 Checking views in database Address Book/filename.nsf
04/04/2004 04:40:58 Error fixing view 486 in Address Book/filename.nsf: Invalid or nonexistent document
04/04/2004 04:40:58 Error fixing view 498 in Address Book/filename.nsf: Invalid or nonexistent document
[…until finally it all come to a screeching hault after about two full log pages of…]
04/04/2004 04:58:52 Insufficient memory.
04/04/2004 04:58:52 Insufficient memory.
04/04/2004 04:58:52 Insufficient memory.
By doing a full IPL on the 400 the problem will be fixed but in it’s wake is left a ton of damaged databases. “Invalid or non-existent documents” and missing design elements such as views, navigators, and forms. Mail files seem to be very vulnerable. This is really killing us and if you have any hints, suggestions, or thoughts, we’d be much appreciated.
Oh, and if you made it this far…thank you for reading this long winded message and I’m sorry it’s so long.