G
George Potemkin
Guest
> As I'm watching the index rebuild process it looks like its scanning the entire data area which is ~170GB in size. Index 15 ( PUB.Customer, Name ): de-activated (8831) TMB value is 8, TM value is 8, SG value is 48, packing factor is 100. Area 10: Index scan (Type II) complete. Elapsed time: 0.001 Processing area 8 : (11463) Area 8: Record scan (Type II) complete. Elapsed time: 0.000 IMHO, it's a bug. > is there a faster way to reactivate indexes for tables that are in an area that's freshly truncated? If all indexes of those tables are resided in their own area than you can truncate this area before running idxbuild. Otherwise idxbuild will do a few operations that could be avoided: 1. Sanity checks of the old index blocks (before step 2!); 2. Converting the old index blocks to the free blocks; 3. Rebuilding free chains.
Continue reading...
Continue reading...