I have enabled DAOS and compacted the mailfiles using compact -c -daos on.After the compact has successfully finished, I saw that DAOS state was READ/WRITE on all files.
Today some (3 of 400) databases have a DAOS state of READONLY.
Can anyone explain what causes the change? What are the effects when the state is READONLY?
Subject: DAOS read only
I have enabled DAOS and compacted the mailfiles using compact -c -daos on.
After the compact has successfully finished, I saw that DAOS state was READ/WRITE on all files.
Today some (3 of 400) databases have a DAOS state of READONLY.
Can anyone explain what causes the change? What are the effects when the state is READONLY?
A database can have one of three DAOS states
Disabled - the database does not have any objects in DAOS and it will not store objects in DAOS
Read/Write - the database is DAOS enabled, any qualifying new objects will go into DAOS
Read Only - the database has DAOS objects and those will continue to work fine, but new objects will be written into the NSF and not DAOS because the database does not meet the criteria for using DAOS (we need to figure out what would cause this )
A database can only participate in DAOS if these criteria are met
the system is transaction logged
DAOS is enables at the server level
I assume you meet these two criteria, you can verify this by issuing a
SHOW SERVER console command
you should see
DAOS: Enabled
the individual database is transaction logged
the individual database has the DAOS property set
the database is ODS 51
to check this, run a
SHOW DIR directory_or_file_name
for example
sh dir zzz
DbName Version Log DAOS —Modified Time----
C:\Lotus\Domino\data\zzz\zmarx.nsf V8:51 Yes Yes 03/18/2009 07:56:24 AM
C:\Lotus\Domino\data\zzz\showard.nsf V8:51 Yes No 03/12/2009 07:30:15 AM
C:\Lotus\Domino\data\zzz\pcastor.nsf V8:51 No No 03/12/2009 07:29:54 AM
C:\Lotus\Domino\data\zzz\mhoward.nsf V8:51 Yes No 03/12/2009 07:30:12 AM
C:\Lotus\Domino\data\zzz\lfine.nsf V8:51 Yes No 03/12/2009 07:30:08 AM
C:\Lotus\Domino\data\zzz\jpollax.nsf V8:51 No No 03/12/2009 07:29:51 AM
C:\Lotus\Domino\data\zzz\hmarx.nsf V8:51 Yes No 03/12/2009 07:30:05 AM
C:\Lotus\Domino\data\zzz\groucho.nsf V8:51 Yes Yes 03/18/2009 07:55:49 AM
C:\Lotus\Domino\data\zzz\gmarx.nsf V8:51 Yes Yes 03/18/2009 07:56:02 AM
C:\Lotus\Domino\data\zzz\cmarx.nsf V8:51 Yes Yes 03/18/2009 07:56:10 AM
C:\Lotus\Domino\data\zzz\choward.nsf V8:51 Yes No 03/12/2009 07:29:08 AM
C:\Lotus\Domino\data\zzz\cderita.nsf V8:51 Yes No 03/12/2009 07:29:57 AM
Total files: 12
For the files in question, verify that ODS version is V8:51, Logging is Yes and DAOS is Yes.
Are any of these indicators wrong for your Read/Write databases ??? (if so, then the next step is to determine how/why)
Subject: Since they were at one point READ/WRITE
My guess would be someone/something changed the database property to disable DAOS… This can be done manually… I thought we added code to prevent Design Replace from changing the existing DAOS property on the database but will check with DAOSTeam to make sure still holds true…
Subject: Points 1- 5 = OK
@Gary: DAOS is enabled on the server as well as transactional logging. ODS is V8:51 on all databases.About the side effect of not having enabled transactional loggin on the database level, I’ve wrote an article in imy blog DAOS: Transaction Protocol Trap | eknori.de
TL is enabled on the database.
@John: The design task is not running. No 3rd party products installed on the server ( like anti virus or so )
I guess that the state might change when another process uses the database ( fixup, compact )
Subject: what does SHOW DIR display for these db’s
are they marked as DAOS enabled ?
We need to determine if the “system” is thinking they are disabled for some reason or if the property got improperly changed (say replicating through an older server ).
???
Subject: unfortunately …
I had reenabled DAOS on these databases before I read your post, so all files are now read/write …I’ll wait for the next state change and give feedback here.