• Defrag databases stay locked until end of DominoDefrag process

    By vincent valentin 1 decade ago

    I ued DominoDefrag since 2.2 and it is a great tool.

    Recently I upgrade it to 3.3 and found out that I have problem doing admin task on database time to time (compact, delete, ...) Domino always stay it is locked. After investigation I found out that DominoDefrag 3.3 keep a lock on all processed database until it ended.

    In was not the case in prévious version.

    Is it a bug ?

    Thanks for help

    • Can you please give a specific example

      By Andrew Luder 1 decade ago

      Hi Vincent,

      I haven't experienced what your talking about. The only thing I can think of is your using Dominodefrag to do a compact and trying to use another task like updall or fixup on a database at the same time.  

      Can you please give a specific  example

      Regards

      • Re: Defrag databases stay locked until end of DominoDefrag process

        By vincent valentin 1 decade ago

        Hi Andrew,

        In fact I used for Example DominoDefrag to process on all my cluster mailbox (arround 3000). If DominoDefrag from on all databases and have process on asmith.nsf and is currently doing zcheng.nsf and can't delete for example. First I think is was locked by user or other Domino standard process but using OFview (http://www.nirsoft.net/utils/opened_files_view.html) I can see tha all databases that DominoDefrag already process are locked by it. When finished it is unlock.

        I used DominoDefrag on a 8.5.1FP5 32bitsDomino server on Windows 2003 SP2 32bits.

        Thanks for help

        Vincent

        • Can you please remove all your INI settings and try again

          By Andrew Luder 1 decade ago

          Hi Vincent,

          I built a Windows 2003 SP2 Domino 851 fp5 32 bit server over the weekend and on my first test had no DominoDefrag Notes INI settings and could not reproduce your problem using the command show opendatabases at the Domino console or using the tool you referred me to below. Can you please remove all your DominoDefrag INI settings,try again and tell me how you go. If you get my result then we'll test each of your DominoDefrag INI settings to see if we can reproduce your open databases issue.

           

          • DominoDefrag_PerformanceCheck=1

            By vincent valentin 1 decade ago

            Hi Andrew,

            I checked INI setting as you required and it seems that the problem occured when DominoDefrag_PerformanceCheck=1

            You introduced this setting in version 2.4.2 of DominoDefrag. I upgraded from 2.3 to 3.3 and I should copy/past that setting from your admin release example. Reading again the aim of that setting I am not sure of the need to set it to 1. What you recommend for this setting ?

            Do you reproduce the problem with setting up to 1 ?

            Regards

            Vincent VALENTIN

            • Found database close bug in DominoDefrag_PerformaneCheck functionality

              By Andrew Luder 1 decade ago

              Hi Vincent,

              found database close bug in DominoDefrag_PerformanceCheck functionality. As this setting is just for performance reporting you can turn it off for now with setting DominoDefrag_PerformanceCheck=0

              Thanks for helping with this. Will fix with 3.4 version to be released in October in conjunction with 853.

              Andrew