Start/notes.ini Parameters/DAOSCatalogState

DAOSCatalogState

DAOSCatalogState reflects the current state of the DAOS catalog (daoscat.nsf) as a number in notes.ini. The value is written by the server itself – administrative changes are not made by editing the file directly, but via the console (tell daosmgr resync).

Profile

Parameter
DAOSCatalogState
Component
Server
Category
DAOS
Available since
Domino 8.5; currently documented in HCL Domino 9.0.x–14.5.1
Value format
Integer 0, 1, or 2 (set by the server)
Manually editable
No – do not change in notes.ini
GUI equivalent
Console command tell daosmgr status

Description

The DAOS catalog is the central index database of the Domino Attachment and Object Service. As long as the catalog is in the Synchronized state, DAOS can reliably create, reference, and delete NLO files.
DAOSCatalogState reflects exactly this state:
  • 0 – Down / Disabled: DAOS is disabled or the catalog is not initialized. Typical value on a server freshly set up without DAOS.
  • 1 – Needs Resync: The catalog must be synchronized before it can work reliably again. Occurs e.g. after abrupt server stops, defective backups, or hardware errors.
  • 2 – Synchronized: Normal operation. DAOS works consistently.

Status check in daily operation

For operational checks, DAOSCatalogState in notes.ini is less suitable than the console commands:
  • tell daosmgr status – shows the state and useful statistics.
  • show stat DAOS – detailed statistics on repository, pruning, resync.

When the status „Needs Resync“ occurs

According to HCL KB0031850 „Troubleshooting the DAOS Catalog »Needs Resync« state“, the typical steps are:
  1. Take a backup of the affected server/volume.
  1. tell daosmgr resync – start a soft synchronization.
  1. If that is not enough: tell daosmgr resync force – forced synchronization.
  1. Only if even that does not help, further diagnosis (tell daosmgr dbdelete, KB0126234).
After a successful resync, DAOSCatalogState changes to 2 on its own.

Examples

Freshly configured DAOS server, after the first tell daosmgr resync:
DAOSEnable=1
DAOSBasePath=D:\DAOS
DAOSMinObjSize=4096
DAOSDeferredDeleteInterval=30
DAOSCatalogState=2
Server in recovery state (before manual resync):
DAOSEnable=1
DAOSCatalogState=1

Notes

  • Never set manually – a manual DAOSCatalogState=2 does not correct any real inconsistencies, but can mask them and cause later data corruption.
  • Do not delete daoscat.nsf – KB0079120 explicitly states that deleting daoscat.nsf and daos.cfg to fix resync problems resets the DAOS calculations and can heavily slow down the deletion of NLO files.
  • Monitoring – well suited to check via a monitoring script whether a server is permanently in state 2; anything else is an alarm.
  • Companion parameters – DAOSEnable, DAOSBasePath, DAOSMinObjSize, DAOSDeferredDeleteInterval, DAOS_ENCRYPT_NLO, DAOS_LOAD.

Sources (HCL Product Documentation)