Option 1: Enable largefiles and re-run the idxbuild operation:
- If an Enterprise database license is installed and
- If the last extent of the index area is variable (not fixed) and
- If there are sufficient disk space available to extend the variable extent indexes are being built in
Option 2: Clear the flag in the master block with an incomplete by successful index build.
- A valid and verified database backup needs to be taken before attempting any repair routine. If an index rebuild does not complete for any reason, the database is inaccessible by any means until the idxbuild completes. If you cannot complete an index rebuild against your database, you will need to resort to the backup.
- Create a dbname.xb text file in the directory where the dbname.db file exists
- Instead of listing all the original indexes that were being rebuilt when the idxbuild failed initially, only add information regarding one of the smaller indexes to the xb file.
- Re-run idxbuild is from the same directory/folder as the .xb file, when the dbname.xb file is found, only that one small index will be rebuilt. This will reset the failed idxbuild flag in the master block of the database and delete the xb file.
- The prostrct add command can then be used to add extents to the area that reached capacity which caused the idxbuild to terminate earlier.
- Finally rebuild all indexes for the database that were deactivated on earlier failed idxbuild attempts through the 'some', 'area', 'table or 'schema' IDXBUILD Options.
For the format of the dbname.xb file, refer to Article
An idxbuild SOME builds all indexes after a previous index rebuild has terminated or been cancelled.