Kbase P152078: How to determine how long an idxbuild takes with each area using the database log file in Release 10
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
22/10/2009 |
|
Status: Unverified
GOAL:
How to determine how long an idxbuild takes with each area using the database log file in Release 10.1x.
GOAL:
How long individual areas are taking to do an index rebuild from looking at the log in Release 10.1x.
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
FIX:
Fore releases 10.1C and newer, when doing the complete database in a single operation, if the amount of time taken does not have to be real exacting. just look for the (14536) and (11483) messages in the database log file for each area.
Subtracting the (start) time of the (14536) message from it's associated (11483) message (which is the end time) will give the Rebuild/Sort time for the indices in the associated area.
Note: in Releases 10.1A/B the start message appears without a message number so the search would have to be for "start for the area" rather than a message number :
(-----) 1 threads start for the area
If more accurate times are needed it becomes much more involved as there are 3 steps to the index build.
Step 1: All Indexes are cleared or deactivated.
Step 2: All indexes entries for every data record are rebuilt and indexes is sorted.
Step 3: All Indexes are Activated.
Looking at the log files it is not possible to get an exact time due to the way the 3 steps are reported.
Step 1 does have a begin time for the current index being deactivated. It's end time is the begin time for the following index or process. However, this process does not report the area in the log file so you either have to know this or look the area name up in .df file based on the index name, in order to know which area the deactivated and activate times are to be associated with.
Step 2 Rebuilding / Sorting process:
The Rebuilding / Sorting process for each area starts with a (14536) message and ends with a (11483) message. The 11483 message will also tell you which area it is for. Subtracting the (start) time of the (14536) message from it's associated (11483) message (which is the end time) will give the Rebuild/Sort time for the indices in the associated area.
Step 3 Activation time:
Is written to the log file in the same manor as the Deactivation of the index. The area association for this step is the same as for Step 1.
The deactivation and Activation processes are relatively short compared to the Rebuild and Sort times. You might want to just look at the over all time for these two operations add them together and divide by the number of indexes for a rough estimate of time for each index, then add that amount of time for each index that was rebuilt in each area in Step 2.