We recently discovered a database that had some corruption due to the document compression bug related to 8.5.1. We have received a hot fix from Lotus Support to prevent any further database corruption, but we have had to repair and resolve issues with a number of databases.
As I was working on this particular database, after running fixup on the database, I attempted to run a folder upgrade, as we have found that some of the corruption relates to older folder designs. The folder upgraded failed. The error message returned indicated that the agent had exceeded the 64k limit.
So I started investigating further. We have a little agent we run to look at folder structures. It will look through each folder, determine how many documents in a folder, and prepare a list of all folders. I ran that agent. And waited, and waited, and waited.
The results came back. The user’s database contained 2,937 folders. Yes, you are reading that correctly. 2,937! This is an all time record for the users at our site. And we’ve had a few who have run amok with folders. My next step was to push data from a backup replica to the repaired replica to restore the corrupted documents that had been deleted during the fixup. Again, I waited, and waited, and waited. And here is the dialog that appeared after the replication completed. Yes 40,191,544 databases replicated! Well done Domino is all I could say!
My best guess is that because the folder structure exceeded the 64k limit on naming structure, somehow this affected the report back to the replication statistics dialog. I confirmed that the correct number of documents were restored by reviewing the database properties.
Sometimes you just have to see it to “believe it.”
Summer breeze…makes me feel fine! I’ll be heading to St. Louis for a few days in August to attend and present at IAMLUG. I hope to see you there!
Of course I couldn’t resist an opportunity to speak about one of my favorite products – Tivoli Directory Integrator – with my TDI blog series co-author Tom “Duffbert” Duff: Tivoli Directory Integrator (TDI) – The Best Free Tool You’ve Never Heard Of Tivoli Directory Integrator, or TDI for short, is a great (free!) tool you can use in your Domino environment. TDI moves and formats data from a large list of different data sources and targets using preconfigured connectors that come with the package. And don’t be mislead by the “Directory” part of the name! TDI can take data from nearly any data source (even directories) and integrate it into nearly any other data source (even directories). Oh, and did we mention it’s free if you’re licensed to use Domino? (This session is for both developers AND administrators!)
The fabulous “Dame of Domino” Gabriella Davis and I will be presenting a session about directories and authentication – a session you don’t want to miss! One Directory to Rule Them All? Yes! You’ve heard buzzwords like single-sign on, single userid, or authentication management, but also heard that they were a nightmare to implement. Or perhaps you always wanted to use another directory – like Active Directory for your Sametime, Web, IMAP or Traveler password authentication but thought it required a 3rd party tool or something installed on the Domino server? In this session we’ll show you how to configure your Domino server to authenticate with either the HTTP Password or the LDAP directory password without a server reboot! We’ll extend that idea to demonstrate how with a little bit of magic and a sprinkling of Tivoli Directory Integrator you can get closer to that simple single userid or directory system you’ve always wanted. Check out Gab’s other IAMLUG sessions here.
We deployed Lotus Notes Traveler in November 2009. And today I realized that we’ve had it in place seven months to the day. While normally having a server or product in place for a short period of time isn’t a cause for celebration, in this case I think it is.
Since November, we’ve added 196 devices to our dedicated Traveler server. Twenty-nine of which are iPads (most of which have been added in the last few weeks). Users can install and connect to Traveler without much assistance (if any). This alone may be reason for an administrator to celebrate!
The support issues we’ve had have been minor (and I really mean minor). We are running Traveler 184.108.40.206 Build 201002131306 on a Windows 2003 Enterprise Server SP2 server. And we rarely have to touch it!
Our user community includes only faculty and staff. And believe me, they have high expectations as to what expect from a mobile device. Many of them are former Blackberry users who switched from a corporate device to a personally owned iPhone, iPad, etc. They may have switched devices, but their need for their mail, calendar, and contacts in real time didn’t change. If you’re in the only in the “consideration” phase regarding Traveler, give it a second thought as it will be a win/win for you and your user community.