As a Domino Administrator you might have been asked by your users, “Where is this specific email!?” It has been a long-standing issue with older versions of Domino when an important document goes missing in an application used by multiple users, with no way to identify who/what/when/how a certain document was deletedFear no moreDomino document deletion logging is now a feature that was made available starting from Domino v10. You now have the ability to explain what might happen to the document they are looking for. 

So, how can you implement it? It’s as simple as running compact task on a database, literally! A new compact task option is available to enable logging of data about deleted documents in databases that you specify. Here are the key requirements for such feature. 

  1. Use Domino v10 and above.
  2. Have transaction logging enabled.
  3. Run compact task against the database that you want to monitor 

load compact <database path> -dl on “<comma separated list of items>” 

where <database path> is a specific database or a directory of databases, relative to the data directory, for example, mail or discussion.nsf. 

 <comma separated list of items> is a list of fields to show in the logs to help you identify deleted documents. The fields must be one of these types: Text, Text_List, RFC822_Text, or Time. Suggested fields for mail documents are SubjectSendToFrom, and DeliveredDate. If you have custom fields on a document, you can use them as well. 

The data is logged to a deletion log file called delete.logwhich is located under the server Data directory, IBM_TECHNICAL_SUPPORT folder. When documents are deleted from a database, entries are added to that file. 

When the server is restarted, a new deletion log file is created. Old deletion log files are renamed to delete_<servername>_yyyy_mm_dd@hh_mm_ss.log; for example: delete_Server1\Renovations_2020_01_10@06_28_45.log 

Deleting a document from a database adds an entry to the current deletion log file with the following data. This data is provided in a CSV-compatible format. 

Data in deletion log entry 

More information 

Date and time of the document deletion   
Database from which the document was deleted.  Relative to the data directory 
Replica ID of the database  Helps you find multiple replicas of a database in the log if the database name is not the same on all servers. 
Process that did the deletion  For example: 

  • server 
  • dbmt 
  • replica 
Name of the server or person who deleted the document   
Type of document deletion  Can be: 

  • SOFT — document is in the trash 
  • HARD — Stub delete (for example when the document is deleted from the trash) 
  • RESTORE (document restored after a SOFT delete) 
Class of document deleted  Specified as one of the following hex values: 

  • 0001 (Document – NOTE_CLASS_DATA) 
  • 0002 (About Database Document – NOTE_CLASS_INFO) 
  • 0004 (Form – NOTE_CLASS_FORM) 
UNID  Unique document identifier across replicas 
Items  Up to four field values in a deleted document to help you identify it. Specified when you enable deletion logging. Although you can specify more than four field values, only the first four that are found are shown in the log entry. Each item has three parts: the item name, the length of the item value, and the first 400 characters of the item value. 

 Then if you no longer need to monitor the document deletion on the database, run the following command: load compact <database path> -dl off 

Here’s some things to keep in mind when using this feature. 

  • When entering the compact command, no spaces inside the comma separated list of items.  

load compact mail/admin.nsf -dl on “SendTo,From,DeliveredDate” — Correct 

load compact mail/admin.nsf -dl on “SendTo, From, DeliveredDate”— Incorrect 

  • More than 4 comma separated items can be put in when entering the command. However, only 4 comma separated list of items will be logged in the deletion log file. 

Learn more about Domino Document Deletion Logging here.  

