You are on page 1of 117

EDM

Production and Economics


Database & Migration Guide
2004-2005 Landmark Graphics Corporation

R2003.14 June 2005


2004, 2005 Landmark Graphics Corporation
All Rights Reserved Worldwide

This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by
Federal copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system,
or translated into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or
disclosed to third parties without the express written permission of:

Landmark Digital and Consulting Solutions


2101 CityWest Blvd, Building 2, Houston, Texas 77042-3021, USA
P.O. Box 42806, Houston, Texas 77242, USA
Phone: 713-839-2000
FAX: 713-839-2401
Web: www.lgc.com

Trademark Notice

3DFS, 3D Drill View, 3D Drill View KM, 3DView, 3D Surveillance, Active Field Surveillance, Active Reservoir Surveillance,
ADC, Advanced Data Transfer, ARIES, Asset Development Center, AssetJournal, Asset Performance, AssetView, Atomic
Meshing, Automate, BLITZ, BLITZPAK, CasingSeat, COMPASS, Contouring Assistant, Corporate Data Archiver, Corporate
Data Store, DataManager, DataStar, DBPlot, DecisionSuite, Decisionarium, DecisionSpace, DecisionSpace AssetPlanner,
DecisionSpace AssetView, DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace
Nexus, DecisionSpace PowerGrid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir,
DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion, DepthTeam, DepthTeam Explorer, DepthTeam Express,
DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery,
Discovery Asset, Drill-to-the-Earth Model, Drillability Suite, Drilling Desktop, DrillModel, DrillVision, DSS, Dynamic Reservoir
Management, Dynamic Surveillance System, EarthCube, EDM, eLandmark, Engineers Data Model, The Engineer's Desktop,
Engineers Link, Executive Assistant, ezFault, ezSurface, ezTracker, FG+, FastTrack, FieldWorks, FZAP!, GeoDataLoad,
GeoGraphix (stylized), GeoGraphix Exploration System, GeoLink, GeoProbe, GeoProbe GF DataServer, GES, GESXplorer,
GMAplus, GRIDGENR, Handheld Field Operator, I2 Enterprise, iDIMS, IsoMap, iWellFile, Landmark, Landmark & Design,
Landmark Logo & Design, Landmark Decision Center, Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep,
Magic Earth, MagicDesk, Make Great Decisions, MathPack, MIMIC, MIMIC+, MIRA, Model Builder, MyLandmark, Nexus,
Object MP, OpenBooks, Open Explorer, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks
Well File, PAL, Parallel-VIP, PetroBank, PetroWorks, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher,
PostStack, PostStack ESP, PowerCalculator, PowerExplorer, PowerHub, Power Interpretation, PowerJournal, PowerModel,
PowerView, Presgraf, PRIZM, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX,
ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+,
QUICKDIF, QUIKCDP, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, Quickwell, Quickwell+, RAVE, RayMap, RayMap+,
RTOC, Real Time Asset Management Center, Real Time Asset Management Centre, Real Time Knowledge Company, Real Time
Operations Center, Real Time Production Surveillance, Real Time Surveillance, Reference Data Manager, Reservoir Framework
Builder, RESev, ResMap, RightTime, RMS, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks,
SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisXchange, Sierra, Sierra (design),
SigmaView, SimResults, SIVA, SIVA+, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel,
StrataSim, StratWorks, StressCheck, STRUCT, Surf & Connect, SynTool, SystemStart for Servers, SystemStart, SystemStart for
Clients, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, Total Drilling Performance, TOW/cs, TOW/cs
Revenue Interface, TracPlanner, Trend Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIP-
DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Well Seismic Fusion,
Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WELLPLAN, WellXchange, WOW, Xsection, You're in
Control. Experience the difference, ZAP!, and Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark
Graphics Corporation.

All other trademarks are the property of their respective owners.

Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by
Landmark Graphics Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this
manual. Some states or jurisdictions do not allow disclaimer of expressed or implied warranties in certain transactions; therefore,
this statement may not apply to you.
Landmark EDM Production and Economics Database & Migration Guide

Contents

EDM Introduction............................................................................................................ 7
Overview............................................................................................................................. 7
What is an EDM Database ........................................................................................... 7
Database Security ........................................................................................................ 7
Java Functions .............................................................................................................. 7
Backup Strategy ........................................................................................................... 8
Upgrading and Merging the 2003.5 and 2003.6 Databases ......................................... 8

Creating a New 2003.14 Database ......................................................................... 9


Overview............................................................................................................................. 9
Required Tools and Installation .......................................................................................... 9
Database Creation ........................................................................................................ 9
Creation Procedures ............................................................................................................ 10
Oracle ........................................................................................................................... 10
SQL Server .................................................................................................................. 14

Upgrading a 2003.4.2.0 AFS Database


to Version 2003.14 .......................................................................................................... 17
Overview............................................................................................................................. 17
Required Tools and Installation .......................................................................................... 18
Database Update .......................................................................................................... 18
AFS Data Migration ..................................................................................................... 18
ARIES Upgrade Tool ................................................................................................... 19
An existing AFS Instance ................................................................................................... 20
Upgrade Procedures ..................................................................................................... 20
Upgrading your EDM 2003.11 database to an EDM 2003.14 database............................. 26
Upgrade Procedures ..................................................................................................... 26

Upgrading a Standalone ARIES Database........................................................ 33


Overview............................................................................................................................. 33
Required Tools and Installation .......................................................................................... 33
Database Creation ........................................................................................................ 33
ARIES Upgrade Tool ................................................................................................... 34
ARIES to EDM Migration Tool .................................................................................. 34
Upgrade ARIES 2003.40 or less to 2003.41 Schema ......................................................... 36
Create EDM Instance Procedures ....................................................................................... 37
Oracle ........................................................................................................................... 37

R2003.14 Contents iii


EDM Production and Economics Database & Migration Guide Landmark

SQL Server/MSDE ...................................................................................................... 40


Migrating The Data from ARIES to EDM ......................................................................... 43
Upgrading your EDM 2003.11 database to an EDM 2003.14 database............................. 48
Upgrade Procedures ..................................................................................................... 48

Upgrading ARIES & TOW/cs Standalone Databases.................................. 53


Overview............................................................................................................................. 53
Required Tools and Installation .......................................................................................... 54
Database Creation ........................................................................................................ 54
Database Update .......................................................................................................... 54
AFS Data Migration ..................................................................................................... 55
ARIES Upgrade Tool ................................................................................................... 56
ARIES to EDM Migration Tool .................................................................................. 56
Converting Standalone ARIES and Tow/cs Databases ...................................................... 58
Upgrading your EDM 2003.11 database to an EDM 2003.14 database............................. 61
Upgrade Procedures ..................................................................................................... 61

Appendix A:
Migration Tables and Column Mappings .......................................................... 65
AFS to EDM Column Migration Mappings ....................................................................... 71
Migrating Modified ARIES Tables .................................................................................... 72

Appendix B:
ARIES Table Changes .................................................................................................. 73
Traditional ARIES Table Changes ..................................................................................... 73
New ARIES Tables (4 Tables) .................................................................................... 75
New ARIES International Tables (2 Tables) ............................................................... 75
Unchanged ARIES Tables ........................................................................................... 76
ARIES AFS Table Changes ......................................................................................... 76
Merged ARIES Tables ................................................................................................. 77
ARIES Column Changes ............................................................................................. 77

Appendix C:
Manual Oracle Upgrades ............................................................................................ 111
Procedure ............................................................................................................................ 112

Appendix D:
Manual SQL Server Upgrades ................................................................................. 113

Appendix E:Oracle Configuration ......................................................................... 115

iv Contents R2003.14
Landmark EDM Production and Economics Database & Migration Guide

Oracle ODBC...................................................................................................................... 115


RDBMS Configuration ....................................................................................................... 116
Oracle ........................................................................................................................... 116

R2003.14 Contents v
EDM Production and Economics Database & Migration Guide Landmark

vi Contents R2003.14
Landmark EDM Production and Economics Database & Migration Guide

EDM Introduction

Overview

What is an EDM Database


EDM provides a common database schema that allows for common
data access, enables naturally integrated engineering workflows, and
reduces data entry duplication across applications.

EDM provides support for Drilling, Production & Economics


applications on a shared data model.

Through the Engineers Desktop, applications access the EDM


database.

Database Security
The 2003.14 release of EDM includes a standard EDM Security Model.
This Security Model supports group and user permissions, Tight Site
and Well protection, and application security tokens.

Landmark does not recommend customizing the EDM data model as


changes may conflict with or be removed by future versions of EDM.

Java Functions
The Engineers Desktop installation includes some Java Functions that
get stored in the database. Therefore, Oracle JServer Components must
be installed with the Oracle Software on the Server. Open the Oracle
Universal Installer on the Oracle Server and verify that this component
is installed. If this component is needed, use the Oracle Universal
Installer to add this component. In addition, the Oracle JServer
Component must be included in the database. If the Jserver Component
exists in the Oracle Software Installation, then a Typical Database can
be created and this component will be included. If a Custom database is
created, then the JServer component should be selected during the
database creation. The Oracle Database Configuration Assistant can be

R2003.14 EDM Introduction 7


EDM Production and Economics Database & Migration Guide Landmark

used to add the Oracle Jserver Component to an existing Custom


Database.

If the JServer component is missing from the Oracle Software and/or


the database, then an error may occur.

Backup Strategy
Defining a reliable backup strategy is vital to any Database
Administrators role to enable timely restoration of the database in the
event of a database server failure. Landmark recommends the
establishment of a backup strategy prior to loading data. It is essential
to implement the backup strategy before the entry of data into the EDM
database begins.

Upgrading and Merging the 2003.5 and 2003.6 Databases


To upgrade both a Drilling 2003.5 database and a Production and
Economics 2003.6 database to the 2003.14 platform, clients should use
the following steps:

First, upgrade the Production and Economics 2003.6 database to a


2003.11 database (e.g., Database A), using the instructions in this
guide.

Second, upgrade the Drilling 2003.5 database to a 2003.11


database (e.g., Database B), using the instructions in the EDM
Drilling Database Guide (EDM_Drilling_Database.pdf).

Third, export 2003.11 Database B data to XML, using one of the


Drilling applications (e.g., OpenWells, COMPASS).

Fourth, import Drilling data XML to the 2003.11 Database A,


using one of the Drilling Applications (e.g., OpenWells,
COMPASS).

Fifth, merge any duplicate business objects in the 2003.11


Database A using the EDM Merging tool (see EDM Drilling Data
Migration Guide (EDM_Drilling_DataMigration.pdf)).

Sixth, upgrade the Production & Economics 2003.11 database to


the Production & Economics 2003.14 database, using the
instructions in this guide. This concludes the procedure.

8 EDM Introduction R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Creating a New 2003.14 Database

Overview

This section outlines the required tools and procedures that you will
need to use and understand in order to create a new 2003.14 Oracle or
SQL Database.

These instructions are not intended for users that are already using an
AFS, ARIES standalone, TOW/cs standalone, or Drilling Database.

Required Tools and Installation

Database Creation

About Database Creation


The EDM Database Creation Tool allows the user to create an EDM
2003.14 Oracle or SQL Server\MSDE database.

Locating and Installing the Database Update Tool


To install the EDM database creation tool choose Database Creation
from the Selection Components list during the installation process. This
will place the executable, db_create.exe under the
c:\Landmark\EDT_2003.14\EDM folder.

The EDM Database Creation Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
EDM Database Creation.

R2003.14 Creating a New 2003.14 Database 9


EDM Production and Economics Database & Migration Guide Landmark

Creation Procedures

These steps should be used for clients that do not have a database.

Oracle
1. Create a blank Oracle instance. For more information on instance
configuration, see Appendix E.

2. Tablespaces are created from the script, EDMSPC.SQL and


located in c:\Landmark\EDT_2003.14\EDM\Oracle\
tablespaces

The EDMSPC.SQL script can be edited to create the tablespaces in


the desired directories.

3. Click Start > Programs > Landmark Engineers Desktop


2003.14 > Tools > EDM Database Creation to execute
db_create.exe. The master script is created through the
db_create.exe and when executed, will create the new EDM
database and populate the required tables with startup data and
metadata.

4. Select Oracle

5. Click Start.

10 Creating a New 2003.14 Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The EDM Oracle Database Creation Wizard message will be


displayed.

6. Click Yes.

7. Select a directory for the master script createDB.sql file to be


created in.

All log files will be created in this directory.

8. Click OK to create an Admin schema.

A Database Creation Wizard message is displayed.

9. Click Yes.

10. Continue with EDMADMIN as the default.

11. Press OK.

R2003.14 Creating a New 2003.14 Database 11


EDM Production and Economics Database & Migration Guide Landmark

A db_create message will be displayed.

12. Click OK.

13. Edit the createdb.SQL file if needed.

Running the Script from Locations Other than the Server/


Multiple Oracle databases.

If you are running the script from a location other than the server or if you
have multiple Oracle databases on one machine, you will need to change
the connection string. The script should include the instance name if you
are not running it from the server.

Examples:
Connect EDMADMIN/EDMADMIN
should be changed to
connect EDMADMIN/EDMADMIN@instancename

Connect PK/Landmark
should be changed to
connect PK\Landmark@Instancename
In addition, you need to update the location of log files within the script.
To manually change the location of log files, edit the script with a text
editor. Log files exist at each instance in the script where something is
created.

14. Run the createdb.SQL.

12 Creating a New 2003.14 Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

15. Import Site Config Files.

Landmark default configurations are contained in the EDM database


and installed with the MSDE database. These files are used to
configure Output Reports, OpenWells Preview Panes, OpenWells
Data Entry Forms, OpenWells Shortcut Bars, and more. For an
Oracle database, these configuration files must be imported using
the EDM Administration Utility. The files are located in the
following folder once the installation has been performed:
c:\Landmark\EDT_2003.14\EDM\Site
Configuration Files. For detailed instructions see the EDM
Administration Utility
on-line help.

Loading Production Metadata into the EDM Oracle Database

To load metadata into the EDM Oracle Database, the database


administrator should:

1. Follow the previous installation and database creation instructions.

2. Have or install the Microsoft .NET Framework 1.1 on the machine


