Topic:
What does Option #22: Rebuild Interpretation do?

Description:

Solution:
This funtion rebuilds corrupted interpretation files.

The IESX interpretation database could become corrupted (due to disk problems or
system crashes), or accidentally deleted, causing problems in applications that
access these files.  This function attempts to rebuild the existing
interpretation database (horizons, faults, fault traces, and fault contacts)
provided certain key files exist and these key files have not lost their
integrity. During the rebuild operation, you may be prompted to supply horizon
and/or fault names when this information is not recoverable from the original
data files.

The following is a list of critical files with brief descriptions:
db_file_key.* = Master project inventory.  If lost, no recovery is possible.
db_contact_key.* = Fault contact information.
db_ftr_hdr_key.* = Fault trace information.
db_ntrp_key.* = Horizon information.
db_nobj_key.* = Interpretation object information.
db_nfcut_key.* = Fault cut information.

The rebuild operation deletes all fault cuts, fault contacts, fault traces, and
also the *.surf and *.disp files in the project.  The deletion and addition
operation is required because horizons and faults may no longer be valid or may
have been created with new tokens which require a matching of the fault traces
and contacts with newly created horizon or fault tokens. After the rebuild
operation, saved sessions for this project will no longer be vaild since they
contain outdated interpretation tokens. 

1.)  Make sure there is a current backup of the project before starting this
     procedure!
 
2.)  Check disk space! - If the disks are at 100% capacity, possible corruption
     could occur.

3.)  Check permissions! - If permissions are not open for the user to perform
     the function, possible corruption could occur.

4.)  Check to make sure the key files (example: vvol_key.dat, vvol_key.fpb, 
     and vvol_key.idx) that compliment the *.disp, *.surf, and *.vvol files 
     are located on the same DSL.  Otherwise, possible corruption could occur.

5.)  You will be prompted to enter a path for temporary* file storage at the
     initiation of the rebuild process.  The approximate space required is the
     total space currently used by the *.fpb, *.idx, and *.dat files in the
     directory containing the IESX *.idx files to be rebuilt.

6.)  You must start a new session after running this function.

7.)  Large projects could take a long time (30 minutes or more) and should NEVER
     be aborted while running this option.


PROCEDURE:

1.) Option #1 - Initialize access to data area.
    - Enter the project name and password.
    - Select Exploration as Data Area Type.
    
2.) Option #22 - Rebuild Interpretation.
   *Note: You must enter the path for a temporary directory here. The 
    approximate space required is the total space currently use by the 
    *.fpb, *idx, and *.dat files in the directory containing the IESX 
    *.idx files to be rebuilt.

3.) Option #2 - Terminate access to the data area.

4.) Option #99 - Exit IESX_Utilities.



Last Modified on: 23-NOV-98