Questions on 'Time to Copy', 'Time to Post' and 'Time to Reorg' (4328529)

Q1. Does 'Time to Copy' include the time taken to create posting index?

Q2. Does 'Time to Post' include the time taken for the switch (ie. end of the switch)?

Q3. 'Time to Copy' and 'Time to Post' do not usually add up to 'Time to Reorg'. Is the difference the time taken for the switch?

A1. No, 'Time to Copy' is the time from QUEST_EXEC.BEGIN_COPY  to QUEST_EXEC.END_COPY. The END_COPY is always put before the creation of the Posting Index.

A2. No, switch time will be a very small portion of the difference; more time will be consumed by creating the Posting Index (this occurs after the Copy and before the Posting).

A3. No, a big factor will be time to create the posting index which is not included in either of those times. LiveReorg is a multi-threaded application, the posting runs in a separate thread. Time to Post is "wall clock" or elapsed time from the time the posting started to the time it is completed just before the switch. In the current versions of Space Manager for Oracle with LiveReorg  posting is usually suspended while creating indexes, so  "Time to Post" is not the amount of time spent posting.

For more information  on timing details,  please look at the Reorg History Report which provides much richer details.  Select a specific table, right click on it and choose Details  then go to the Timing tab. Note that because the timings are collected using different mechanisms, there will be minor differences between the timings reported in Reorg History and LiveReorg Detail.