that will launch the program.

Microsoft .NET Framework 1.1

Installation for the Microsoft .NET Framework is part of the EDM and
Production & Economics 3rd party installation.

3. Create a dsn on the users machine using the ODBC data source
and use the same username and password that you used for the
database login name and password.

4. Verify that the MetaDataLibrary.resources program is in the


<Landmark Install drive>
\Landmark\EDT_2003.14\EDM\Oracle\EDMdata\
MetaData Loader directory.

MetaDataLibrary.resources

The MetaDataLibrary.resources file is required in the application directory.


This program is the program that specifically loads the metadata.

R2003.14 Creating a New 2003.14 Database 13


EDM Production and Economics Database & Migration Guide Landmark

5. From the command line, change the directory to access the


MetaDataLoader.exe from the c:\Landmark\EDT_2003.14
\EDM\Oracle\EDMdata
\MetaDataLoader folder.

6. Type the following text in the command line: MetaDataLoader


DSN username password and the MetaDataLoader.exe will run.

After the MetaDataLoader.exe is run from the command line, a


MetaDataLoad.log output file will be generated in the application
directory. It will log the error message or the summary information for
the metadata (how many rows loaded into each table).

The MetaDataLoader.exe is a console program used to load the


Landmark published metadata into the users EDM database.

The MetaDataLoader will load the following tables:

MD_EDT_FORMULA_GROUP
MD_EDT_COLUMN_FORMULA
MD_EDT_TABLE_GROUP
MD_EDT_TABLE_PROP
MD_EDT_FIELD_PROP
MD_EDT_TMPL_CATEGORY
MD_EDT_TMPL_SET
MD_EDT_TMPL_SET_DATA
MD_EDT_TMPL_TEMPLATE
MD_EDT_TMPL_PICKLIST
MD_EDT_PICKLIST_USAGE

After administrating the MetaDataLoader.exe

After administrating the MetaDataLoader.exe, check the


MetaDataLoad.log output file in the MetaDataLoader folder and verify
that the new tables exist and that the data was loaded.

The database is ready for use.

SQL Server
1. Click Start > Programs > Landmark Engineers Desktop
2003.14 > Tools > EDM Database Creation to run db_create.exe.

14 Creating a New 2003.14 Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The Database Schema Creation Wizard screen will be displayed.

2. Select SQL Server and click Start.

The EDM SQL Server Database Creation Wizard message will be


displayed.

3. Click Yes.

R2003.14 Creating a New 2003.14 Database 15


EDM Production and Economics Database & Migration Guide Landmark

4. Select the directory where you would like the database to be


copied to.

If you are not running the db_create.exe on a server, you must


map the servers drive before running db_create.

5. Click OK.

6. Enter the database name and click OK.

7. Enter the System Administrator password.

The Database is attached and a message will be displayed.

8. Press OK.

9. Click End.

The database is ready for use.

16 Creating a New 2003.14 Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Upgrading a 2003.4.2.0 AFS Database


to Version 2003.14

Overview

This section outlines the required tools and procedures that you will
need to use and understand in order to upgrade a 2003.4.2.0 database to
a new 2003.14 AFS Oracle or SQL Database.

First, you will upgrade the AFS Database to a 2003.11 AFS Oracle or
SQL Database, then migrate your data, and finally upgrade the 2003.11
database to a 2003.14 Oracle or SQL Database.

These instructions are intended for users that are already using an AFS
database.

The upgrade procedure will work for AFS 2003.4.2.0 databases with
any of the following configurations:

TOW/cs only database

TOW/cs with ARIES Integration database

TOW/cs with ARIES & DIMS Integration (An AFS database)

Before an upgrade can be performed on an AFS database, verify that


the AFS database version is AFS version 2003.4.2.0 and the ARIES
table version is 2003.41.

Attention TOW/cs Users

Complete the Send/Receive process before upgrading your database.

Back up the database.

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 17


EDM Production and Economics Database & Migration Guide Landmark

Required Tools and Installation

Database Update
Use the Production_to_2003.11.exe to update your 2003.4.2.0 AFS
database.

About the Database Utility


The Production_to_2003.11 exe is an upgrade executable that upgrades
any form of an AFS database to an EDM 2003.11 database.

Production_to_2003.14.exe

The Production _to_2003.14.exe will up grade your EDM 2003.11 Oracle or SQL
Database to an EDM 2003.14 Oracle or SQL Database.

Locating and Installing the Database Update Tool


To install the database update tools choose Database Updates from the
Selection Components list during the installation process. This will
place the executables under the c:Landmark\EDT\EDM\Updates
folder.

AFS Data Migration

About AFS Data Migration


The AFSMigration.exe is the tool to migrate the Production and
Economics Data from an AFS 2003.4.2.0 database to an EDM 2003.11
database.

Data Migration

You will not have to migrate the data when upgrading the 2003.11 database to a
2003.14 database.

18 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Locating and Installing the AFS Data Migration Tool


To install the AFS to EDM Migration tool you must select the
Production and Economics Data Migration tool from the select
components list during the installation process. This installs the
AFSDataMigration.exe into the
C:\Landmark\EDT_2003.14\EDM\Data Migration folder.

The AFS Data Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
AFS to EDM Migration.

ARIES Upgrade Tool

About ARIES Upgrade Tool


The ARIES Upgrade Tool is only used if your ARIES schema version
is not 2003.41. Otherwise, you will be unable to update your AFS
2003.4.2 database.

Please verify ARIES schema version before installing ARIES.

Locating and Installing the ARIES Upgrade Tool


To install the ARIES upgrade tool, you must select the ARIES product
from the select components list during the installation process. This
installs the Upgrade.exe into the
C:\Landmark\EDT_2003.14\ARIES\Programs directory.

When using an older ARIES database in which the PROJList


table has not been updated for old projects, you may receive the
error No Master Record Found. This error is caused by the
INTKEY and PROPNUM being different in the original database.
To prevent this error from occurring, update any projects in
which the INTKEY and PROPNUM do not match by using the
Upgrade.exe tool and check the Update ProjectList Table option
when the original database is upgraded prior to migration.

See page 34 for instruction on how to use this tool.

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 19


EDM Production and Economics Database & Migration Guide Landmark

An existing AFS Instance

Upgrade Procedures

Run Automated Oracle Upgrade


These steps should be used for clients that have an existing AFS
database.

Oracle
1. Run the Edmspc.sql from the updates directory

c:\Landmark\EDT_2003.14\EDM\Updates

The EDMspc.sql file will create the necessary tablespaces and grant the
correct permissions to perform the upgrade.

The EDMSPC.SQL script can be edited to create the tablespaces in


the desired directories.

2. From the
c:\Landmark\EDT_2003.14\EDM\Updates\Oracle
directory, execute the Production_to_2003.11.exe self
extracting executable.

The following dialog appears:

3. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into the


TEMP directory for execution.

20 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

4. Choose Run Automated to run the upgrade program in automatic


mode.

The following dialog appears:

5. Enter the requested database login and connection parameters


information. You will need to login as the schema owner to
perform this upgrade.

6. Click OK.

If the AFS or ARIES version is incorrect, a message will be


displayed and the upgrade process will abort.

7. If prompted to save the log file, click the Yes button and select a
destination directory.

8. Review the log files for errors.

9. Run the AFS to EDM Migration Utility.

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 21


EDM Production and Economics Database & Migration Guide Landmark

Start > Programs > Landmark Engineers Desktop 2003.14 >


Tools > AFS to EDM Migration

10. Select the ellipse button to login to the database.

11. Enter the schema owner as username with password.

12. Click the Edit button.

13. Select the database with ODBC DSN or .Net Connection.

14. Click OK.

15. Click Login.

22 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The AFS to EDM Data Migration Tool screen will be displayed.

16. Click the Migrate button.

The database will begin the migration and a progress bar will be
displayed.

17. Review the log file by selecting Menu > View > Log.

18. Verify that the data is correct.

19. Run the cleanup script.

C:\Landmark\EDT_2003.14\EDM\ DATA Migration\


AFSFinalCleanup_Oracle.SQL

The database is ready to use.

Run Automated SQL Server Upgrade

SQLServer
1. From the Vol 5\Products\EDT\Previous DB
Upgrades\SQL Server directory, execute the
Production_to_2003.11.exe self extracting executable.

The following dialog appears:

2. Click the Setup button to begin the upgrade process.

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 23


EDM Production and Economics Database & Migration Guide Landmark

The WinZip Self-Extractor unzips the upgrade scripts into a


TEMP directory for execution.

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

3. Choose Run Automated to run the upgrade program in automatic


mode.

The following dialog appears:

4. Enter the requested database login and connection parameters


information. You will need to login as System Administrator SA
to perform this upgrade.

5. Click OK.

If the AFS or ARIES version is incorrect, a message will be


displayed and the upgrade process will abort.

6. If prompted to save the log file, click the Yes button and select a
destination directory.

24 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

7. Review the log files for errors.

8. Run the AFS to EDM Migration Utility

Start > Programs > Landmark Engineers Desktop 2003.14 >


Tools > AFS to EDM Migration

9. Select the ellipse button to login to the database.

10. Enter the schema owner as username with password.

11. Click the Edit button.

12. Select the database with ODBC DSN or .Net Connection.

13. Click OK.

14. Click Login.

15. Click the Migrate button.

The database will begin the migration and a progress bar will be
displayed.

16. Review the log file by selecting Menu > View > Log.

17. Verify that the data is correct.

18. Run the cleanup script.

c:\Landmark\EDT_2003.14\EDM\DATA
Migration\AFSFinalCleanup.sql

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 25


EDM Production and Economics Database & Migration Guide Landmark

Upgrading your EDM 2003.11 database to an EDM


2003.14 database

Next, you will upgrade your 2003.11 Oracle or SQL database to a


2003.14 Oracle or SQL database

Upgrade Procedures

Run Automated Oracle Upgrade


These steps should be used for clients that have already established the
EDM 2003.11 database.

Oracle
1. From the
c:\Landmark\EDT_2003.14\EDM\Updates\Oracle
directory, execute the 2003_14_0_0_Patch_Oracle.exe
self extracting executable.

The following dialog appears:

2. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into the


TEMP directory for execution.

26 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

3. Choose Run Automated to run the upgrade program in automatic


mode.

The following dialog appears:

4. Enter the requested database login and connection parameters


information. You will need to login as the schema owner to
perform this upgrade.

5. Click OK.

If the AFS or ARIES version is incorrect, a message will be


displayed and the upgrade process will abort.

6. If prompted to save the log file, click the Yes button and select a
destination directory.

7. Review the log files for errors.

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 27


EDM Production and Economics Database & Migration Guide Landmark

8. Run the AFS to EDM Migration Utility.

Start > Programs > Landmark Engineers Desktop 2003.14 >


Tools > AFS to EDM Migration

9. Select the ellipse button to login to the database.

10. Enter the schema owner as username with password.

11. Click the Edit button.

12. Select the database with ODBC DSN or .Net Connection.

13. Click OK.

14. Click Login.

28 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The AFS to EDM Data Migration Tool screen will be displayed.

15. Click the Migrate button.

The database will begin the migration and a progress bar will be
displayed.

16. Review the log file by selecting Menu > View > Log.

17. Verify that the data is correct.

18. Run the cleanup script.

C:\Landmark\EDT_2003.14\EDM\ DATA Migration\


AFSFinalCleanup_Oracle.SQL

The database is ready to use.

Run Automated SQL Server Upgrade

SQLServer
1. From the c:\Landmark\EDT_2003.14\EDM\Updates\
SQLServer directory, execute the
2003_14_0_0_Patch_SQL.exe self extracting executable.

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 29


EDM Production and Economics Database & Migration Guide Landmark

The following dialog appears:

2. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into the


TEMP directory for execution.

3. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into a


TEMP directory for execution.

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

4. Choose Run Automated to run the upgrade program in automatic


mode.

30 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The following dialog appears:

5. Enter the requested database login and connection parameters


information. You will need to login as System Administrator SA
to perform this upgrade.

6. Click OK.

If the AFS or ARIES version is incorrect, a message will be


displayed and the upgrade process will abort.

7. If prompted to save the log file, click the Yes button and select a
destination directory.

8. Review the log files for errors.

9. Run the AFS to EDM Migration Utility

Start > Programs > Landmark Engineers Desktop 2003.14 >


Tools > AFS to EDM Migration

10. Select the ellipse button to login to the database.

11. Enter the schema owner as username with password.

12. Click the Edit button.

13. Select the database with ODBC DSN or .Net Connection.

14. Click OK.

15. Click Login.

16. Click the Migrate button.

R2003.14 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 31


EDM Production and Economics Database & Migration Guide Landmark

The database will begin the migration and a progress bar will be
displayed.

17. Review the log file by selecting Menu > View > Log.

18. Verify that the data is correct.

19. Run the cleanup script.

c:\Landmark\EDT_2003.14\EDM\DATA

The database is ready to use.

32 Upgrading a 2003.4.2.0 AFS Database to Version 2003.14 R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Upgrading a Standalone ARIES Database

Overview

This section outlines the required tools and procedures that you will
need to use for upgrading a standalone ARIES Oracle, Access, or SQL
database.

These instructions are intended for users that are already using a
standalone ARIES database and this chapter will explain how to
upgrade a Standalone ARIES database to an EDM 2003.11.0 database.

Once the EDM 2003.11 database is established, you will migrate your
data, then upgrade the EDM 2003.11 database to an EDM 2003.14
database using the Production_to_2003.14 exe.

Required Tools and Installation

Database Creation

About Database Creation


The EDM Database Creation Tool allows the user to create an EDM
2003.11 Oracle or SQL Server\MSDE database.

Locating and Installing the Database Update Tool


To install the EDM database creation tool choose Database Creation
from the Selection Components list during the installation process. This
will place the executable, db_create.exe under the
c:\Landmark\EDT_2003.14\EDM folder.

The EDM Database Creation Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
EDM Database Creation.

R2003.14 Upgrading a Standalone ARIES Database 33


EDM Production and Economics Database & Migration Guide Landmark

ARIES Upgrade Tool

About ARIES Upgrade Tool


