Index seems to be stuck trying to update

Post Reply
barry.marcus
Posts: 288
Joined: Thu Nov 16, 2006 1:05 pm

Index seems to be stuck trying to update

Post by barry.marcus »

We loaded about 80,000 rows of data into one of our tables the day before yesterday. Each row contains the content of a patent, so this is a lot of data. There are about 20 inverted metamorph indexes on the table. Though it took a while, all but two of those indexes seem now to be up to date. However, the two indexes involving the biggest column in the table (that is, the column that contains the largest amount of data) seem to be stuck in some kind of endless process. The .BTR file for them has the date/time stamp from the day of the data "load", but the remaining files for the index are dated from the last time we updated the indexes, which was about a year ago. Moreover, there are a number of temporary files (T04168a.btr, T04168a.data, T04168a.PID, etc.) that seem to get modified often (though they have very little content) AND there is an instance of monitor.exe that seems to be grinding away at a furious pace, consuming a lot of CPU cycles and memory. This has been going on for about 36 hours, but so far we've left it alone thinking that it might be normal. But I'm starting to think that it might not be!

My question is Will killing monitor.exe and/or all other Texis processes, so that we can simply drop and recreate these two indexes do any harm to the DATA ITSELF. It'll take quite a few hours to rebuild them from nothing, but it certainly won't take 36 and counting!

Thanks
User avatar
mark
Site Admin
Posts: 5513
Joined: Tue Apr 25, 2000 6:56 pm

Index seems to be stuck trying to update

Post by mark »

That sounds like chkind is working to update the indices. Not sure why it would take extra long though. Perhaps check monitor.log to see if there are any complaints. Also make sure the disk with the index has enough space for 2 complete copies of the index.

Stopping an index process will not hurt data. The index might be a mess afterwards. Just drop it.

With your batch load process you probably want to turn off chkind in texis.cnf, or texis.ini in texis v6, then update the indices manually after the load.
Post Reply