This is expected behaviour, all IDXBUILD/IDXCHECK command line Options are exclusive:
Additional IDXCHECK/IDXBUILD command line Options were added as a new feature to compensate the only other command line option "all", without having to first navigate through the IDXBUILD table/index pages to run a restricted IDXBUILD
When restricted IDXBUILD commandline options are combined, the
first qualifier specified on the command line is used and any other scope qualifiers are ignored.
- OpenEdge 10.0B added additional IDXCHECK/IDXBUILD command line Options: "table", "area", "schema"
- OpenEdge 10.1A, added further IDXCHECK/IDXBUILD command line Options: "activeindexes", "inactiveindexes"
All 5 of these commandline Options are stand alone options. None of these were designed to work in conjunction with each other. In other words, an index build cannot be run for all 'inactive indexes' AND all indexes in an area for example.
Other methods to reactivate an inactive index:
1. Use
IDXACTIVATE, which has the advantage of being able to run online and does not require after-imaging to be disabled before building indexes.
$ proutil dbname -C idxactivate
- IDXACTIVATE can be used fully online, but will start from scratch each time to build all index keys and activate the index. It does not take into consideration if the keys were already built by any other tool
- The Primary index does not have to be active, as long as another active index is referenced with the "useindex" option. For further information refer to Article: What is idxactivate?
2. Use either IDXBUILD or IDXFIX (offline) to activate indexes
3. Activate indexes marked as
inactive using a combination of Online and Offline methods:
- IDXFIX (Option 3) online for the inactive index(es). This will not activate the index, it will pre-build the key entries
- IDXBUILD (offline) will activate the index (much) faster with less downtime
It was determined that the Progress Product is functioning as designed.
An enhancement to the product can be requested through the Progress Community via an Ideas submission. Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea.
For detailed information on how to submit an Idea, please refer to Article: How to submit an enhancement request for a Progress product?