The ARIES Upgrade Tool is only used if your ARIES schema version
is not 2003.41. Otherwise, you will be unable to update your AFS
2003.4.2 database.

Please verify ARIES schema version before installing ARIES.

Locating and Installing the ARIES Upgrade Tool


To install the ARIES upgrade tool, you must select the ARIES product
from the select components list during the installation process. This
installs the Upgrade.exe into the
C:\Landmark\EDT_2003.14\ARIES\Programs directory.

When using an older ARIES database in which the PROJList


table has not been updated for old projects, you may receive the
error No Master Record Found. This error is caused by the
INTKEY and PROPNUM being different in the original database.
To prevent this error from occurring, update any projects in
which the INTKEY and PROPNUM do not match by using the
Upgrade.exe tool and check the Update ProjectList Table option
when the original database is upgraded prior to migration.

See page 34 for instruction on how to use this tool.

ARIES to EDM Migration Tool

About ARIES to EDM Upgrade Tool


The ARIES to EDM Migration tool migrates ARIES standalone data
into a new EDM instance.

Locating and Installing the ARIES to EDM Migration Tool


To install the ARIES to EDM Migration tool you must select the
Production and Economics Data Migration tool from the select
components list during the installation process. This installs the

34 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

ARIESTOEDM.exe into the


C:\Landmark\EDT_2003.14\EDM\Data Migration folder.

The ARIES to EDM Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
ARIES to EDM Migration.

R2003.14 Upgrading a Standalone ARIES Database 35


EDM Production and Economics Database & Migration Guide Landmark

Upgrade ARIES 2003.40 or less to 2003.41 Schema

Before data can be migrated to the EDM model, it must be upgraded to


version 2003.4.1. This is accomplished using the upgrade.exe program.
To perform the upgrade, follow these steps:

1. Double click the upgrade.exe program. By default, Upgrade.exe is


installed to the C:\Landmark\EDT_2003.14\ARIES\Programs
directory.

2. The upgrade program will automatically be populated with the


available ARIES data sources. Click the data source relating to the
ARIES database to be upgraded.

3. If they have been defined, enter the ARIES Schema Owner and
ARIES Role names. If these have not been defined, accept the
default values of No Owner and No Role.

4. Select the Update ProjectList Table box. It is recommended that


the Update PROJLIST check-box is checked to ensure that ARIES
INTKEY and PROPNUM are the same. EDM will not recognize
any property in which these are different.

5. Click OK. The database will be updated to schema 2003.41.

Once your data has been upgraded to 2003.41, you need to create an
EDM instance to which you will migrate your data.

36 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Create EDM Instance Procedures

Use these tools and procedures to create a new Oracle or SQL Server
database.

Oracle
1. Create a blank Oracle instance. For more information on instance
configuration, see Appendix E.

2. Tablespaces are created from the script, EDMSPC.SQL and


located in
<Install folder>\EDM\Updates\Previous
Upgrades folder

The EDMSPC.SQL script can be edited to create the tablespaces in


the desired directories.

3. Click Start > Programs > Landmark Engineers Desktop


2003.14 > Tools > EDM Database Creation to execute
db_create.exe. The master script is created through the
db_create.exe and when executed, will create the new EDM
database and populate the required tables with startup data and
metadata.

4. Select Oracle

5. Click Start.

R2003.14 Upgrading a Standalone ARIES Database 37


EDM Production and Economics Database & Migration Guide Landmark

The EDM Oracle Database Creation Wizard message will be


displayed.

6. Click Yes.

7. Select a directory for the master script createdb.sql file to be


created in.

All log files will be created in this directory.

8. Click OK to create an Admin schema.

A Database Creation Wizard message is displayed.

9. Click Yes.

10. Continue with EDMADMIN as the default.

11. Press OK.

38 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

A db_create message will be displayed.

12. Click OK.

13. Edit the createdb.SQL file if needed.

Running the Script from Locations Other than the Server/


Multiple Oracle databases.

If you are running the script from a location other than the server or if you
have multiple Oracle databases on one machine, you will need to change
the connection string. The script should include the instance name if you
are not running it from the server.

Examples:
Connect EDMADMIN/EDMADMIN
should be changed to
connect EDMADMIN/EDMADMIN@instancename

Connect PK/Landmark
should be changed to
connect PK\Landmark@Instancename
In addition, you need to update the location of log files within the script.
To manually change the location of log files, edit the script with a text
editor. Log files exist at each instance in the script where something is
created.

14. Run the createdb.SQL.

R2003.14 Upgrading a Standalone ARIES Database 39


EDM Production and Economics Database & Migration Guide Landmark

15. Import Site Config Files.

Landmark default configurations are contained in the EDM database


and installed with the MSDE database. These files are used to
configure Output Reports, OpenWells Preview Panes, OpenWells
Data Entry Forms, OpenWells Shortcut Bars, and more. For an
Oracle database, these configuration files must be imported using
the EDM Administration Utility. The files are located in the
following folder once the installation has been performed:
c:\Landmark\EDT\EDM\Site Configuration Files.
For detailed instructions see the EDM Administration Utility
on-line help.

The following steps are recommended before migrating the ARIES


data.

16. Review the EDM database and compare to your existing database.
Specifically, compare master table (AC_PROPERTY) to EDM
master tables (ECON_PROPERTY, ECON_EXTENSION)

17. Since EDM is more rigid than prior ARIES releases, Master items
match similar item in the EDM table

18. If desired to include more master items, add any user defined items
to ECON_EXTENSION_UXEXT

