The OpenEdge Hive

The last project I was doing for this company was database reorganization, to remove the unwanted tables/extents/areas . The task was to get rid of the areas and free up the SAN space. First I went through the process the analysis of data see which table in which area; which way I should should move to make the whole thing more effective; after that, it is the process of testing which methods I should use to move the tables to different areas, table move or dump&load. Table move is straight forward, move both data and index in one command, but the test show that the multi-thread table move can result in index corruption. I was able to duplicate this for Progress in a large scale environment. I am not sure what Progress is doing with this though.

After the move of the table and it's time to truncate the areas, get rid of the extents. You will have to get rid of all the tables before you can successfully remove the entire area.
1. truncate the area, both data and index
2. generate the df file for remove the tables unless you choose to remove them from dictionary one by one.
3. activate index, because they are de-activated in truncating. You can try "activate by area" option in idxbuild, but I found that this option doesn't work all the time. It doesn't show all the indices. So the best sure way is to generate the list of the indices from a 4GL programs, then feed that list to the idxbuild utility.
4. apply the schema from step 2
5. remove the extents of the area.