#dominoforever | Product Ideas Portal

 

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Show Deletion Logging Status of Database

How can I find out, whether a database has deletion logging activated?

Please make it visible in one or all ways:

  • sh database db.nsf -> DL Status
  • start delete.log with a list of logged databases
  • list logged databases with show server
  • ...

If I missed an already existent way, please add to the documentation.

Thank you

  • Guest
  • Dec 31 2018
  • Needs review
  • Attach files
  • Guest commented
    14 Jan, 2019 08:19am

    @Daniel Nashed: I did not have the time yet to test either nshdbcat with DL nor nshdellog, but I am aware of these. Thanks for your hard and good work. I like the idea of those. I was so free to link nshdellog on our blog.

    Also agree with your comments concerning LotusScript and Admin Client.

  • Guest commented
    2 Jan, 2019 07:09am

    We need to be able to show the status and also set the status via Lotus Script etc.
    I wrote a tool (C-API) that can query and set the status and also my nshdbcat (extended database catalog) shows it. But I would wish there would be a way to see it in:

    - admin client

    - database properties

    - from Lotus Script

    Also setting it right now is only possible via compact task.
    Having it controllable via admin client would be helpful!

    By the way, I have a free tool nshdellog database which allows you to annotate and manage delete.log files.

    ( Daniel Nashed (/ blog@nashcom.de )