19. Assure that the first four ECOPHASES match (1. OIL (i.e. 370), 2.
GAS (371), 3. CND (372), and 4. OWG (373). Some users have
flipped NGL and CND, the NGL (374) should be 5th phase (not
the 3rd). If not corrected, errors will occur when the data is
migrated.

SQL Server/MSDE
1. Click Start > Programs > Landmark Engineers Desktop
2003.14 > Tools > EDM Database Creation to run db_create.exe.

40 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The Database Schema Creation Wizard screen will be displayed.

2. Select SQL Server and click Start.

The EDM SQL Server Database Creation Wizard message will be


displayed.

3. Click Yes.

4. Select the directory where you would like the database to be


copied to.

If you are not running the db_create.exe on a server, you must


map the servers drive before running db_create.

R2003.14 Upgrading a Standalone ARIES Database 41


EDM Production and Economics Database & Migration Guide Landmark

5. Click OK.

6. Enter the database name and click OK.

7. Enter the System Administrator password.

The Database is attached and a message will be displayed.

8. Press OK.

9. Click End.

The EDM 2003.11 database is ready for use.

The following steps are recommended before migrating the ARIES


data.

10. Review the EDM database and compare to your existing database.
Specifically, compare master table (AC_PROPERTY) to EDM
master tables (ECON_PROPERTY, ECON_EXTENSION)

11. Since EDM is more rigid than prior ARIES releases, Master items
to match similar item in the EDM table

12. If desired to include more master items, add any user defined items
to ECON_EXTENSION_UXEXT

13. Assure that the first four ECOPHASES match (1. OIL (i.e. 370), 2.
GAS (371), 3. CND (372), and 4. OWG (373). Some users have
flipped NGL and CND, the NGL (374) should be 5th phase (not
the 3rd). If not corrected, errors will occur when the data is
migrated.

42 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Migrating The Data from ARIES to EDM

The ariestoedm.exe will migrate ARIES 2003.4.1 data to the EDM data
model. By default, ariestoedm.exe is installed to the
C:\Landmark\EDT_2003.14\EDM\DATA Migration
directory.

1. Select Start > Programs > Landmark Engineers Desktop


2003.14 > Tools > ARIES to EDM Migration.

2. Select the Data Source Name. The Data Source Name list-box
should correspond to the list of all Microsoft Access, SQL Server,
and Oracle data sources available from the ARIES Data Sources
dialog box displayed when ARIES is launched. Any Excel, dBase,
or other possible database formats will not be included in this
listing.

R2003.14 Upgrading a Standalone ARIES Database 43


EDM Production and Economics Database & Migration Guide Landmark

3. Click the arrow, and choose the data source that you wish to
migrate. Once a data source has been selected, the Data Migration
Tool's interface may change to reflect the type (Access, SQL
Server, or Oracle) of data source selected. As the Data Migration
process differs slightly for each data type, each process is
described individually below.

Microsoft Access Data Migration


When a Microsoft Access Data Source is selected, the Data Migration
Tool will update to display the following:

Source Data
For the Source Data, the Data Source Name and Primary DBS are
required. The DBS name must be entered manually, and should
correspond to a valid DBS listed in the ARIES DBS Selection window
for the selected Data Source.

Destination Data
For the destination data, the Driver, Server, Owner, Log In ID and
Password are required. The Database on Server is required if you select
the SQL Server driver.

The Driver defines whether the database will be transported to a SQL


Server or Oracle Database. The Server is the server to which the data
will be transported. If you are transporting to a SQL Server, you will

44 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

need to define the Database on the server to which you will transport.
The other items (Owner, Log In ID and Password) are all dependent
upon the database to which you are transporting.

SQL Server Data Migration


When an SQL Server Data Source is selected, the Data Migration Tool
will update to display the following:

Source Data
For the Source Data, the Data Source Name, Primary DBS, Log In ID,
Owner, and Password boxes are required. The DBS name must be
entered manually, and should correspond to a valid DBS listed in the
ARIES DBS Selection window for the selected Data Source.

Destination Data
For the destination data, the Driver, Server, Owner, Log In ID and
Password are required. The Database on Server is requires if you select
the SQL Server driver.

The Driver defines whether the database will be transported to a SQL


Server or Oracle Database. The Server is the server to which the data
will be transported. If you are transporting to a SQL Server, you will
need to define the Database on the server to which you will transport.
The other items (Owner, Log In ID and Password) are all dependent
upon the database to which you are transporting.

R2003.14 Upgrading a Standalone ARIES Database 45


EDM Production and Economics Database & Migration Guide Landmark

Oracle Data Migration


When an Oracle Data Source is selected, the Data Migration Tool will
update to display the following:

Source Data
For the Source Data, the Data Source Name, DBS, Log In ID, Owner,
and Password boxes are required. The DBS name must be entered
manually, and should correspond to a valid DBS listed in the ARIES
DBS Selection window for the selected Data Source.

Destination Data
For the destination data, the Driver, Server, Owner, Log In ID and
Password are required. The Database on Server is required if you
select the SQL Server driver.

The Driver defines whether the database will be transported to a SQL


Server or Oracle Database. The Server is the server to which the data
will be transported. If you are transporting to a SQL Server, you will
need to define the Database on the server to which you will transport.
The other items (Owner, Log In ID and Password) are all dependent
upon the database to which you are transporting.

4. Enter the information for the source and destination databases.

5. Click the Migrate button.

46 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

After running ARIES migration tool, it is strongly recommended to


open and review the LOG file created from the migration. This log file
will highlight master table items not migrated and may detail other
items that did not migrate.

Since EDM is rigid, there may be the possibility that the client may
defined a certain variable differently (size). If these items have size
larger than the EDM size, the properties containing these items with
sizes larger than the EDM size will not be migrated. For example, one
client has an API number of 18 characters (includes dashes), EDM only
allows for 16. If the 18 characters name is needed, then redefine it
using the UEXT table.

Review and compare data in the new EDM database; visually inspect
data; also, it is recommended to compare record count (this is the
quickest way to find data that did not migrate).

R2003.14 Upgrading a Standalone ARIES Database 47


EDM Production and Economics Database & Migration Guide Landmark

Upgrading your EDM 2003.11 database to an EDM


2003.14 database

Next, you will upgrade your 2003.11 Oracle or SQL database to a


2003.14 Oracle or SQL database

Upgrade Procedures

Run Automated Oracle Upgrade


These steps should be used for clients that have already established the
ARIES EDM 2003.11 database.

Oracle
1. From the
c:\Landmark\EDT_2003.14\EDM\Updates\Oracle
directory, execute the 2003_14_0_0_Patch_Oracle.exe
self extracting executable.

The following dialog appears:

2. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into the


TEMP directory for execution.

48 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

3. Choose Run Automated to run the upgrade program in automatic


mode.

The following dialog appears:

4. Enter the requested database login and connection parameters


information. You will need to login as the schema owner to
perform this upgrade.

5. Click OK.

If the ARIES version is incorrect, a message will be displayed


and the upgrade process will abort.

6. If prompted to save the log file, click the Yes button and select a
destination directory.

7. Review the log files for errors.

R2003.14 Upgrading a Standalone ARIES Database 49


EDM Production and Economics Database & Migration Guide Landmark

The database is ready to use.

Run Automated SQL Server Upgrade

SQLServer
1. From the c:\Landmark\EDT_2003.14\EDM\Updates\
SQLServer directory, execute the
2003_14_0_0_Patch_SQL.exe self extracting executable.

The following dialog appears:

2. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into the


TEMP directory for execution.

3. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into a


TEMP directory for execution.

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

50 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

4. Choose Run Automated to run the upgrade program in automatic


mode.

The following dialog appears:

5. Enter the requested database login and connection parameters


information. You will need to login as System Administrator SA
to perform this upgrade.

6. Click OK.

If the AFS or ARIES version is incorrect, a message will be


displayed and the upgrade process will abort.

7. If prompted to save the log file, click the Yes button and select a
destination directory.

8. Review the log files for errors.

The database is ready to use.

R2003.14 Upgrading a Standalone ARIES Database 51


EDM Production and Economics Database & Migration Guide Landmark

52 Upgrading a Standalone ARIES Database R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Upgrading ARIES & TOW/cs Standalone


Databases

Overview

This section is intended for users that are using individual ARIES and
TOW/cs databases and outlines the required tools and procedures that
you will need to use and understand in order to upgrade an ARIES and
TOW/cs standalone database to a single EDM 2003.14 Oracle or SQL
Database.

First, verify that the ARIES database schema is 2003.41 and the
TOW/cs database version is 2003.4.2.

If you currently have an earlier version of both ARIES and TOW, the
migration process is slightly different. The following workflow details
the steps needed to migrate both an ARIES and TOW/cs database to the
2003.0 model.

R2003.14 Upgrading ARIES & TOW/cs Standalone Databases 53


EDM Production and Economics Database & Migration Guide Landmark

Required Tools and Installation

Database Creation

About Database Creation


The EDM Database Creation Tool allows the user to create an EDM
2003.11 Oracle or SQL Server\MSDE database.

Locating and Installing the Database Update Tool


To install the EDM database creation tool choose Database Creation
from the Selection Components list during the installation process. This
will place the executable, db_create.exe under the
c:\Landmark\EDT_2003.14\EDM folder.

The EDM Database Creation Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
EDM Database Creation.

Database Update
Use the Production_to_2003.11.exe to update your 2003.4.2.0 AFS
database.

About the Database Utility


The Production_to_2003.11 exe is an upgrade executable that upgrades
any form of an AFS database to an EDM 2003.11 database.

Attention TOW/cs Users

Complete the Send/Receive process before upgrading your database.

54 Upgrading ARIES & TOW/cs Standalone Databases R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Production_to_2003.14exe

The Production _to_2003.14.exe will be used later in this chapter to upgrade your
EDM 2003.11 Oracle or SQL Database to an EDM 2003.14 Oracle or SQL
Database.

Locating and Installing the Database Update Tool


To install the database update tools choose Database Updates from the
Selection Components list during the installation process. This will
place the executables under the
c:Landmark\EDT_2003.14\EDM\Updates folder.

AFS Data Migration

About AFS Data Migration


The AFSMigration.exe is the tool to migrate the Production and
Economics Data from an AFS 2003.4.2.0 database to an EDM 2003.11
database.

Data Migration

You will not have to migrate the data when upgrading the 2003.11 database to a
2003.14 database.

Locating and Installing the AFS Data Migration Tool


To install the AFS to EDM Migration tool you must select the
Production and Economics Data Migration tool from the select
components list during the installation process. This installs the
AFSDataMigration.exe into the C:\Landmark\EDT\EDM\Data
Migration folder.

The AFS Data Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.11 > Tools >
AFS to EDM Migration.

R2003.14 Upgrading ARIES & TOW/cs Standalone Databases 55


EDM Production and Economics Database & Migration Guide Landmark

ARIES Upgrade Tool

About ARIES Upgrade Tool


The ARIES Upgrade Tool is only used if your ARIES schema version
is not 2003.41. Otherwise, you will be unable to update your AFS
2003.4.2 database.

Please verify ARIES schema version before installing ARIES.

Locating and Installing the ARIES Upgrade Tool


To install the ARIES upgrade tool, you must select the ARIES product
from the select components list during the installation process. This
installs the Upgrade.exe into the
C:\Landmark\EDT_2003.14\ARIES\Programs directory.

When using an older ARIES database in which the PROJList


table has not been updated for old projects, you may receive the
error No Master Record Found. This error is caused by the
INTKEY and PROPNUM being different in the original database.
To prevent this error from occurring, update any projects in
which the INTKEY and PROPNUM do not match by using the
Upgrade.exe tool and check the Update ProjectList Table option
when the original database is upgraded prior to migration.

See page 34 for instruction on how to use this tool.

ARIES to EDM Migration Tool

About ARIES to EDM Upgrade Tool


The ARIES to EDM Migration tool migrates ARIES standalone data
into a new EDM instance.

Locating and Installing the ARIES to EDM Migration Tool


To install the ARIES to EDM Migration tool you must select the
Production and Economics Data Migration tool from the select
components list during the installation process. This installs the

56 Upgrading ARIES & TOW/cs Standalone Databases R2003.14


Landmark EDM Production and Economics Database & Migration Guide

ARIESTOEDM.exe into the


C:\Landmark\EDT_2003.14\EDM\Data Migration folder.

The ARIES to EDM Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
ARIES to EDM Migration.

R2003.14 Upgrading ARIES & TOW/cs Standalone Databases 57


EDM Production and Economics Database & Migration Guide Landmark

Converting Standalone ARIES and Tow/cs Databases

AFS
Original

1st Upgrade using production_to_2003.11.exe


2nd Migrated data using AFSDATAMigration.exe

3rd Create ARIES EDM with DB_Create.exe

4th Upgrade ARIES with Upgrade.exe to get data to 2003.4.1

5th Migrate ARIES from standalone to EDM database


using ARIESTOEDM.exe.

6th Merge ARIES into EDM database using ARIES


functionality

7th Upgrade the EDM 2003.11 database to an EDM 2003.14


database using the 2003_14_0_0_Patch_Oracle.exe or the
2003_14_0_0_Patch_SQL.exe.

Verify Data
7th Optional step. Cleaup and/or delete ARIES Standalone database
8th Optional step. Cleanup and/or delete EDM ARIES database

58 Upgrading ARIES & TOW/cs Standalone Databases R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Initially, this process mirrors that used to migrate data for the individual
applications.

Above is a schematic illustrating the upgrade and migration.

1. Upgrade the original AFS database using the


production_to_2003.11.exe.

2. Migrate your AFS data using the AFSDATAMIGRATION.exe.

3. Use the db_create.exe tool to create a separate EDM ARIES


database.

Since EDM is more rigid than prior ARIES releases, Master


items to match similar item in the EDM table. If desired to
include more master items, add any user defined items to
ECON_EXTENSION_UXEXT
Review the EDM database and compare to your existing ARIES
database. Specifically, compare master table (AC_PROPERTY)
to EDM master tables (ECON_PROPERTY,
ECON_EXTENSION).
Assure that the first four ECOPHASES match (1. OIL (i.e. 370),
2. GAS (371), 3. CND (372), and 4. OWG (373). Some users
have flipped NGL and CND, the NGL (374) should be 5th phase
(not the 3rd). If not corrected, errors will occur when the data is
migrated.

4. Upgrade the ARIES Standalone database to 2003.41 using the


upgrade.exe. See page 33 for more information.

5. Migrate ARIES data from the ARIES standalone database into the EDM
ARIES database using the ARIESTOEDM.exe.

Once you have migrated the ARIES data, use the ARIES Data
Transporter to copy ARIES data into the EDM TOW/cs database

6. Launch ARIES and connect to EDM ARIES database

7. Select File > New Project, Click Run Query icon to load all
properties in DBS.

8. Select File > Data Transporter.

R2003.14 Upgrading ARIES & TOW/cs Standalone Databases 59


EDM Production and Economics Database & Migration Guide Landmark

9. Check Columns to verify that they match.

Note

The Data Transporter only can copy data within a given project. To maintain and
keep the hierarchy of each project, each project must be transported separately or
user must use Full DBS and re-create Project listing in the EDM TOW database.

10. Clean up and or delete ARIES standalone database.

11. Clean up and or delete EDM ARIES standalone database.

60 Upgrading ARIES & TOW/cs Standalone Databases R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Upgrading your EDM 2003.11 database to an EDM


2003.14 database

Next, you will upgrade your 2003.11 Oracle or SQL database to a


2003.14 Oracle or SQL database

Upgrade Procedures

Run Automated Oracle Upgrade


These steps should be used for clients that have already established the
EDM 2003.11 database.

Oracle
1. From the
c:\Landmark\EDT_2003.14\EDM\Updates\Oracle
directory, execute the 2003_14_0_0_Patch_Oracle.exe
self extracting executable.

The following dialog appears:

2. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into the


TEMP directory for execution.

R2003.14 Upgrading ARIES & TOW/cs Standalone Databases 61


EDM Production and Economics Database & Migration Guide Landmark

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

3. Choose Run Automated to run the upgrade program in automatic


mode.

The following dialog appears:

4. Enter the requested database login and connection parameters


information. You will need to login as the schema owner to
perform this upgrade.

5. Click OK.

If the ARIES or TOW/cs version is incorrect, a message will be


displayed and the upgrade process will abort.

6. If prompted to save the log file, click the Yes button and select a
destination directory.

7. Review the log files for errors.

62 Upgrading ARIES & TOW/cs Standalone Databases R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The database is ready to use.

Run Automated SQL Server Upgrade

SQLServer
1. From the c:\Landmark\EDT_2003.14\EDM\Updates\
SQLServer directory, execute the
2003_14_0_0_Patch_SQL.exe self extracting executable.

The following dialog appears:

2. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into the


TEMP directory for execution.

3. Click the Setup button to begin the upgrade process.

The WinZip Self-Extractor unzips the upgrade scripts into a


TEMP directory for execution.

Next, the Database Upgrade Program launches. A text window


describes the upgrade scripts that will run.

R2003.14 Upgrading ARIES & TOW/cs Standalone Databases 63


EDM Production and Economics Database & Migration Guide Landmark

4. Choose Run Automated to run the upgrade program in automatic


mode.

The following dialog appears:

5. Enter the requested database login and connection parameters


information. You will need to login as System Administrator SA
to perform this upgrade.

6. Click OK.

If the AFS or ARIES version is incorrect, a message will be


displayed and the upgrade process will abort.

7. If prompted to save the log file, click the Yes button and select a
destination directory.

8. Review the log files for errors.

The database is ready to use.

64 Upgrading ARIES & TOW/cs Standalone Databases R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Appendix A:
Migration Tables and Column Mappings

AFS to EDM Table Migration Mapping

AFS to EDM table migration mapping is described in the following


spreadsheet. The spreadsheet also explains actions performed by the
cleanup script.

Action during New EDM Production


Old Table Action during cleanup
migration Table

XREF table created to Table dropped TOWDM_VC_WELLBOR


track ID's E_XREF

Populated with default MD_SITE_TIGHT_GROU


data P

Populated with default CD_POLICY


data

Populated with default CD_PROJECT


data

AC_DETAIL data migrated to new table Old table dropped DW_ECON_DETAIL

AC_ECONOMIC data migrated to new table Old table dropped AR_ECONOMIC

AC_ECOSUM Existing table renamed Propnum column dropped, AR_ECON_SUMMARY


Primary Key added.

AC_MONTHLY data migrated to new table Old table dropped DW_ECON_MONTHLY

AC_NOTES data migrated to new table Old table dropped AR_NOTES

AC_ONELINE data migrated to new table Old table dropped DW_ECON_ONELINE

AC_OWNER data migrated to new table Old table dropped DW_ECON_OWNER

AC_PZFCST data migrated to new table Old table dropped DW_ECON_PZFCST

AC_RATIO data migrated to new table Old table dropped AR_RATIO

AC_RESERVE data migrated to new table Old table dropped AR_RESERVE

R2003.14 Appendix A: Migration Tables and Column Mappings 65


EDM Production and Economics Database & Migration Guide Landmark

Action during New EDM Production


Old Table Action during cleanup
migration Table

AC_SCENARIO data migrated to 2 new Old table dropped EDM_SCENARIO


tables

EDM_SCENARIO_DTL

AC_SETUP Existing table renamed AR_SETUP

AC_SETUPDATA Existing table renamed AR_SETUPDATA

AC_TEST data migrated to new table Old table dropped AR_TEST

AC_VIPDATA data migrated to new table Old table dropped AR_VIPDATA

AC_WELL data migrated to new table Old table dropped AR_WELL

ARCURVE data migrated to new table Old table dropped ARCURVE

ARFILTERS data truncated ARFILTERS

ARLOCK data truncated ARLOCK

ARSYSCOL old data will be truncated. ARSYSCOL


Table is repopulated with
new metadata.

ARSYSTBL old data will be truncated. ARSYSTBL


Table is repopulated with
new metadata.

BATCHMACROS Existing table renamed ARBATCHMACROS

BKTITLES Existing table renamed ARBKTITLES

CD_GROUP Merge data with GROUP Old table dropped EDM_GROUP_MEMBERS

CD_GROUP_ME Merge data with GROU- Old table dropped EDM_GROUP


MBER PLIST

DBSLIST Existing table renamed ARDBSLIST

ECOPHASE Existing table renamed, ARECOPHASE


old data is dropped and
table is repopulated with
metadata.

ECOSTRM Existing table renamed, ARECOSTRM


old data is dropped and
table is repopulated with
metadata.

GROUPLIST Merge data with Old table dropped EDM_GROUP_MEMBERS


CD_GROUP_MEMBER

66 Appendix A: Migration Tables and Column Mappings R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Action during New EDM Production


Old Table Action during cleanup
migration Table

GROUPS Merge data with Old table dropped EDM_GROUP


CD_GROUP

GROUPTABLE data migrated to new table ARGROUPTABLE

GROUPTEST data migrated to new table Old table dropped ARGROUPTEST

PROJECT Existing table renamed ARPROJECT

PROJLIST data migrated to new table Old table dropped ARPROJLIST

PZCALCINS Existing table renamed ARPZCALCINS

RMSBKDELTA data migrated to new table Old table dropped RMS_BKDELTA

RMSBKMEMO data migrated to new table Old table dropped RMS_BKMEMO

RMSBKPROD data migrated to new table Old table dropped RMS_BKPROD

RMSCHANGE Existing table renamed RMS_CHANGE

RMSDEFMEMO data migrated to new table Old table dropped RMS_DEFMEMO

RMSEIA data migrated to new table Old table dropped RMS_EIA

RMSEIAHEADER data migrated to new table Old table dropped RMS_EIAHEADER

RMSEIAID Existing table renamed RMS_EIAID

RMSNONBK- data migrated to new table Old table dropped RMS_NONBKMEMO


MEMO

RMSPHASE Existing table renamed RMS_PHASE

RMSREPORT Truncate data and drop RMS_REPORT


table

RMSRESCAT Existing table renamed RMS_RESCAT

RMSRESERVES data migrated to new table Old table dropped RMS_RESERVES

RMSRPT Truncate data and drop RMS_RPT


table

RMSRPTHDR Truncate data and drop RMS_RPTHDR


table

RMSSCENARIO data migrated to new table Old table dropped RMS_SCENARIO

RMSSECURITY Existing table renamed RMS_SECURITY

Old Table Action during migration Action during cleanup New EDM Production Table

R2003.14 Appendix A: Migration Tables and Column Mappings 67


EDM Production and Economics Database & Migration Guide Landmark

Action during New EDM Production


Old Table Action during cleanup
migration Table

SELFILTERS data migrated to new table Old table dropped ARSELFILTERS

SORTFILTERS data migrated to new table Old table dropped ARSORTFILTERS

SORTTITLE Existing table renamed ARSORTTITLE

SUMPROPS data migrated to new table Old table dropped ARSUMPROPS

TBLSETS Existing table renamed ARTBLSETS

VC_ARIES_WC_ Migrate ARIES properties Old table dropped DW_DAILY_PROD


DD only

VC_ARIES_WC_ Migrate ARIES properties Old table dropped DW_MONTHLY_PROD


MM only

VC_BORE_CHRO Old table dropped


N

VC_CEMENT Old table dropped

VC_COMPLETIO Migrate AR*** entities to Drop columns NEW_ID, ECON_PROPERTY


N_RF ECON_PROPERTY NEW_TYPE and alter
DWIGHTS_CD column size

data migrated to new table ECON_EXTENSION

VC_DIAMETERS Old table dropped

VC_DOWNHOLE Old table dropped


_INVENTORY

VC_DRILL_BITS Old table dropped

VC_EQUIPMENT EQUIP_ID in the


VC_EQUIPMENT is pop-
ulated during the migration
process.

VC_EQUIP_TEST Add TEST_ID column to


table and populate with
ID's

VC_LOCATION VC_LOCATION is popu- CD_SITE_SOURCE


lated with SITE_ID, For
every record in the
VC_LOCATION table
there will be a new record
created in the
CD_SITE_SOURCE

VC_PACKER Old table dropped

68 Appendix A: Migration Tables and Column Mappings R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Action during New EDM Production


Old Table Action during cleanup
migration Table

VC_PERFORATIO Old table dropped


NS

VC_PROD_TEST Add TEST_ID column to


table and populate with
ID's

VC_PROPERTY Alter LEGAL_DS column


size.

VC_RODS Old table dropped

VC_STRING_SU Old table dropped


M

VC_SURFACE_W Old table dropped


ORK

VC_USER_CONFI All records in the MD_SITE_USER


G VC_USER_CONFIG table
create a new record in the
MD_SITE_USER table. If
the user PUBLICUSERS
does not exist it is created
as a group. All records cre-
ated from the
VC_USER_CONFIG are
assigned to the PUBLI-
CUSERS group.

VC_WELLBORE LOC_SK will be com- Old table dropped CD_SITE_SOURCE


pared to LOC_SK from the
VC_LOCATION table. If
they match the SITE_ID
will be returned, if they
don't a new record is gen-
erated in the
CD_SITE_SOURCE

Either matched record CD_WELL_SOURCE


from the
CD_SITE_SOURCE or
newly generated record is
used to populate table.

Data is migrated and CD_WELLBORE


merged with SITE_ID
from
CD_WELL_SOURCE

R2003.14 Appendix A: Migration Tables and Column Mappings 69


EDM Production and Economics Database & Migration Guide Landmark

Action during New EDM Production


Old Table Action during cleanup
migration Table

WELL_ID is generated CD_DATUM


from the
CD_WELL_TABLE.
DATUM_ID is automati-
cally generated.

VC_WELLCOMP LOC_SK will be com- Alter DWIGHTS_CD col- CD_WELL_SOURCE


pared find an existing umn size.
SITE_ID. If a SITE_ID
exists it will be used other-
wise a new record is gener-
ated in the
CD_SITE_SOURCE

Data is migrated and CD_WELLBORE


merged with SITE_ID
from
CD_WELL_SOURCE

A new record is generated CD_COMPLETION


in CD_COMPLETION for
every record in
VC_WELLCOMP.

VC_WORKOVER Old table dropped

70 Appendix A: Migration Tables and Column Mappings R2003.14


Landmark EDM Production and Economics Database & Migration Guide

AFS to EDM Column Migration Mappings

The following spreadsheets define the default records entered by the


AFS Migration Utility and some high level column mappings.

EDM Table Function Columns Being Column Values


Populated
MD_SITE_TIGHT_GROUP Used to specify the tight tight_group_id T0001
groups that are used to tight_group_name UNRESTRICTED
control well access. The
migration process will create
an entry for a new tight
group that will be associated
with every well that the
migration creates.
CD_POLICY The migration process will policy_id PRDPL00000
check to see if a policy exists
customer_name pulled from
for a given Company Name,
VC_TOW_REF.
which is pulled from
ref_ds where ref_no =
VC_TOW_REF. If a policy
9003.
does not exist for this name
If the 9003 reference is
the process will created an
not found the word
entry for a new policy that
Company will be
will be associated with a new
used.
project that will get created.
The column section shows create_date Current system date
the values that will be time
inserted into the new record create_user_id User ID as entered into
the login screen
create_app_id AFSDATAMIGRATION
CD_PROJECT The migration process will project_id PRDPJ00000
create an entry for a new project_name Production
project that will be
associated with each new site policy_id PRDPL00000
that is created. The column create_date Current systemdate
section shows the values that time
will be inserted into the new
record. The process will create_user_id User ID as entered into
make sure that a project with the login screen
the name Production does create_app_id AFSDATAMIGRATION
not already exist before
adding the new record. If
such a project does exist, the
project_id associated will be
used in the rest of the
migration.

R2003.14 Appendix A: Migration Tables and Column Mappings 71


EDM Production and Economics Database & Migration Guide Landmark

Migrating Modified ARIES Tables

The AFS to EDM Migration Utility has three external and editable
script files that are automatically run during the migration process and
migrate the modified AC_Monthly, AC_Detail, and AC_Oneline
tables.

The script files are located in the same directory as the AFS Migration
Utility executable.

c:\Landmark\EDT\EDM\DataMigration\
SQLStmt_AC_DETAIL.SQL.
c:\Landmark\EDT\EDM\DataMigration\
SQLStmt_AC_MONTHLY.SQL
c:\Landmark\EDT\EDM\DataMigration\
SQLStmt_AC_ONELINE.SQL
c:\Landmark\EDT\EDM\DataMigration\
SQLStmt_AC_ONELINE_ORACLE.SQL.

If these ARIES tables have been modified and no longer follow


the original ARIES format they will not be migrated properly
if the script files are not updated to reflect these changes.

72 Appendix A: Migration Tables and Column Mappings R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Appendix B:
ARIES Table Changes

Traditional ARIES Table Changes

The following Table changes have been made to the Traditional ARIES
Database. There are 56 changes in total. 17 tables have not been
changed.

Traditional ARIES tables renamed for the EDM datamodel

Old Table Name New Table Name

AC_DAILY DW_DAILY_PROD

AC_DETAIL DW_ECON_DETAIL

AC_ECONOMIC AR_ECONOMIC

AC_ECOSUM AR_ECON_SUMMARY

AC_MONTHLY DW_ECON_MONTHLY

AC_NOTE AR_NOTES

AC_ONELINE DW_ECON_ONELINE

AC_OWNER DW_ECON_OWNER

AC_PRODUCT DW_MONTHLY_PROD

AC_PROPERTY ECON_PROPERTY

AC_PZFCST DW_ECON_PZFCST

AC_RATIO AR_RATIO

AC_RESERVES AR_RESERVE

AC_SCENARIO EDM_SCENARIO_DTL

AC_SETUP AR_SETUP

AC_SETUPDATA AR_SETUPDATA

R2003.14 Appendix B: ARIES Table Changes 73


Landmark

Old Table Name New Table Name

AC_TEST AR_TEST

AC_WELL AR_WELL

BATCHMACROS ARBATCHMACROS

BKTITLES ARBKTITLES

DBSLIST ARDBSLIST

ECOPHASE ARECOPHASE

ECOSTRM ARECOSTRM

GROUPLIST EDM_GROUP_MEMBERS

GROUPS EDM_GROUP

GROUPTABLE ARGROUPTABLE

GROUPTEST ARGROUPTEST

PROJECT ARPROJECT

PROJLIST ARPROJLIST

PZCALCINS ARPZCALCINS

RMSBKDELTA RMS_BKDELTA

RMSBKMEMO RMS_BKMEMO

RMSBKPROD RMS_BKPROD

RMSCHANGE RMS_CHANGE

RMSDEFMEMO RMS_DEFMEMO

RMSEIA RMS_EIA

RMSEIAHEADER RMS_EIAHEADER

RMSEIAID RMS_EIAID

RMSNONBKMEMO RMS_NONBKMEMO

RMSPHASE RMS_PHASE

RMSREPORT RMS_REPORT

RMSRESCAT RMS_RESCAT

RMSRESERVES RMS_RESERVES

RMSRPT RMS_RPT

74 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Old Table Name New Table Name

RMSRPTHDR RMS_RPTHDR

RMSSCENARIO RMS_SCENARIO

RMSSECURITY RMS_SECURITY

SELFILTERS ARSELFILTERS

SORTFILTERS ARSORTFILTERS

SORTTITLE ARSORTTITLE

SUMPROPS ARSUMPROPS

TBLSETS ARTBLSETS

New ARIES Tables (4 Tables)

Table Name Description

ECON_EXTENSION An extension of the ECON_PROPERTY table

ECON_EXTENSION_UEXT A further, user-defined extension of the


ECON_EXTENSION table.

EDM_SCENARIO A new table serving as a parent of the


EDM_SCENARIO_DTL table.

AR_VIPDATA This table previously existed in the AFS


datamodel, but was not a standard ARIES
table.

New ARIES International Tables (2 Tables)

Table Name Description

ARI_SCRIPT The storage location for ARIES International


scripts.

ARI_SCRIPTHDR A reference table that cross - references the


ARIES International scripts to the storage
table (ARI_SCRIPT).

R2003.14 Appendix B: ARIES Table Changes 75


Landmark

Unchanged ARIES Tables


ARCURVE
ARENDDATE
ARFILTER
ARFILTERS
ARGRAPH
ARGRAPHCURVE
ARIESSCHEMAVERSION
ARLOCK
ARLOOKUP
ARPLOT
ARREPORTFORMAT
ARSTREAM
ARSYSCOL
ARSYSTBL
ARTREND
ARUNITS
ARUNITTYPES

ARIES AFS Table Changes

Renamed Tables
All of the same Standard ARIES tables were Renamed in AFS except
for the following:

Standard ARIES Table AFS Table Name New EDM Table Name

AC_DAILY VC_ARIES_WC_DD DW_DAILY_PROD

AC_PRODUCT VC_ARIES_WC_MM DW_MONTHLY_PROD

Not a Standard ARIES Table AC_VIPDATA AR_VIPDATA

AC_PROPERTY) VC_COMPLETION_RF VC_COMPLETION_RF


(Was not renamed)

76 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

New EDM Tables

New Table Name Function

ECON_PROPERTY added to separate ARIES ECON


properties from TOW ACMP
properties.

ECON_EXTENSION an extension of the


ECON_PROPERTY table

ECON_EXTENSION_UEXT a further user extension of the


ECON_EXTENSION table

EDM_SCENARIO a new table, a parent of the


EDM_SCENARIO_DTL table

Merged ARIES Tables


The GROUP and GROUPLIST tables were merged with the
CD_GROUP and CD_GROUP_MEMBERS tables to create the new
EDM tables EDM_GROUP and EDM_GROUP_MEMBERS tables
respectively.

ARIES Column Changes

PROPNUM to PDEN_ID
In the following ARIES tables, the PROPNUM was replaced by the
new PDEN_ID column.

Traditional ARIES Table EDM Table

AC_ECOSUM AR_ECON_SUMMARY

AC_ECONOMIC AR_ECONOMIC

AC_NOTE AR_NOTES

AC_RATIO AR_RATIO

AC_RESERVES AR_RESERVE

AC_TEST AR_TEST

Not a Standard ARIES Table AR_VIPDATA

R2003.14 Appendix B: ARIES Table Changes 77


Landmark

Traditional ARIES Table EDM Table

AC_WELL AR_WELL

AC_DAILY DW_DAILY_PROD

AC_DETAIL DW_ECON_DETAIL

AC_MONTHLY DW_ECON_MONTHLY

AC_ONELINE DW_ECON_ONELINE

AC_OWNER DW_ECON_OWNER

AC_PZFCST DW_ECON_PZFCST

AC_PRODUCT DW_MONTHLY_PROD

Not a Standard ARIES Table ECON_EXTENSION

Not a Standard ARIES Table ECON_EXTENSION_UEXT

AC_PROPERTY ECON_PROPERTY

RMSBKDELTA RMS_BKDELTA

RMSBKMEMO RMS_BKMEMO

RMSBKPROD RMS_BKPROD

RMSEIAHEADER RMS_EIAHEADER

RMSNONBKMEMO RMS_NONBKMEMO

RMSREPORT RMS_REPORT

RMSRESERVES RMS_RESERVES

RMSRPT RMS_RPT

PDEN_TYPE Added
In the following ARIES tables, the new column PDEN_TYPE was
added.

Traditional ARIES Table New ARIES Table

AC_ECOSUM AR_ECON_SUMMARY

AC_ECONOMIC AR_ECONOMIC

AC_NOTE AR_NOTES

78 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Traditional ARIES Table New ARIES Table

AC_RATIO AR_RATIO

AC_RESERVES AR_RESERVE

AC_TEST AR_TEST

Not a Standard ARIES Table AR_VIPDATA

AC_WELL AR_WELL

AC_DAILY DW_DAILY_PROD

AC_DETAIL DW_ECON_DETAIL

AC_MONTHLY DW_ECON_MONTHLY

AC_ONELINE DW_ECON_ONELINE

AC_OWNER DW_ECON_OWNER

AC_PZFCST DW_ECON_PZFCST

AC_PRODUCT DW_MONTHLY_PROD

Not a Standard ARIES Table ECON_EXTENSION

Not a Standard ARIES Table ECON_EXTENSION_UEXT

RMSBKDELTA RMS_BKDELTA

RMSBKMEMO RMS_BKMEMO

RMSBKPROD RMS_BKPROD

RMSEIAHEADER RMS_EIAHEADER

RMSNONBKMEMO RMS_NONBKMEMO

RMSREPORT RMS_REPORT

RMSRESERVES RMS_RESERVES

RMSRPT RMS_RPT

AC_ECOSUM (AR_ECON_SUMMARY) Changes


As noted above the AC_ECOSUM table has been renamed
AR_ECON_SUMMARY. Along with this name change, the following
columns have been added.

REMARK
CREATE_DATE

R2003.14 Appendix B: ARIES Table Changes 79


Landmark

CREATE_USER_ID
UPDATE_DATE
UPDATE_USER_ID
CREATE_APP_ID
UPDATE_APP_ID

Column changes made to the AR_VIPDATA table


The following columns that were included in this New EDM table

QUALIFIER
PROD_DT
OIL
GAS
WTR
WTRINJ
GASINJ
PRESS
PTYPE

Column changes made to the ARECOPHASE table


The column KWORD was Renamed to KEYWORD

New columns that were added in EDM (compared to old AC_OWNER


table)

REMARK
CREATE_DATE
CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID

Column changes made to the ARECOSTRM table


Columns that were Renamed

The column ARRAY renamed to STREAM_TYPE


The column ITEM_NUM renamed to STREAM_NUM

New columns that were added in EDM (compared to old AC_OWNER


table)

80 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

REMARK
CREATE_DATE
CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID

Column changes made to the ARGROUPTEST table


Columns that were Renamed

The column GROUP_KEY renamed to GROUP_ID


The column MEMBER renamed to CHILD_ID

New column CHILD_TYPE was added to EDM (compared to old


GROUPTEST table)

Column changes made to the AR_LOCK table


The column TBL_SET was Renamed to TABLE_SET

Column changes made to the DW_DAILY_PROD table(


Columns that were Renamed

The column D_DATE renamed to PROD_DT


The column OIL renamed to VO_OIL_PROD
The column GAS renamed to VO_GAS_PROD
The column WATER renamed to VO_WAT_PROD

New columns that were added in EDM (compared to old AC_DAILY


table) (143 items)

QA_GAS_RCV_LIFT DATA_SOURCE

QA_GAS_LIFT PT_MI_ON

QA_OIL_SALE_PIPE VO_COND_PROD

QA_OIL_SALE_TR VO_GWG_PROD

QA_OIL_SALE_BARGE VO_GCH_PROD

QA_OIL_SALE_RR VO_OIL_SALE_PIPE

R2003.14 Appendix B: ARIES Table Changes 81


Landmark

QA_OIL_SALE_INTER VO_OIL_SALE_TR

QA_OIL_SALE_INTRA VO_OIL_SALE_BARGE

WM_OILWM_GAS VO_OIL_SALE_RR

WM_WAT VO_OIL_SALE_INTER

WM_GAS_LIFT VO_OIL_SALE_INTRA

WT_OIL VO_OIL_FLD_OTHER

WT_GAS VO_OIL_BEG_INV

WT_WAT VO_OIL_END_INV

WT_GAS_LIFT VO_OIL_FLD_GLOS

WT_NEW_IND VO_OIL_INTRA_OTHER

WT_MEAS_MI VO_OIL_INTER_OIL

WT_PURP_CODE VO_OIL_RCV_TREAT

TD_OIL VO_OIL_TREAT

TD_GAS VO_WAT_RCV_TREAT

TD_WAT VO_WAT_SUPPLY

TD_GAS_LIFT VO_WAT_TREAT

QT_GAS VO_GAS_SALE_PIPE

QD_GAS VO_GAS_SALE_PLANT

QM_GAS VO_GAS_SALE_RESID

QT_GAS_LIFT VO_GAS_SALE_SPOT

QM_GAS_LIFT VO_GAS_SALE_INTER

CI_OIL VO_GAS_SALE_INTRA

CI_WAT VO_GAS_INTRA_GL

CI_GAS VO_GAS_INTRA_FUEL

CI_SUL VO_GAS_INTRA_FLARE

CI_CO2 VO_GAS_INTRA_OTHER

WI_OIL VO_GAS_INTER_GL

WI_WAT VO_GAS_INTER_FUEL

WI_GAS VO_GAS_INTER_FLARE

82 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

WI_SUL VO_GAS_INTER_OTHER

WI_CO2 VO_GAS_FLD_FUEL

CHOKE VO_GAS_FLD_FLARE

STROKES VO_GAS_FLD_GLOS

CASING_PRESS1 VO_GAS_FLD_OTHER

CASING_PRESS2 VO_GAS_PLT_FUEL

CASING_PRESS3 VO_GAS_PLT_FLARE

CASING_PRESS4 VO_GAS_PLT_SHRNK

TUBING_PRESS VO_GAS_PLT_GLOS

VO_USER_DEF1 VO_GAS_PLT_OTHER

VO_USER_DEF2 VO_GAS_RCV_LIFT

VO_USER_DEF3 VO_GAS_LIFT

VO_USER_DEF4 QA_GAS_SALE_PIPE

VO_USER_DEF5 QA_GAS_SALE_PLANT

VOL_ORIGIN QA_GAS_SALE_RESID

QA_GAS_PROD QA_GAS_SALE_SPOT

QA_GCH_PROD QA_GAS_SALE_INTER

QA_GWG_PROD QA_GAS_SALE_INTRA

USER_DEF_TYPE1 QA_GAS_INTRA_GL

USER_DEF_TYPE2 QA_GAS_INTRA_FUEL

USER_DEF_TYPE3 QA_GAS_INTRA_FLARE

USER_DEF_TYPE4 QA_GAS_INTRA_OTHER

USER_DEF_TYPE5 QA_GAS_INTER_GL

VO_LIQ_OUOM QA_GAS_INTER_FUEL

VO_GAS_OUOM QA_GAS_INTER_FLARE

QA_GAS_OUOM QA_GAS_INTER_OTHER

QA_OIL_OUOM QA_GAS_FLD_FUEL

RATE_OUOM QA_GAS_FLD_FLARE

PR_OUOM QA_GAS_FLD_GLOS

R2003.14 Appendix B: ARIES Table Changes 83


Landmark

CREATE_DATE QA_GAS_FLD_OTHER

CREATE_USER_ID QA_GAS_PLT_FUEL

UPDATE_DATE QA_GAS_PLT_FLARE

UPDATE_USER_ID QA_GAS_PLT_SHRNK

REMARK QA_GAS_PLT_GLOS

DB_OWN_SK QA_GAS_PLT_OTHER

CREATE_APP_ID UPDATE_APP_ID

Note

The columns and table structure of the above is virtually the same as
the TOW/cs PDM_DAILY_PROD table.

Column changes made to the DW_ECON_DETAIL table


In the three Economic Output tables (Detail, Monthly, and Oneline),
stream numbers were converted to stream names.

Columns that were Renamed (50 items)

Traditional ARIES Column Name New Column Name

Period End_Date

S345 OIL_WELL_MOS

S346 GAS_WELL_MOS

S349 PROD_MOS

S370 G_OIL_PROD

S371 G_GAS_PROD

S372 G_NGL_PROD

S427 G_OIL_REV

S428 G_GAS_REV

S429 G_NGL_REV

S442 G_TOT_REV

84 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Traditional ARIES Column Name New Column Name

S815 N_OIL_SOLD

S816 N_GAS_SOLD

S817 N_NGL_SOLD

S846 N_OIL_REV

S847 N_GAS_REV

S848 N_NGL_REV

S861 N_PROD_REV

S887 N_TOT_SEV

S1062 N_OPC

S1065 N_TOT_OPC_ADV

S1069 BFIT_OP_INC

S1100 BFIT_LESS_LOANS

S1101 BFIT_NET_CF

S1134 N_TANG_INV

S1182 N_LSHLD_INV

S1183 N_EQTY_INV

S1184 N_BOR_INV

S1185 N_RISK_INV

S1186 N_INV_WO_RISK

S1187 N_INV_EQTY_RISK

S1208 N_DEPR_TANG

S1236 N_EXP_INV

S1263 N_DEPL_TAKEN

S1264 TAXABLE_INCOME

S1265 FEDERAL_TAX

S1266 INV_TAX_CREDIT

S1269 INCOME_TAX_PAID

S1270 AFIT_BEFORE_LOANS

R2003.14 Appendix B: ARIES Table Changes 85


Landmark

Traditional ARIES Column Name New Column Name

S1301 PRINCIPAL_PAID

S1302 INTEREST_PAID

S1303 INTEREST_CAP

S1305 INV_SALV

S1306 INV_ABDN

S1307 AFIT_LESS_LOANS

S1308 AFIT_NET_CF

S1314 PW_BFIT_LESS_LOANS

S1315 PW_AFIT_LESS_LOANS

S1316 PW_INV

S1317 PW_BFIT_NET_CF

New columns that were added in EDM (compared to old AC_DETAIL


table)(23 items)

G_WAT_PROD
G_OIL_SOLD
G_GAS_SOLD
G_NGL_SOLD
G_TOT_SEV
G_OPC
G_TOT_OPC_ADV
WI_TANG_INV
WI_INT_INV
WI_OIL_SOLD
WI_GAS_SOLD
WI_NGL_SOLD
N_CROWN_ROY
N_MINERAL_TAX
N_PROD_ROY_PAID
N_PROD_ROY_REC
N_RES_ROY_PAID
N_RES_ROY_REC
N_NPI_PAID
N_NPI_OWNED
N_INT_INV
N_DEPR_INTAN
PW_AFIT_NET_CF

86 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Columns that were Removed and not included in the EDM data model
(5 items)

S872
S873
S874
S892
S1064

Note

The above columns plus other items can be added to EDM using the
DW_ECON_DETAIL_UEXT table if created.

Column changes made to the DW_ECON_MONTHLY table (29 items)


In the three Economic Output tables (Detail, Monthly, and Oneline),
stream numbers were converted to stream names.

Columns that were Renamed (5 items)

Traditional ARIES Column Name New ARIES Column


Name

OUTDATE END_DATE

"S370" "G_OIL_PROD

"S371" "G_GAS_PROD

"S1065" "N_TOT_OPC_ADV

"S1069" "BFIT_OP_INC

New columns that were added in EDM (compared to old


AC_MONTHLY table)(23 items)

OIL_WELL_MOS
GAS_WELL_MOS
G_NGL_PROD
G_WAT_PROD
G_OIL_SOLD
G_GAS_SOLD
G_NGL_SOLD
G_TOT_REV
G_TOT_SEV

R2003.14 Appendix B: ARIES Table Changes 87


Landmark

G_OPC
G_TOT_OPC_ADV
WI_TANG_INV
WI_INT_INV
WI_OIL_SOLD
WI_GAS_SOLD
WI_NGL_SOLD
N_OIL_SOLD
N_GAS_SOLD
N_NGL_SOLD
N_PROD_REV
N_TOT_SEV
N_OPC
PW_BFIT_OP_INC

The S892 column was Removed and not included in the EDM data
model

Note

The above column plus other items can be added to EDM using the
DW_ECON_MONTHLY_UEXT table if created.

Column changes made to the DW_ECON_ONELINE table (173 items)


In the three Economic Output tables (Detail, Monthly, and Oneline),
stream numbers were converted to stream names.

Columns that were Renamed (58 items)

Traditional ARIES Column New ARIES Column

C370 G_OIL_PROD

C371 G_GAS_PROD

C815 N_OIL_SOLD

C816 N_GAS_SOLD

C846 N_OIL_REV

C847 N_GAS_REV

C861 N_PROD_REV

88 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Traditional ARIES Column New ARIES Column

C887 N_TOT_SEV

C1062 N_OPC

C1065 N_TOT_OPC_ADV

C1069 BFIT_OP_INC

C1100 BFIT_LESS_LOANS

C1101 BFIT_NET_CF

C1183 N_EQTY_INV

C1184 N_BOR_INV

C1185 N_RISK_INV

C1186 N_INV_WO_RISK

C1187 N_INV_EQTY_RISK

C1208 N_DEPR_TANG

C1263 N_DEPL_TAKEN

C1264 TAXABLE_INCOME

C1265 FEDERAL_TAX

C1269 INCOME_TAX_PAID

C1270 AFIT_BEFORE_LOANS

C1301 PRINCIPAL_PAID

C1302 INTEREST_PAID

C1303 INTEREST_CAP

C1308 AFIT_NET_CF

C1317 PW_BFIT_NET_CF

C1318 PW_AFIT_NET_CF

B3 PW_BFIT_03

B4 PW_BFIT_04

B5 PW_BFIT_05

B6 PW_BFIT_06

E1 BFIT_ROR_INTERP

R2003.14 Appendix B: ARIES Table Changes 89


Landmark

Traditional ARIES Column New ARIES Column

E2 AFIT_ROR_INTERP

E3 BFIT_PAYOUT

E4 AFIT_PAYOUT

E5 PW_BFIT_PAYOUT

E7 BFIT_INC_TO_INV

E8 AFIT_INC_TO_INV

M1 PW_RATE

M4 LIFE_OF_WELL

M6 REPORT_DATE

M7 PW_DATE

M16 DATE_OF_RUN

M18 G_OIL_WELLS

M19 G_GAS_WELLS

M23 G_PRIOR_CUM_OIL

M25 G_PRIOR_CUM_GAS

M31 INIT_WI

M41 INIT_NRI

M111 DS_NAME

P3 PW_RATE_03

P4 PW_RATE_04

P5 PW_RATE_05

P6 PW_RATE_06

P7 PW_RATE_07

Columns added to DW_ECON_ONELINE (111 items)

G_TANG_INV G_INT_INV

G_NGL_PROD G_WAT_PROD

G_OIL_SOLD G_GAS_SOLD

90 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

G_NGL_SOLD G_OIL_REV

G_GAS_REV G_NGL_REV

G_TOT_REV G_TOT_SEV

G_OPC G_TOT_OPC_ADV

WI_TANG_INV WI_INT_INV

WI_OIL_SOLD WI_GAS_SOLD

WI_NGL_SOLD WI_PROD_REV

WI_OPC_ADV N_NGL_SOLD

N_NGL_REV N_CROWN_ROY

N_MINERAL_TAX N_PROD_ROY_PAID

N_PROD_ROY_REC N_RES_ROY_PAID

N_RES_ROY_REC N_TOT_TAX_CREDITS

N_TANG_INV N_INT_INV

N_LSHLD_INV N_DEPR_INTAN

N_EXP_INV INV_TAX_CREDIT

N_ST_PROV_TAX INV_SALV

INV_ABDN AFIT_LESS_LOANS

PW_BFIT_LESS_LOANS PW_AFIT_LESS_LOANS

PW_INV PW_AFIT_01

PW_AFIT_02 PW_AFIT_03

PW_AFIT_04 PW_AFIT_05

PW_AFIT_06 PW_AFIT_07

PW_AFIT_08 PW_AFIT_09

PW_AFIT_10 PW_AFIT_11

PW_AFIT_12 PW_AFIT_13

PW_AFIT_14 PW_AFIT_15

PW_BFIT_01 PW_BFIT_02

PW_BFIT_07 PW_BFIT_08

PW_BFIT_09 PW_BFIT_10

R2003.14 Appendix B: ARIES Table Changes 91


Landmark

PW_BFIT_11 PW_BFIT_12

PW_BFIT_13 PW_BFIT_14

PW_BFIT_15 BONUS_AFIT_01

BONUS_AFIT_02 BONUS_AFIT_03

BONUS_AFIT_04 BONUS_AFIT_05

BONUS_AFIT_06 BONUS_AFIT_07

BONUS_AFIT_08 BONUS_AFIT_09

BONUS_AFIT_10 BONUS_AFIT_11

BONUS_AFIT_12 BONUS_AFIT_13

BONUS_AFIT_14 BONUS_AFIT_15

PW_AFIT_PAYOUT PW_BFIT_INC_TO_INV

PW_AFIT_INC_TO_INV TITLE1

TITLE2 TITLE3

TITLE4 TITLE5

TITLE6 START_DATE

G_TOT_WELLS G_ULT_OIL

G_ULT_GAS FINAL_WI

REVERSION1_YRS FINAL_NRI

INP_SETTINGS PW_RATE_01

PW_RATE_02 PW_RATE_08

PW_RATE_09 PW_RATE_10

PW_RATE_11 PW_RATE_12

PW_RATE_13 PW_RATE_14

PW_RATE_15

Columns Removed from EDM data model

C892
C1064
M17
M24

92 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Note

the above columns plus other items can be added to EDM using the
DW_ECON_ONELINE_UEXT table if created.

Column changes made to the DW_ECON_OWNER table (11 items)


Columns that were Renamed

Traditional ARIES Column Name New ARIES Column Name

PHASENAME PHASE_NAME

STARTDATE START_DATE

OWNERNAME OWNER_NAME

UNITS INTEREST_TYPE

Columns Added in EDM (compared to old AC_OWNER table)


REMARK
CREATE_DATE
CREATE_USER_ID
UPDATE_DATE
UPDATE_USER_ID
CREATE_APP_ID
UPDATE_APP_ID

Column changes made to the DW_MONTHLY_PROD table(160 items)


Columns that were Renamed

Traditional ARIES Column New ARIES Column

"P_DATE" "PROD_DT

"OIL" "VO_OIL_PROD

"GAS" "VO_GAS_PROD

"WATER" "VO_WAT_PROD

R2003.14 Appendix B: ARIES Table Changes 93


Landmark

Columns Added in EDM compared to AC_PRODUCT table (156 items)


DATA_SOURCE PT_MI_ON

VO_COND_PROD VO_GAS_ALLOWABLE

VO_OIL_BEG_INV VO_OIL_END_INV

VO_OIL_INTER_OIL VO_OIL_INTRA_OTHER

VO_OIL_SALE_INTER VO_OIL_SALE_INTRA

VO_OIL_SALE_TR VO_OIL_TREAT

VO_WAT_TREAT VO_GAS_SALE_INTER

VO_GAS_SALE_PLANT VO_GAS_SALE_RESID

VO_GAS_INTER_FUEL VO_GAS_INTER_GL

VO_GAS_INTRA_FUEL VO_GAS_INTRA_GL

VO_GAS_FLD_FUEL VO_GAS_FLD_GLOS

VO_GAS_PLT_FUEL VO_GAS_PLT_GLOS

VO_GAS_LIFT VO_GAS_RCV_LIFT

QA_GWG_PROD QA_GAS_SALE_INTER

QA_GAS_SALE_PLANT QA_GAS_SALE_RESID

QA_GAS_INTER_FUEL QA_GAS_INTER_GL

QA_GAS_INTRA_FUEL QA_GAS_INTRA_GL

QA_GAS_FLD_FUEL QA_GAS_FLD_GLOS

QA_GAS_PLT_FUEL QA_GAS_PLT_GLOS

QA_GAS_LIFT QA_GAS_RCV_LIFT

QA_OIL_SALE_INTRA QA_OIL_SALE_PIPE

WM_GAS WM_GAS_LIFT

WT_GAS WT_GAS_LIFT

TD_GAS TD_GAS_LIFT

QD_GAS QM_GAS

QT_GAS_LIFT CI_CO2

CI_SUL CI_WAT

PR_TUB_MAX PR_CAS1_AVG

94 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

PR_CAS4_AVG PR_CAS1_MIN

PR_CAS4_MIN PR_CAS1_MAX

PR_CAS4_MAX PT_DD_ON

PT_DD_DOWN PT_DD_DOWN_CONS

WI_OIL WI_SUL

VO_USER_DEF2 VO_USER_DEF3

VOL_ORIGIN USER_DEF_TYPE1

USER_DEF_TYPE4 USER_DEF_TYPE5

QA_GAS_OUOM QA_OIL_OUOM

CREATE_DATE CREATE_USER_ID

REMARK DB_OWN_SK

VO_OIL_ALLOWABLE TOT_NO_WELL

VO_GWG_PROD VO_GCH_PROD

VO_OIL_FLD_OTHER VO_OIL_FLD_GLOS

VO_OIL_SALE_BARGE VO_OIL_RCV_TREAT

VO_OIL_SALE_RR VO_OIL_SALE_PIPE

VO_WAT_SUPPLY VO_WAT_RCV_TREAT

VO_GAS_SALE_PIPE VO_GAS_SALE_INTRA

VO_GAS_INTER_FLARE VO_GAS_SALE_SPOT

VO_GAS_INTRA_FLARE VO_GAS_INTER_OTHER

VO_GAS_FLD_FLARE VO_GAS_INTRA_OTHER

VO_GAS_PLT_FLARE VO_GAS_FLD_OTHER

VO_GAS_PLT_SHRNK VO_GAS_PLT_OTHER

QA_GCH_PROD QA_GAS_PROD

QA_GAS_SALE_PIPE QA_GAS_SALE_INTRA

QA_GAS_INTER_FLARE QA_GAS_SALE_SPOT

QA_GAS_INTRA_FLARE QA_GAS_INTER_OTHER

QA_GAS_FLD_FLARE QA_GAS_INTRA_OTHER

QA_GAS_PLT_FLARE QA_GAS_FLD_OTHER

R2003.14 Appendix B: ARIES Table Changes 95


Landmark

QA_GAS_PLT_SHRNK QA_GAS_PLT_OTHER

QA_OIL_SALE_INTER QA_OIL_SALE_BARGE

QA_OIL_SALE_TR QA_OIL_SALE_RR

WM_WAT WM_OIL

WT_WAT WT_OIL

TD_WAT TD_OIL

QT_GAS QM_GAS_LIFT

CI_GAS CI_OIL

PR_TUB_MIN PR_TUB_AVG

PR_CAS3_AVG PR_CAS2_AVG

PR_CAS3_MIN PR_CAS2_MIN

PR_CAS3_MAX PR_CAS2_MAX

CD_EOM_DOWN PT_DT_LAST_PROD

WI_GAS WI_CO2

VO_USER_DEF1 WI_WAT

VO_USER_DEF5 VO_USER_DEF4

USER_DEF_TYPE3 USER_DEF_TYPE2

VO_GAS_OUOM VO_LIQ_OUOM

RATE_OUOM PR_OUOM

UPDATE_USER_ID UPDATE_DATE

UPDATE_APP_ID CREATE_APP_ID

VO_OIL_ALLOWABLE TOT_NO_WELL

VO_GWG_PROD VO_GCH_PROD

VO_OIL_FLD_OTHER VO_OIL_FLD_GLOS

VO_OIL_SALE_BARGE VO_OIL_RCV_TREAT

VO_OIL_SALE_RR VO_OIL_SALE_PIPE

VO_WAT_SUPPLY VO_WAT_RCV_TREAT

VO_GAS_SALE_PIPE VO_GAS_SALE_INTRA

VO_GAS_INTER_FLARE VO_GAS_SALE_SPOT

96 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

VO_GAS_INTRA_FLARE VO_GAS_INTER_OTHER

VO_GAS_FLD_FLARE VO_GAS_INTRA_OTHER

Note

The columns and table structure of the above is virtually the same as the TOW/cs
PDM_MONTHLY_PROD table.

Column changes made to the DW_ECON_PZFCST table


The column GASINPLACE was Renamed to GAS_IN_PLACE

Column changes made to the ECON_PROPERTY table


During the conversion from ARIES to EDM, the standard items within
the AC_PROPERTY table have been divided and placed into three
separate tables in the EDM data model. These new EDM tables are
ECON_PROPERTY, ECON_EXTENSION, and
ECON_EXTENSION_UEXT.

Only 9 items from the original AC_PROPERTY table are placed in the
ECON_PROPERTY table. All other migrated items to EDM are
listed in the ECON_EXTENSION table.

New columns that were added in EDM (compared to the


AC_PROPERTY table)
PROPERTY_NAME
REMARK
CREATE_DATE
CREATE_USER_ID
UPDATE_DATE
UPDATE_USER_ID
CREATE_APP_ID
UPDATE_APP_ID

R2003.14 Appendix B: ARIES Table Changes 97


Landmark

Columns that were Removed and not included in the EDM data
model
DBSKEY
PI_CODE
DW_CODE
RRCD
OIL_PUR
GAS_PUR

Column changes made to the EDM_GROUP table


Using Standard ARIES, the following changes are made in the EDM
model; however, if using an AFS database, the GROUP table and
CD_GROUP table are combined into one single table
EDM_GROUP.

Columns that were Renamed


The column "GROUP_KEY" renamed to "GROUP_ID

The column "DBSKEY" renamed to "DATA_SOURCE

The column "GROUP_TIMESTAMP" renamed to "BUILD_DATE

New columns that were added in EDM (compared to the GROUP


table)

CHILD_TYPECREATE_DATECREATE_USER_ID

CREATE_APP_IDUPDATE_DATEUPDATE_USER_ID

UPDATE_APP_ID

Column changes made to the EDM_GROUP_MEMBERS table


Using Standard ARIES, the following changes are made in the EDM
model; however, if using an AFS database, the GROUPLIST table and
CD_GROUP_MEMBERS table are combined into one single table
EDM_GROUP_MEMBERS.

Columns that were Renamed

The column "GROUP_KEY" renamed to "GROUP_ID

98 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The column "MEMBER" renamed to "CHILD_ID

New columns that were added in EDM (compared to the


GROUPLIST table)(14
OWNER
X
Y
DYNAMIC_DATA
DYNAMIC_CONFIG
CONFIG_CRITERIA
CURRENT_STATUS
REMARK
CREATE_DATE
CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID

PROP_KEY column was removed from EDM_GROUP_MEMBERS table

Column changes made to the EDM_SCENARIO table


The following columns that were included in this New EDM table

SCENARIO
DATA_SOURCE
REMARK
CREATE_DATE
CREATE_USER_ID
UPDATE_DATE
UPDATE_USER_ID
CREATE_APP_ID
UPDATE_APP_ID

Column changes made to the EDM_SCENARIO_DTL table


The column SCEN_NAME was Renamed to SCENARIO

New columns that were added in EDM (compared to the


AC_SCENARIO table)
CREATE_DATE

R2003.14 Appendix B: ARIES Table Changes 99


Landmark

CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID

Column changes made to the RMS_EIA table


New columns that were added in EDM (compared to old RMSEIA
table)

SUBDCODE
FIELDNAME

Column changes made to the RMS_EIAHEADER table


The column Operator_Code was Renamed to OPCODE

The RigFieldCodes table is an external table provided by the government


Columns included in this table which will be added by the client for
EIA

ID
ST
SUB
FLDCD
FIELD
CO
CNTY
DISC

ARIES Column Definition / Size Changes50 Total

Column changes made to the AR_ECONOMIC table


QUALIFIER column increased text size from 12 to 20 characters

Column changes made to the AR_NOTES table


NOTE_TEXT column decreased text size from 255 to 254 characters

100 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Column changes made to the AR_SETUP table


OWNER column increased text size from 12 to 30 characters

Column changes made to the AR_SETUPDATA table


LINE column decreased text size from 255 to 254 characters

Column changes made to the ARECOPHASE table


Redefined column KWORD to KEYWORD; increased text size from 3
to 20 characters

Column changes made to the ARENDDATE table


RECORD_CODE column increased text size from 8 to 20 characters

Column changes made to the ARGRAPH table


STARTPOINT column decreased text size from 80 to 32 characters

Column changes made to the ARGROUPTEST table


Redefined column GROUP_KEY to GROUP_ID; decreased text size
from 254 to 10 characters

Redefined column MEMBER to CHILD_ID; decreased text size from


15 to 10 characters

Column changes made to the ARREPORTFORMAT table


NAME column decreased text size from 255 to 254 characters

DESCRIPTION column decreased text size from 255 to 254 characters

REMARK column decreased text size from 255 to 254 characters

Column changes made to the ARPROJLIST table


INTKEY column increased text size from 12 to 20 characters

R2003.14 Appendix B: ARIES Table Changes 101


Landmark

Column changes made to the ARSELFILTERS table


OPERATORTEXT column decreased text size from 255 to 254
characters

Column changes made to the ARSUMPROPS table


SUM_KEY column decreased text size from 255 to 254 characters

NAME column decreased text size from 255 to 254 characters

Column changes made to the ARSYSCOL table


MAKEKEY column increased text size from 4 to 30 characters

Column changes made to the AR_NOTES table


NOTE_TEXT column decreased text size from 255 to 254 characters

Column changes made to the DW_ECON_ONELINE table


REPORT_DATE (M6) column was redefined from a Text to Date/
Time format

PW_DATE (M7) column was redefined from a Text to Date/Time


format

DATE_OF_RUN (M16) column was redefined from a Text to Date/


Time format

Column changes made to the ECON_PROPERTY table


FIELD column increased text size from 38 to 50 characters

OPERATOR column increased text size from 24 to 50 characters

RESERVOIR column increased text size from 20 to 50 characters

COUNTY column increased text size from 20 to 50 characters

API column decreased text size from 17 to 16 characters

CODE column increased text size from 22 to 30 characters

102 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Column changes made to the ECON_EXTENSION table


LEASE column increased text size from 36 to 40 characters

WELLID column increased text size from 6 to 10 characters

LOCATION column increased text size from 15 to 20 characters

RESCAT column increased text size from 4 to 6 characters

Column changes made to the EDM_GROUP table


Redefined column GROUP_KEY to GROUP_ID; decreased text size
from 254 to 10 characters

Redefined column MEMBER to CHILD_ID; decreased text size from


15 to 10 characters

Column changes made to the EDM_GROUP_MEMBERS table


Redefined column GROUP_KEY to GROUP_ID; decreased text size
from 254 to 10 characters

Redefined column DBSKEY to DATA_SOURCE; decreased text size


from 12 to 5 characters

GROUP_TYPE column decreased text size from 50 to 12 characters

GROUP_NAME column decreased text size from 254 to 60 characters

Column changes made to the EDM_GROUP_MEMBERS table


DBSKEY column increased text size from 12 to 20 characters

QUAL0 column increased text size from 12 to 20 characters

QUAL1 column increased text size from 12 to 20 characters

QUAL2 column increased text size from 12 to 20 characters

QUAL3 column increased text size from 12 to 20 characters

QUAL4 column increased text size from 12 to 20 characters

R2003.14 Appendix B: ARIES Table Changes 103


Landmark

Column changes made to the RMS_BKMEMO table


RESCAT column decreased text size from 50 to 6 characters

DESCRIPTION column decreased text size from 255 to 254 characters

Column changes made to the RMS_DEFMEMO table


DESCRIPTION column decreased text size from 255 to 254 characters

Column changes made to the RMS_EIA table


STATECODE column decreased text size from 3 to 2 characters

COUNTYCODE column decreased text size from 50 to 3 characters

Column changes made to the RMS_NONBKMEMO table


DESCRIPTION column decreased text size from 255 to 254 characters

Column changes made to the RMS_RPT table


PROPNAME column increased text size from 50 to 60 characters

Column changes made to the RMS_SCENARIO table


SCENARIO column increased text size from 6 to 20 characters

ARIES Primary Key Changes43 Total

PDEN_ID replaced PROPNUM as a primary key in 25 tables plus


the following new tables
ECON_EXTENSION

ECON_EXTENSION_UEXT

AR_VIPDATA

PDEN_TYPE was added as a primary key in all of the tables mention


previously

104 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Primary Key changes made to the ARGROUPTEST table

New column CHILD_TYPE was added as a primary key

Primary Key changes made to the ARPROJECT table

DBSKEY column was removed as a primary key

Primary Key changes made to the ARSUMPROPS table

DBSKEY column was removed as a primary key

Primary Key changes made to the AR_VIPDATA table

New column QUALIFIER was added as a primary key to this new


table (non AFS)

New column PROD_DT was added as a primary key to this new table
(non AFS)

Primary Key changes made to the DW_DAILY_PROD table

New column DATA_SOURCE was added as a primary key

Primary Key changes made to the DW_MONTHLY_PROD table

New column DATA_SOURCE was added as a primary key

Primary Key changes made to the ECON_PROPERTY table

DBSKEY was not included in this table and was removed as a primary
key

Primary Key changes made to the EDM_GROUP_MEMBERS table

CHILD_ID column replaced MEMBER and was added as a primary


key

New column CHILD_TYPE was added as a primary key

PROPKEY column was removed as a primary key

Primary Key changes made to the EDM_SCENARIO table

New column SCENARIO was added as a primary key to this new table

R2003.14 Appendix B: ARIES Table Changes 105


Landmark

Primary Key changes made to the RMS_EIA table

OPCODE column was added as a primary key in Upgraded databases


using UPGRADE.exe

Primary Key changes made to the RMS_SCENARIO table

DBSKEY column was added as a primary key

SCENARIO column was added as a primary key

Database Changes from Non-ARIES database to an EDM database

Non-ARIES Tables Changes103 Total

TOW/cs tables included in the EDM database - 317 tables

No TOW/cs tables were renamed

No TOW/cs tables were added

Other AFS tables included in the EDM database

The CD_GROUP table was renamed to EDM_GROUP

The CD_GROUP_MEMBERS table was renamed to


EDM_GROUP_MEMBERS

In an AFS database, the ARIES tables GROUPS and GROUPLIST


were dropped in the EDM model. Their columns and respective data
were combined with the CD_GROUP and
CD_GROUP_MEMBERS tables to form the new EDM tables
EDM_GROUP and EDM_GROUP_MEMBERS.

New EDM tables that were added in the new EDM database (101
items)

Non-ARIES Column Changes30 Total

TOW/cs and other AFS Tables in which columns were Renamed in


EDM

Columns renamed in EDM_GROUP table (compared to


CD_GROUP table)

The column "GROUP_SID" renamed to "GROUP_ID

106 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

The column "GROUP_UID" renamed to "GROUP_NAME

The column "DATA_IND" renamed to "DYNAMIC_DATA

The column "DYNAMIC_CONFIG_IND" renamed to


"DYNAMIC_CONFIG

The column "STATUS" renamed to "CURRENT_STATUS

The column "REMARKS" renamed to "REMARK

Columns renamed in EDM_GROUP_MEMBERS table (from


CD_GROUP_MEMBERS)

The column "GROUP_SID" renamed to "GROUP_ID

The column "MEMBER_SID" renamed to "CHILD_ID

The column "MEMBER_TYPE" renamed to "CHILD_TYPE

TOW/cs and other AFS Tables in which New columns were added to
the EDM

Columns added to the EDM_GROUP table (compared to


CD_GROUP table)

BUILD_DATE

DATA_SOURCE

OWNER

TEST_ID column was added to the VC_EQUIP_TEST table

EQUIP_ID column was added to the VC_EQUIPMENT table

FIELD_ID column was added to the VC_FIELD table

STRAT_UNIT_ID column was added to the VC_FORMATION


table

SITE_ID column was added to the VC_LOCATION table

TEST_ID column was added to the VC_PROD_TEST table

RESERVOIR_ID column was added to the VC_RESERVOIR table

R2003.14 Appendix B: ARIES Table Changes 107


Landmark

Columns added to the VC_WELLCOMP table


LOCATION_ID
WELL_ID
COMPLETION_ID
ACCT_COMPLETION_ID
CREATE_DATE
CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID

TOW/cs and other AFS Tables in which columns were not included (Removed) in
EDM
SEQUENCE_NO column was removed from
EDM_GROUP_MEMBERS table

Non-ARIES Column Definition / Size Changes

Column changes made to the VC_COMPLETION_RF table


DWIGHTS_CD column increased text size from 20 to 40 characters

Column changes made to the VC_PROPERTY table


LEGAL_DS column increased text size from 10 to 50 characters

Column changes made to the VC_RPT_CONFIG table


Redefined RPT_DS column from a Memo field to VarChar 1000
format

Column changes made to the VC_SELECT_SQL table


Redefined WHERE_CLAUSE column from a Memo field to VarChar
2000 format

Column changes made to the VC_SYS_MSG table


Redefined EXT_MSG_DS column from a Memo field to VarChar

108 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

2000 format

Redefined ACTION_DS column from a Memo field to VarChar 2000


format

Column changes made to the VC_SYS_SQL table


Redefined SQL_SYNTX1 column from a Memo field to VarChar 2000
format

Column changes made to the VC_WELLCOMP table


DWIGHTS_CD column increased text size from 20 to 40 characters

R2003.14 Appendix B: ARIES Table Changes 109


Landmark

110 Appendix B: ARIES Table Changes R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Appendix C:
Manual Oracle Upgrades

Manually Running the Oracle Upgrade Utilities

Landmark recommends to our users that they should upgrade databases


automatically with the methods discussed in Chapter 2 5 of this
manual.

However, there may be instances when a DBA or System


Administrator might need the following steps to reference a manual
upgrade.

Required Tools and Installation

Database Update installs the Oracle and SQL Server upgrade


executables in the
C:\Landmark\EDT_2003.14\EDM\Updates\Oracle and
C:\Landmark\EDT_2003.14\EDM\Update\SQLServer
directories.

R2003.14 Appendix C: Manual Oracle Upgrades 111


EDM Production and Economics Database & Migration Guide Landmark

Procedure

1. Run the EDMSPC.SQL located in the <Install


folder>\EDM\Updates\Previous Upgrades folder.
The EDMSPC.SQL creates the needed tablespaces and user
permissions needed for the upgrade.

2. Run the appropriate upgrade executable from the


C:\Landmark\EDT_2003.14\EDM\Updates\Oracle
directory.

3. Select the SETUP Option.

4. Select the Run Manually option.

5. Select the directory you wish the upgrade script to be copied to and
click OK.

Scripts are copied into the selected folder.

6. Select the current version of your database from the drop down
menu and click OK.

A version to version message will be displayed.

7. Click Yes.

A script location message will be displayed.

8. Click OK.

9. Browse to the location of the copied scripts and run the


COPYFILE.exe.

The COPYFILE.exe creates a temporary folder if one does not


exist and copies a file containing the Drilling store functions.

10. Scroll to the bottom of the runscript.txt file and edit the
PK\Landmark to read PK\Landmark@instancename to correctly
create the Picklist tables.

11. Run the runscrpt.txt file against the database you want to upgrade.

You must be logged in as the Schema owner.

112 Appendix C: Manual Oracle Upgrades R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Appendix D:
Manual SQL Server Upgrades

Manually Running the SQL Server Upgrade Utilities

Landmark recommends to our users that they should upgrade databases


automatically with the methods discussed in Chapter 2 5 of this
manual.

However, there may be instances when a DBA or System


Administrator might need the following steps to reference a manual
upgrade.

Required Tools and Installation

Database Update installs the Oracle and SQL Server upgrade


executables in the
C:\Landmark\EDT_2003.14\EDM\Updates\Oracle and
C:\Landmark\EDT_2003.14\EDM\Update\SQLServer
directories.

Procedure

1. Run the appropriate upgrade executable located in the <Install


folder>\EDM\Updates\Previous Upgrades folder.
The EDMSPC.SQL creates the needed tablespaces and user
permissions needed for the upgrade.

2. Select the SETUP Option.

3. Select the Run Manually option.

4. Select the directory you wish the upgrade script to be copied to and
click OK.

R2003.14 Appendix D: Manual SQL Server Upgrades 113


EDM Production and Economics Database & Migration Guide Landmark

Scripts are copied into the selected folder.

5. Select the current version of your database from the drop down
menu and click OK.

A version to version message will be displayed.

6. Click Yes.

A script location message will be displayed.

7. Click OK.

8. Browse to the location of the copied scripts and run the


COPYFILE.exe.

The COPYFILE.exe creates a temporary folder if one does not


exist and copies a file containing the Drilling store functions.

9. Run the runscrpt.txt file against the database you want to upgrade.

You must be logged into the database as the System Administrator.

114 Appendix D: Manual SQL Server Upgrades R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Appendix E:Oracle Configuration

Oracle ODBC

Landmarks Applications use the Open Database Connectivity (ODBC)


standard as a common interface between their code and their data
stored on the EDM database. A single module interfaces to all
Relational Database Management Systems (RDBMS), with ODBC
handling the differences. EDM Engineering applications are shipped
with the Oracle JDBC drivers.

Appropriate ODBC drivers must be installed and tested on the client


workstation before installing the EDM Engineering applications.

In most cases, network ODBC drivers will require previous installation


of supporting client/server librariesthis in turn may require previous
installation of supporting network software. Corresponding
components would also be required on the server.

For example, a typical Oracle installation will require:

1. A SQL*Net listener on the server;

2. TCP/IP or other transport protocols on the server;

3. An ODBC driver on the client;

4. Oracle's SQL*Net and TCP Adapter or another transport protocol


adapter on the client;

5. TCP/IP or some other network transport software on the client.

This will require coordination of several software vendors, and often


requires expert installation.

EDM is certified against Oracle using the ODBC drivers supplied by


Oracle Corporation.

R2003.14 Appendix E:Oracle Configuration 115


EDM Production and Economics Database & Migration Guide Landmark

RDBMS Configuration

Engineers Desktop applications have been certified for Oracle 8.1.7


and Oracle 9i (including ODBC drivers). Earlier versions of Oracle
may not work for this release. There are separate procedures for
installing EDM on Oracle depending on whether Oracle 8.1.7 or Oracle
9i are used.

Oracle

Separate Tables & Indexes (Performance)


A common strategy to reduce disk contention is to put tables, indexes,
control files, system table space, and rollback segments each on
separate spindles.

Some sites use other strategies such as disk striping and disk mirroring.
Consult the Oracle documentation for more complete information on
performance strategies.

The DBA is free to manage these performance issues, as long as the


following conditions are met:

1. The Engineers Desktop applications data schema must be left as


supplied (i.e. table names, column names, column data types, and
column order cannot be changed).

2. All Engineers Desktop applications user(s) must have access to


all tables.

Rollback Segments
Size: Landmark recommends a minimum rollback segment size of 2
megabytes (each). All rollback segments on-line should be at least that
size.

Number: Use the Oracle recommendations, count one concurrent user


as one concurrent transaction. If you expect 16 users or less, use 4
rollback segments; 32 or less, 8 segments; 200 or less, users/4; over
200 users, 50 segments.

116 Appendix E:Oracle Configuration R2003.14


Landmark EDM Production and Economics Database & Migration Guide

Exception: One of EDMs features is its XML data transfer file


system. XML imports are checked and committed frequently, so they
do not require large rollback segments.

Temporary Tablespace
Landmark recommends that you maintain at least 50 megabytes free in
your temporary tablespace. If you have more than 20 concurrent users,
allow 2.5 megabytes per user.

Note:

If a database exists, there may be a shared temporary tablespace suitable for use
by the EDM user.

R2003.14 Appendix E:Oracle Configuration 117