When the DAOS catalog transitions to the state of "NEEDS RESYNC" a DDM event is fired that will identify the database that first caused the catalog to go into this state. This information can be found in the DDM database or in the log.nsf. 

The following is a list of operations that cause the DAOS catalog to transition to the state of "NEEDS RESYNC": 

• copy a DAOS enabled database into the data directory from the OS
• delete a DAOS enabled database from the OS
• rename a database from the OS
• delete an NLO from the OS (will transition to "NEEDS RESYNC" when the NLO is attempted to be opened.)
• restore a database directly to the data directory
• If you can not determine what action caused the catalog to "NEEDS RESYNC" and it continues to occur, debug code should be enabled. Setting 
• DAOS_LOGGING=c:debugdaos.txt STATE_CHANGE 
• will log all DAOS state change activity. Also enabling DAOS_LOGGING will cause DAOS to output the call stack to the server console that caused the catalog to transition to this state. That should be given to support along with the daos.txt FILE to help troubleshoot the problem. 
• To clear the "NEEDS RESYNC" state run a resync by entering the COMMAND 'tell daosmgr resync'. Note that while the catalog is in this state DAOS will continue to operate normally. HOWEVER deletion of NLO files by the PRUNE task will be postponed until the catalog is in the "SYNCHRONIZED" state again. 

When the DAOS catalog transitions to the state of "NEEDS RESYNC" a DDM event is fired that will identify the database that first caused the catalog to go into this state. This information can be found in the DDM database or in the log.nsf. 

The following is a list of operations that cause the DAOS catalog to transition to the state of "NEEDS RESYNC":