Comment wrap
Further Reading
article-img
Digital Solutions | August 23, 2021
Introducing Domino v12.0.1 and HTMO 3.0.3 Beta Program!
After the successful launch of HCL Domino v12.0 in June 2021, we are approaching the next milestone: We’re happy to announce two new beta programs at once, HCL Domino 12.0.1 and HTMO 3.0.3 have both launched a Beta Program today! You are invited to join the beta program to test our latest release and provide feedback to development teams.   We’re calling on our community to share open, effective, and thoughtful review and testing of our software product. Your input is essential to how we develop our products, and we will continue to listen to you every step along our roadmap.  What you can expect from this first beta of Domino v12.0.1: HCL Notes Client Domino Online Meeting Integration The Notes Client 12.0.1 is providing native integration of online meeting platforms like Zoom, Webex, GoToMeeting, Teams and of course Sametime Meetings. So, from within the Notes calendar users can now more easily schedule online meetings on their preferred platform without having to install a plug-in. Improved Workspace Design with High Resolution Icons The new Notes client is finally allowing to use high resolution icons for your databases, which makes a big difference to the look and feel of your workspace! No need to stick to small and old style 32x32 pixel database icons anymore. We have already updated our standard templates with new icons, will you update yours? Advanced Properties Box You have asked for it, we have delivered: an all-new and resizable document property box: Thanks to Panagenda, the new "advanced properties" box allows to search for field names or values, it also provides the requested ability to copy to clipboard or export to a CSV file: What's new in Notes v12.0.1? https://help.hcltechsw.com/notes/beta/12.0.1/whats_new_01.html HCL Domino Designer We have already provided a 64Bit Notes client (in beta as of now), and based on your request are now providing a 64Bit Domino Designer client. Also, Domino Designer v12.0.1 provides the ability to include high quality icons for rendering and enables developers to optimize the database full...
article-img
Digital Solutions | August 18, 2021
New Tech Updates for HCL Domino, Notes, Traveler, Verse, and Connections
While you may have been on a summer vacation, we at HCL have been busy improving our products! Here is a small overview of what happened in the last couple of weeks and what you can expect soon from your most favorite collaboration platform.  Group 3 Language Translations for Notes and Domino 11.0.1  Good news for many of our customers: HCL Notes 11.0.1 is now available in more languages.   You asked for it (DOMINO-I-831 and NTS-I-842) - In addition to the 16 languages the Notes client was already providing, we are delivering the following language translations:  Danish  Finnish  Norwegian Catalan Hebrew Hungarian Slovenian Thai Turkish  Install kits for the HCL Notes Standard and Basic Client V11.0.1 in those languages can be found at our License and Download Portal under the Notes/Domino version 11.0.1.   Of course, we are also providing the Multilingual User Interface (MUI) kit for those languages, as well as the Install Shield Tuner files to customize your installation.  Group 3 language translations for the Notes Client v12 are being worked on. Level up for our Domino Rest API  In June, we started the beta program for our new Domino Rest API. Now in August, it’s time for the next iteration. Shifting gears to Beta 2 will introduce several improvements customers were asking for:  ODATA support was added for reading/writing from/to Domino, which is especially of interest for e.g., Salesforce customers who want to store data in Domino A new Domino server add-in task is provided to start/stop/reload the Domino Rest APIs and show its status from the Domino server console An installer is now allowing to install the Domino Rest APIs on a Domino Linux server. Previously only a docker container was provided  For more details, about the new features please refer to the changelog of this project.  Please note: The Domino Rest APIs are still in beta — the first eGA release is scheduled to be shipping with Domino v12.0.1 later this year. Customers interested in joining the beta program can find the required files available for download at our License and Download Portal.  HCL Traveler 12.0 updated with Fix Pack 1  Fix Pack 1 for...
article-img
Digital Solutions | June 11, 2021
Announcing the Domino REST API Beta Program  
Today, we’re announcing the start of the beta program for our new Domino REST API, formerly known as “Project Keep.” This is the latest addition to our ongoing Domino Early Access Program. The Domino REST API will introduce hundreds of new APIs that aperture to information on Domino — further extending access to your Domino data. It’s a modern take on the REST API for opening Domino access to a world of standards — and API-first developers. What is it?   Domino REST API is a new feature that runs alongside the server and allows you to expose your Domino data in the form of standardized Open-API-based methods securely and easily. Using a browser-based admin UI, application owners can define which data will be made available for view or update on a REST API. It extends the Domino principles of reader/author document access definitions into the world of Internet protocols.  It also includes Swagger UI which allows the visualization and interaction with APIs without having any of the actual implementation logic in place. The APIs are automatically generated from an OpenAPI (formerly Swagger) specification with visual documentation, making it easier to later implement the back-end code.  What is special about the new Domino REST APIs?  Secure by default, with fine granular controls per form, field and user basis  Implements latest open standards  HTTP/2-ready, for server-to-server or client-to-server communication API-first design with full interactive documentation  Low barrier to entry as it runs on a Domino server and/or your Notes client  Admin UI and Postman samples included  State-of-the-art JWT access token integrated with your existing IdP infrastructure What can be accessed via the Domino REST APIs? You can access content like views, documents, and fields, as well as database design, agents, and ACL settings. And, of course, featuring DQL queries to quickly access the data you are looking for.  Built-in declarative security ensures the API will only allow access to fields the caller is authorized to see or update. This can effectively prevent computed fields to be overwritten and limits participants in a workflow to update their fields only.   How to participate   The Domino REST API is now available as a...
Close