--- turnleftjohn <[EMAIL PROTECTED]> wrote: > improved dramatically. So I attempted the creation of the index off hours on > the production system, and after 4 hours no index. I can't detect any > activity at all. The journal file and the .db file just sit at the same size > for 4 hours. Why is this failing? It seems like it is just sitting there > doing nothing. When I created the test index, I noticed the journal file > changing and the .db file changing during the 2.5 hours to create. On the > production .db file, nothing is happening. I have all associated processes > killed that ineract with the db file, so I know it is not locked.
Run lsof on the production database file just in case there is some contention. (You never know). I assume that the copied "test" database was indexed immediately after its creation. If this was the case then the entire file may have been in the OS cache resulting in very quick indexing. Try running "wc prod.db" or "cat prod.db >/dev/null" and then creating the indexes on prod.db to see what happens. ____________________________________________________________________________________ 8:00? 8:25? 8:40? Find a flick in no time with the Yahoo! Search movie showtime shortcut. http://tools.search.yahoo.com/shortcuts/#news ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
