T
Tim Kuehn
Guest
11.6.3 Linux I have a program that is accumulating GB of data from various database tables. The target Db has a data area, an index area, and the usual schema area. I need to reset the db before starting my process, and I use "truncate area" to clear the data tables. "Truncate area" disables the indexes for all the tables in the truncated area, so I'm doing a full index rebuild to reactivate them. As I'm watching the index rebuild process it looks like its scanning the entire data area which is ~170GB in size. Needless to say this takes a fair amount of time for a set of tables that're empty. This leads me to a couple of questions: why is it scanning the entire area of a freshly truncated area instead of checking each table's data? is there a faster way to reactivate indexes for tables that are in an area that's freshly truncated?
Continue reading...
Continue reading...