Topic:
Project Upgrade Preparation: IESX 10.x to GeoFrame 3.1.x 

Description:
Brief guide to upgrading from IESX 10.x to GeoFrame 3.1.x.

Solution:
ENVIRONMENTAL CONCERNS

1.)  Both the IESX 10px and GeoFrame 3.x software must be loaded.
 
2.)  To upgrade IESX 10px to GeoFrame, IESX and GeoFrame must use the same
     $IESX_CONFIG

     To check this:
     in an IESX xterm launched from GeoNet type:   echo $IESX_CONFIG

     in a GeoFrame xterm launched from GeoNet type:   echo $IESX_CONFIG

If they are different and no projects currently exist in GeoFrame :

    edit the following GeoFrame file:

    $GF_HOME/iesx/iesx_setup_site.csh

     Look for the following line and edit the config path.
     =>  setenv $IESX_CONFIG /home/gqs/iesx_config/
     to the complete pathname received from $IESX_CONFIG in the IESX xterm.


If they are different and projects do currently exist in GeoFrame,consult 

    'How to upgrade IESX 10.x to GeoFrame with different $IESX_CONFIG files'


PROJECT CONCERNS

Preparation

1.)  The IESX project must be at the 10.1 or above release level and the
     project preparation should be performed at this level.
 
2.)  Once a project is upgraded to GeoFrame 3.x it is no longer available in
     IESX 10.x. If the user desires a working copy of both the IESX 10.x
     project and the GeoFrame 3.x projects, it is recommended that a copy of
     the 10.x project be created before an upgrade is attempted.  Create a
     copy of the 10.x project using the Rename utility.  Customer Support
     strongly suggests that the rename option available on the `Upgrade IESX10.1
     Project' menu not be used because this option will rename the project in
     the Oracle data base, but the original project name is retained in the
     IESX GeoFrame 3.x database and will cause problems later if the user wants
     to patch in their original IESX 10.x project.
 
3.)  Before the upgrade is attempted MAKE A CURRENT BACKUP of the IESX 10.x
     project.
 
4.)  Open permissions wide open (777) on the 10.x project.
 
5.)  Always unshare all clones from the master 10.x project prior to the
     upgrade.
  -  If you don't want to unshare there is an unshare option in the upgrader
     that will unshare the shared references for you, Customer Support
     recommends to unshare before upgrading.
  -  To get a report of what data is shared in a clone project (outgoing
     references) run option 73 in the iesx_utils.  This will show the paths to
     the data the clone project is sharing (10.2 option only).
 
6.)  Recover project inventory using IES Datamanager > Add data to Project > 
     Add data in IES format > Create new project inventory. 
 
7.)  If any markers reside in the IES database import them to IESX using
     DataManager > Markers > Import from IES.
 
8.)  Clean up any survey descriptions and any byte zero problems by using
     iesx_util/ option 5.
 
9.)  Check for any missing files by using option 41 (Check inventory files)
     in the iesx_utils.
 
10.) Delete any duplicate fault contacts and/or fault cuts or traces using
     iesx_util/ options 23, 24, and 25.
 
11.) It is recommended that a FIELD NAME be entered into IESX > DataManager >
     Wells > Wells menu prior to the upgrade. After the upgrade to GeoFrame
     3.x, each well will be divided into separate fields. If there isn't a
     FIELD NAME associated with the well, it will belong to the `IESX_field'.
     It is much simpler to set this prior to the upgrade, rather than after.


CONSIDERATIONS

1.)  Suggested upgrade sequence.
     -Master projects first 
     -clone or shared projects second 
     Master and clones cannot be upgraded simultaneously.

2.)  Typically in a project upgrade, the problem areas are well data, mapping
     data, and interpretation.  Upgrade of seismic data and interpretation 
     data should be virtually pain free because it just makes pointers in the
     ORACLE database and the bulk files are not touched.  Preparation and
     cleaning up of the wells, mapping data and interpretation data types,
     prior to upgrade, will improve speed and decrease probability of failure.

The following is an overview of what will happen to each data type during the
upgrade (in order of most time taken to least).

a.)  Wells - are exported to a temporary area from IESX (defined in the upgrade
     dialog box).  New wells and boreholes are created in Oracle and this data
     is imported into GeoFrame 3.X.  New files/directories will be created in
     the Default DSL.
 
b.)  Markers - are exported to a temporary area from IESX (defined in the
     upgrade dialog box).  When imported into GeoFrame a surface will be
     created for each marker name (i.e. effectively a horizon for every marker
     name).  The link between existing horizon names and marker names will
     be lost unless they are identical.  The surface created from a marker will
     be a `geological horizon'.  If markers exist for faults they will be
     upgraded as `surfaces'.

If you have a project that has an `f' fault and `f' marker, then read the
below workaround.  

When you try to enter Seis%DV you will receive the following error: 
   Seismic Display creation failed - Interpretation not found. 
   Invalid token.
   Database object token - field ID mismatch.  
   DB token (0,0,0) is incompatible with FID 101014203.

You will not be able to post seismic trace data or interpretation until you do
the following:

From the GeoFrame `Application Manager', under `Managers' choose `Data'. This
will bring up the Data Management Catalog.  Then choose Data Manager/Surfaces
and populate `Geologic Horizon'.  Sort by 'Name'.  Click on the 'f' surface
name and edit to a new name.  Apply.  The `f' fault in Seis%DV will now
recreate and your seismic and interpretation will post.

c.) Mapping Data - (grids, contours, scatter sets and MapView fault traces).
    These data types are exported from IESX 10.x to the temporary area and are
    later imported and converted to BasemapPlus / GeoFrame formats.  These new
    files will be stored in the Default DSL. If CPS-3 DSLs are defined for
    the project after the upgrade, such files would go there when added.


POST UPGRADE

1.)  The DSL naming convention in GeoFrame 3.x is different to that of IESX
     standalone (10.x and below) i.e. /disk/geoframe_dsl/ACCOUNTNAME/dsltype

          Examples:     /disk1/gf_root/PROJECT_X/Default/
                        /disk1/gf_root/PROJECT_X/Seismic/
                        /disk1/gf_root/PROJECT_X/Interpretation/

Data upgraded from IESX 10.x does not fit the new DSL naming convention. 

Examples: /disk1/gf_root/project_name  will upgrade to
          /disk1/gf_root/PROJECT_NAME (this is the account name).

All references for seismic and interpretation DSLs will be lost. In GeoFrame
3.x all DSLs after the upgrade will be considered Default DSLs.  Using Project
Manager, you will be able to add these existing DSLs as Interpretation or Seismic DSLs.


2.)  Items lost in the upgrade process due to upgrades to the appearance sets
     in GeoFrame.
   - Borehole appearance sets
   - Map appearance sets

3.)  A log file is created in the users $HOME directory showing each upgrade
     stage.  It also shows the start and end time of the upgrade so you can
     see how long the process actually ran. The log file is named,
     "uprade_10_11_project_name_time_stamp.log", this is a good file to look
     at if the upgrade has problems, it will log any problems.






Last Modified on: 07-MAY-99