SYMPTOMS
When you are running the Active Directory Management Agent (ADMA) in Delta mode, it is possible that not all of the objects that were created by TAMA in the connector space of the Management Agent (MA) will be processed. The following information is logged in the Zscript.log for the file-based MAs or in the Dslib.log for the ADMA:
01/05/26 21:15:36.125 ERROR 19118: DS_RC_LOST_TRANSACTION
Or, the following message is logged only in the ADMA because of the watermarks that are used to keep track of Delta changes:
01/05/26 21:12:07.218 WARNING: Mismatched watermark
01/05/26 21:12:09.562 WARNING: Possible loss of transactions [Sat May 26
09:22:29 2001 379743 - Sat May 26 13:27:56 2001 78012]
CAUSE
The Db5config file contains a parameter that sets the size of the transaction stack, which is the db5_max_tran_file_size parameter. Setting this parameter controls the maximum size of the transaction stack. When the maximum size is reached, the file is overwritten. If you set the size too small, it is possible that the transaction data will be overwritten, which generates the error message that is noted in the "Symptoms" section of this article.
The following settings are the default settings for the different versions of Microsoft Metadirectory Services (MMS):
MMS 2.1 = 64 MB
MMS 2.2 = 512 MB
MMS 2.2 SP1 = 2 GB
If you upgrade your MMS server, the Db5config file will not be overwritten. You must manually edit the file to set the desired size after upgrading.
Examples of the Db5config File Before and After Upgrade
The following information exists in an upgraded MMS 2.2 SP1 Db5config file:
# 536870912 == 512 MB
db5_max_tran_file_size 536870912
In a new installation of MMS 2.2 SP1 the following setting exists:
# Note that this number cannot be larger than 4294967295
db5_max_tran_file_size 2000000000