Professional Documents
Culture Documents
EDM PE Database & Migration
EDM PE Database & Migration
EDM PE Database & Migration
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:
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.
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
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
iv Contents R2003.14
Landmark EDM Production and Economics Database & Migration Guide
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
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.
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
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.
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.
Database Creation
The EDM Database Creation Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
EDM Database Creation.
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.
4. Select Oracle
5. Click Start.
6. Click Yes.
9. Click Yes.
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.
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.
MetaDataLibrary.resources
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
SQL Server
1. Click Start > Programs > Landmark Engineers Desktop
2003.14 > Tools > EDM Database Creation to run db_create.exe.
3. Click Yes.
5. Click OK.
8. Press OK.
9. Click End.
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:
Database Update
Use the Production_to_2003.11.exe to update your 2003.4.2.0 AFS
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.
Data Migration
You will not have to migrate the data when upgrading the 2003.11 database to a
2003.14 database.
The AFS Data Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
AFS to EDM Migration.
Upgrade Procedures
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.
2. From the
c:\Landmark\EDT_2003.14\EDM\Updates\Oracle
directory, execute the Production_to_2003.11.exe self
extracting executable.
6. Click OK.
7. If prompted to save the log file, click the Yes button and select a
destination directory.
The database will begin the migration and a progress bar will be
displayed.
17. Review the log file by selecting Menu > View > Log.
SQLServer
1. From the Vol 5\Products\EDT\Previous DB
Upgrades\SQL Server directory, execute the
Production_to_2003.11.exe self extracting executable.
5. Click OK.
6. If prompted to save the log file, click the Yes button and select a
destination directory.
The database will begin the migration and a progress bar will be
displayed.
16. Review the log file by selecting Menu > View > Log.
c:\Landmark\EDT_2003.14\EDM\DATA
Migration\AFSFinalCleanup.sql
Upgrade Procedures
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.
5. Click OK.
6. If prompted to save the log file, click the Yes button and select a
destination directory.
The database will begin the migration and a progress bar will be
displayed.
16. Review the log file by selecting Menu > View > Log.
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.
6. Click OK.
7. If prompted to save the log file, click the Yes button and select a
destination directory.
The database will begin the migration and a progress bar will be
displayed.
17. Review the log file by selecting Menu > View > Log.
c:\Landmark\EDT_2003.14\EDM\DATA
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.
Database Creation
The EDM Database Creation Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
EDM Database Creation.
The ARIES to EDM Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
ARIES to EDM Migration.
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.
Once your data has been upgraded to 2003.41, you need to create an
EDM instance to which you will migrate your data.
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.
4. Select Oracle
5. Click Start.
6. Click Yes.
9. Click Yes.
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.
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.
3. Click Yes.
5. Click OK.
8. Press OK.
9. Click End.
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.
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.
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.
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.
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.
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.
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.
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.
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).
Upgrade Procedures
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.
5. Click OK.
6. If prompted to save the log file, click the Yes button and select a
destination directory.
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.
6. Click OK.
7. If prompted to save the log file, click the Yes button and select a
destination directory.
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.
Database Creation
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.
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.
Data Migration
You will not have to migrate the data when upgrading the 2003.11 database to a
2003.14 database.
The AFS Data Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.11 > Tools >
AFS to EDM Migration.
The ARIES to EDM Migration Tool can be launched from Start >
Programs > Landmark Engineers Desktop 2003.14 > Tools >
ARIES to EDM Migration.
AFS
Original
Verify Data
7th Optional step. Cleaup and/or delete ARIES Standalone database
8th Optional step. Cleanup and/or delete EDM ARIES database
Initially, this process mirrors that used to migrate data for the individual
applications.
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
7. Select File > New Project, Click Run Query icon to load all
properties in DBS.
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.
Upgrade Procedures
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.
5. Click OK.
6. If prompted to save the log file, click the Yes button and select a
destination directory.
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.
6. Click OK.
7. If prompted to save the log file, click the Yes button and select a
destination directory.
Appendix A:
Migration Tables and Column Mappings
EDM_SCENARIO_DTL
Old Table Action during migration Action during cleanup New EDM Production Table
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.
Appendix B:
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.
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
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
RMSRPTHDR RMS_RPTHDR
RMSSCENARIO RMS_SCENARIO
RMSSECURITY RMS_SECURITY
SELFILTERS ARSELFILTERS
SORTFILTERS ARSORTFILTERS
SORTTITLE ARSORTTITLE
SUMPROPS ARSUMPROPS
TBLSETS ARTBLSETS
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
PROPNUM to PDEN_ID
In the following ARIES tables, the PROPNUM was replaced by the
new PDEN_ID column.
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
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
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.
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
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
RMSBKDELTA RMS_BKDELTA
RMSBKMEMO RMS_BKMEMO
RMSBKPROD RMS_BKPROD
RMSEIAHEADER RMS_EIAHEADER
RMSNONBKMEMO RMS_NONBKMEMO
RMSREPORT RMS_REPORT
RMSRESERVES RMS_RESERVES
RMSRPT RMS_RPT
REMARK
CREATE_DATE
CREATE_USER_ID
UPDATE_DATE
UPDATE_USER_ID
CREATE_APP_ID
UPDATE_APP_ID
QUALIFIER
PROD_DT
OIL
GAS
WTR
WTRINJ
GASINJ
PRESS
PTYPE
REMARK
CREATE_DATE
CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID
REMARK
CREATE_DATE
CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID
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
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
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
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.
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
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
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
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
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.
OUTDATE END_DATE
"S370" "G_OIL_PROD
"S371" "G_GAS_PROD
"S1065" "N_TOT_OPC_ADV
"S1069" "BFIT_OP_INC
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
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.
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
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
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
G_TANG_INV G_INT_INV
G_NGL_PROD G_WAT_PROD
G_OIL_SOLD G_GAS_SOLD
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
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
C892
C1064
M17
M24
Note
the above columns plus other items can be added to EDM using the
DW_ECON_ONELINE_UEXT table if created.
PHASENAME PHASE_NAME
STARTDATE START_DATE
OWNERNAME OWNER_NAME
UNITS INTEREST_TYPE
"P_DATE" "PROD_DT
"OIL" "VO_OIL_PROD
"GAS" "VO_GAS_PROD
"WATER" "VO_WAT_PROD
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
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
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
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.
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.
Columns that were Removed and not included in the EDM data
model
DBSKEY
PI_CODE
DW_CODE
RRCD
OIL_PUR
GAS_PUR
CHILD_TYPECREATE_DATECREATE_USER_ID
CREATE_APP_IDUPDATE_DATEUPDATE_USER_ID
UPDATE_APP_ID
SCENARIO
DATA_SOURCE
REMARK
CREATE_DATE
CREATE_USER_ID
UPDATE_DATE
UPDATE_USER_ID
CREATE_APP_ID
UPDATE_APP_ID
CREATE_USER_ID
CREATE_APP_ID
UPDATE_DATE
UPDATE_USER_ID
UPDATE_APP_ID
SUBDCODE
FIELDNAME
ID
ST
SUB
FLDCD
FIELD
CO
CNTY
DISC
ECON_EXTENSION_UEXT
AR_VIPDATA
New column PROD_DT was added as a primary key to this new table
(non AFS)
DBSKEY was not included in this table and was removed as a primary
key
New column SCENARIO was added as a primary key to this new table
New EDM tables that were added in the new EDM database (101
items)
TOW/cs and other AFS Tables in which New columns were added to
the EDM
BUILD_DATE
DATA_SOURCE
OWNER
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
2000 format
Appendix C:
Manual Oracle Upgrades
Procedure
5. Select the directory you wish the upgrade script to be copied to and
click OK.
6. Select the current version of your database from the drop down
menu and click OK.
7. Click Yes.
8. Click OK.
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.
Appendix D:
Manual SQL Server Upgrades
Procedure
4. Select the directory you wish the upgrade script to be copied to and
click OK.
5. Select the current version of your database from the drop down
menu and click OK.
6. Click Yes.
7. Click OK.
9. Run the runscrpt.txt file against the database you want to upgrade.
Oracle ODBC
RDBMS Configuration
Oracle
Some sites use other strategies such as disk striping and disk mirroring.
Consult the Oracle documentation for more complete information on
performance strategies.
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.
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.