#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

Upgrade DAOSCAT.NSF ODS without re-creating the database

The only way to upgrade the daoscat.nsf ODS is to remove and re-create this database. Unfortunatly, you will lose the 0 referenced NLO files ( when all database reference for a NLO are gone ).

When you recreate the daoscat.nsf, it will get a list of all NLO's and all references to NLO's. This will end up with lots of orphaned NLO's. The daos rebuild action will set the timestamp of those orphaned nlo's to the current time and date.

If you have set the "Defer Object Deletion" to 180 days because that will meet our SLA. When we set this to 180 days, we never have to restore NLO's from the backup. But when you re-create the daoscat.nsf, it will set the counter back to 0 for all 0-referenced NLO's again. Just after 180 days they are removed what will take a lot of diskspace.

Please let us upgrade the daoscat.nsf without rebuilding it.

  • Guest
  • Feb 26 2021
  • Needs Clarification
  • Attach files
  • Guest commented
    19 Apr, 2022 09:36am

    offline compact does not work for the daoscat.nsf, since compact opens the DaosMgr and opens daoscat.nsf.

    The only way I found was stopping Domino, copy daoscat.nsf to another file say daoscat2.nsf, offline compact daoscat2.nsf, and then switch the files around (i.e. rename daoscat.nsf to daoscatold.nsf, and rename daoscat2.nsf to daoscat.nsf), and only then starting Domino.

    But this feels gnarly and unsafe, by being non-automated and thus error-prone.

    So please consider adding a special case for the daoscat.nsf file to solve this in an automated and supported manner.

  • Admin
    Thomas Hampel commented
    23 Jan, 2022 11:24am

    Did you try compacting the database while the server is down ?

  • Guest commented
    23 Apr, 2021 07:41am

    Interesting observation

  • Guest commented
    26 Feb, 2021 02:24pm

    With upgrading, i mean upgrading ODS :-)