When performing day-to-day administrative tasks, you may need to retrieve a list of all the databases on a particular Lotus Domino server. For example, you may want to find which databases you don't have access to, or the databases that aren't included in the directory catalog. Perhaps you want to identify duplicate templates on the server.
You can use the Lotus Notes Administrator client to view the list of all databases on a server, but it only offers limited ways of sorting and filtering the list and doesn't always provide all the information you need about each database. You could also use the Database Catalog, but not all databases are necessarily included in it.
This agent will quickly and easily retrieve a list of all databases on a Domino server, as well as plenty of useful information about each database.
The first step is to download the ServerScan.nsf database. After you've downloaded the database, you'll need to edit two values in the Scan server agent.
Open the database, then go to View -> Agents (Figure 1).
Next, open the Scan server agent (Figure 2).
In the Initialize section of the agent, you'll see two constants defined, SERVERNAME and FILENAME. You'll need to change these values to match your environment (Figure 3).
SERVERNAME is the name of the Domino server that you want to scan; for example "DevServer1." Leave this blank if you'd like to scan your local computer.
FILENAME is the name of the .csv file where the results of the scan will be recorded. In this example, the results will be written to C:\temp\ServerScan.csv. You can change this to any filename you like, but I recommend keeping the file extension as .csv.
Save and close the agent after you've changed these two values. You're now ready to run the agent from the Actions menu in Lotus Notes (Figure 4).
As the agent runs, a status bar will show a count of the databases being scanned (Figure 5).
Once the agent has finished scanning the databases, the results will be stored in the file you specified in FILENAME above. You can now open the file and analyze the scan results. I prefer to use a spreadsheet for this (Figure 6).
Each row in my spreadsheet represents one database on the server that was scanned. There are a number of different attributes that are recorded for each database.
Note: Some of these database attributes can only be retrieved if the database could be opened. The scan will identify databases that you don't have access to. The scan will only record a subset of the attributes for these databases (Table 1).
Table 1. Explaining the various database attributes
|Database Attribute||Description||Requires database to be open?|
You can now quickly sort, filter and analyze the data in your spreadsheet software. Some of the ways you might want to use this data include:
- Finding all databases that couldn't be opened. This indicates that you don't have access to the database and may indicate some ACL issues with the database.
- Identifying duplicate templates. Sort by Template name to identify any duplicate databases that may claim to be the same template.
- Locating old databases that haven't been used in a long time. Sort by date last modified to identify databases that may need to be removed or archived.
- Identifying databases not listed in the directory catalog but should be. You can accomplish this by sorting by In directory catalog.
I've suggested a few ways that you can use this data, but I'm sure you'll be able to find more. The Scan server agent can easily be extended to include more database attributes by altering the LotusScript code (shown below).
Note: For those interested, the LotusScript source code for the agent is shown below.
Do you have comments on this tip? Let us know.
|ABOUT THE AUTHOR:|
Ethann Castell is a senior consultant with Caliton Innovations. He has extensive experience across all aspects of Lotus Notes and Domino dating back to 1995. Caliton Innovations develops leading-edge Lotus Notes tools, and provide boutique consulting services. You can contact Caliton Innovations through their Web site at www.Caliton.com.
This was first published in December 2009