I am using active logging and have plenty of disk space available for
archive logs to build up. However, when I build an index on a billion
row table I wind up running out of transaction log space when I have 3
active logs of 4096 4k pages. (*or about 3 times 16 meg worth of active
logs)

1. How do I estimate the amount of transaction log space I might need
for an index on "N" rows, by "X" columns of "Y" bytes width?
2. I do not see an unrecoverable option for building the indexes except
when doing the index build with the "LOAD" utility.
3. Technical documentation references you might recommend on the topic
of index building, and active transaction logs.
4. What is actually generating the transaction activity? Is it inserts
to the system tables about the index or is it data related to the
physical index itself?

Thank you in advance.

Kevin

DB2 & UDB email list listserv db2-l LazyDBA home page