Kbase P75127: Adding indexes via batch job resulted in bi file reaching 2GB
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
08/06/2009 |
|
Status: Verified
SYMPTOM(s):
Adding indexes causes the bi file to grow to 2GB.
FACT(s) (Environment):
Progress 9.x
OpenEdge 10.x
All Supported Operating Systems
CHANGE:
Adding indexes.
CAUSE:
Current program to add indexes requires more bi space than allowed for by system administrator
FIX:
The following will fix this issue:
1. Add additional bi extents, or
2. Code to do the work in smaller chunks
If it is not possible to add bi extents nor to re-code the program do the following to add indexes:
1. Create a .df file with the index to be added as INACTIVE.
Example:
ADD INDEX "Agent" ON "mytable"
AREA "Index Area"
INACTIVE
INDEX-FIELD "Agent" ASCENDING
2. Add .df file.
3. Run proutil dbname -C idxfix online selecting number 3 with fix
4. Run proutil dbname -C idxfix off line selecting number 3 with fix
5. Run the offline close in time to the finish of the online run, if not possible, run the online again prior to the offline run.