CacheTemp uses global buffers to keep it in memory. If the database becomes too large for this then cache' will spit it out and change modes so that it runs like any other disk-resident cached database. Perhaps this is causing those messages, as I assume Cache' must suspend writes for a while to reorganise itself. Another reason may be a write daemon panic where it can't keep up with writes to to the database, so all writes are suspended until it can catch up. Only a guess without further info.
Colin "Sam Jones" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED] > Maybe the 'updated are suspended' message was lost because > the disk became full? Is there a max size specified for cachetemp? > > "Peter Cooper" <[EMAIL PROTECTED]> wrote in message > news:[EMAIL PROTECTED] > > John > > > > Broadly Cache uses ^Cache Temp for scratch files - ^CacheTemp is not > > journalled so it is quicker > > > > Almost everything uses ^CacheTemp > > Compilation of Cache classes > > SQL temp tables for creating a sort order > > etc etc > > > > What is meant to happen is that the thingy using CacheTemp should > > clean up when it's done > > if this is not happening then something is going awry elsewhere > > > > By default there is no Max size set by a Cache install - Control panel > > shows 32Tb on my machine - unless you have changed this > > > > Maybe someone else can shed light on the > > DATABASE UPDATES HAVE RESUMED causes > > > > Peter > > > > On Tue, 10 Aug 2004 10:42:52 +0100, John Warren > > <[EMAIL PROTECTED]> wrote: > > > > >What is Cache Temp used for and what happens when it becomes full. We > > >keep getting *** DATABASE UPDATES HAVE RESUMED *** messages in the > > >console.log file, the only thing we can track this down to is that cache > > >temp is full. > > > > > > > > >Thanks in advance > > > > > >John > > > >
