When are S*.dtf Files at the server exactly created?

Hi there,

I need an answer to : When will S*.dtf - files (not idb*.dtf) at server exactly created.

We try to set up a monitoring to get an alarm, when the temp Dir starts to grow.

Therefor we should first know, what problem (corrupt view, different quota settings on replicas, replication failures, …) causes the creation of these files.

Does anybody know that exactly ? Is there any documentation available. I didn’t find an answer in the forum yet.

Thanks in advance.

Peter

History to my question:

our temp Dir at our Domino server was growing up to 20 GB with 200.000 Files mostly the S*.dtf files.

We found a mail application in the monitoring that throw the following failure “Unable to write to database because database would exceed its disk quota”. We had 3 replicas on different servers, two of them with quotas, another one without.

We dropped the application and the s*.dtf files were removed, now everything works fine, but HOW LONG ???

we have troubles with the temporary update Tesk Files S*.dtf.

Subject: When are S*.dtf Files at the server exactly created ?

DTF files are temporary files that are created by Notes in a temporary directory specified by the system’s environment variable. The format is S0-S9 or IDB, followed by a unique five-digit number. These files are normally purged from the system automatically. Notes places these files in the working directory if there is no TEMP or TMP directory specified. Files placed in the working directory are not purged.

Every time the Update task runs it creates view files in the Data directory that start with the letter “S” and have a DTF extension (these files can also be created in the NOTES.INI-specified View_Rebuild_Dir directory). When the Update task ends, all the files should be purged automatically. If the files are not removed, it is likely that the Update task never ended (the server crashed while Update was being run because the server was running out of disk space, for example).

TMP files are generated by mail debuggers in the Notes.INI, for example, SaveImportErrors, SaveExportErrors.

To remove the files, first display them by typing the following:

  • dsplnk '/notes/data/.dtf’ and dsplnk '/notes/data/.tmp

and make sure that all the files with that extension are displayed. Then remove the files by typing the following:

  • RMVLNK '/NOTES/DATA/.DTF , and RMVLNK '/NOTES/DATA/.TMP.

Important Note: It is preferable to stop the Domino Server before removing the files. Otherwise, it may cause database corruption and other unexpected results.

Subject: RE: When are S*.dtf Files at the server exactly created ?

Thanks a lot for your response,

I found this technote already before I posted the problem to the forum.

I do understand, that the update task is creating and deleting this temp s*.dtf files.

I now have to know, all events, which triggers the update task: modifying documents in a database, replication (?), … where do I find a help ? Why did our update task looping because of a database with Quota Settings ?

It seems, that this problem can sometimes be caused by a corrupt document, or by a corrupt view index, but how does come Quotas into play ? - Does anybody has a idea, how to provide precaution, that means how to monitor it ?

Peter

Subject: RE: When are S*.dtf Files at the server exactly created ?

Are these two command dsplnk ‘/notesdata/.dtf’ and rmvlnk '/notesdata/.dtf’ domino console commands and can be typed in within the domino console after stopping the domino service as mentioned in previous answer?