corporate data store™ - openworks® synchronization user

Corporate Data Store™ - OpenWorks® Synchronization

User Reference Guide © 2010 Halliburton

Release 5000.2.1 March 2010 .


© 2010 Halliburton 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

2107 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.Halliburton.com/Landmark

Trademark Notice

3D Drill View, 3D Drill View KM, 3DFS, 3D Surveillance, 3DView, Active Field Surveillance, Active Reservoir Surveillance, ADC, Advanced Data Transfer, ARIES, ARIES DecisionSuite, AssetConnect, Asset Decision Solutions, Asset Development Center, AssetDirector, Asset Journal,

AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, Asset Performance, AssetPlanner, AssetSolver, AssetSolver Online, AssetView, BLITZPAK, CasingLife, CasingSeat, COMPASS, Corporate Data Archiver,

Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot, Decision Management System, DecisionSpace, DecisionsSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace AssetView 2D, DecisionSpace

AssetView 3D, DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace for Production, DecisionSpace Infrastructure, DecisionSpace Nexus, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir,

DecisionSpace TracPlanner, DecisionSpace Well Seismic Fusion, DecisionSpace WellSolver, DecisionSuite, DepthTeam, Depth Team, DepthTeam Explorer, Depth Team Explorer, DepthTeam Express, Depth Team Express, DepthTeam Extreme, Depth Team Extreme, DepthTeam Interpreter, Depth Team Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery Asset, Discovery

FrameBuilder, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth Model, Drillworks, Drillworks ConnectML, DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, EDT, eLandmark, Engineer’s Data Model, Engineer's

Desktop, Engineer’s Link, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, FastTrack, FG+, FieldPlan, Field Scenario Planner, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, GeoLink, GeoProbe GF DataServer, GES, GES97,

GESXplorer, GMAplus, GMI Imager, GRIDGENR, Handheld Field Operator, HHFO, I2 Enterprise, iDIMS, IsoMap, iWellFile, i Wellfile, KnowledgeSource, Landmark, Landmark Decision Center, Landmark & Design, Landmark Logo and Design, Landscape, Lattix, LeaseMap,

LMK Resources, LogEdit, LogM, LogPrep, Make Great Decisions, MathPack, MIMIC, MIMIC+, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWorks, OpenWorks Development Kit, OpenWorks Well

File, OpenWorks Production, PAL, Parallel-VIP, PetroBank, PetroBank Explorer, PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family,

PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, Power Interpretation, PowerJournal, PowerModel, PowerView, PrecisionTarget, Presgraf, Pressworks, PRIZM, Production Asset Manager, Production, PROFILE, Project Administrator,

ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D, ProMAX 3D, ProMAX 3DPSDM, ProMAX 4D, ProMAX Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+, QUICKDIF, QuickWell, QuickWell+, QUIKRAY,

QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom, Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real Time Surveillance, Real-Time View, Reference Data Manager, Reservoir Framework Builder, RESev, ResMap, RightTime, RTOC, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks,

SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio, SimResults,

SimResults+, SimResults+3D, SIVA+, SLAM, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel, StrataSim, StrataWorks, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SynTool, SystemStart,

SystemStart for Clients, SystemStart for Servers, System Start for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, The Engineer’s Desktop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, TracPlanner Xpress, Trend

Form Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Wellbase, Wellbore Planner, Wellbore Planner Connect,

WELLCAT, Well Cost, WELLPLAN, Well Seismic Fusion, WellSolver, 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, service marks and product or service names are the trademarks or names 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.


Third Party Applications

Halliburton uses various third-party applications in the development of its software.

Halliburton acknowledges that certain third party code has been bundled with, or embedded in, its software. The licensors of this third party code, and the terms and conditions of their respective licenses, may be found at the following location:

$PE_HOME/www/cds/Third_Party.pdf

Release 5000.2.1 Corporate Data Store™ - OpenWorks® Synchronization User Reference Guide

Contents

Topics in this book.......................................................................................................................... 1

Pre-requisite skills........................................................................................................................... 2

Workflow ........................................................................................................................................ 4

Select wellbores for synchronization .............................................................................................. 4 Area of Interest ............................................................................................................................ 4

Example 1................................................................................................................................. 5 Example 2................................................................................................................................. 5 Example 3................................................................................................................................. 5

Corporate OpenWorks® Wells ................................................................................................... 6

Backup verification......................................................................................................................... 7 Backups in the Oracle database ................................................................................................... 8 Oracle project backup files .......................................................................................................... 8

Optimization and well lists ............................................................................................................. 9

Insert and updates with batch Advanced Data Transfer™ software............................................. 10 Advanced Data Transfer™ template files ................................................................................. 10

Data Selection ........................................................................................................................ 11 Target OpenWorks® project.................................................................................................. 11 Target coordinate system ....................................................................................................... 11 Selection file........................................................................................................................... 12

Cascade deletes ............................................................................................................................. 13 Deleted data items in Corporate Data Store™ database ........................................................ 14 Data deletion mechanism ....................................................................................................... 14 Deletion of wells .................................................................................................................... 14 Deletion of wellbores ............................................................................................................. 16 Deletion of positional logs ..................................................................................................... 16 Deletion of directional surveys .............................................................................................. 17 Deletion of time-depths.......................................................................................................... 17

Email notification.......................................................................................................................... 18 Email summary ...................................................................................................................... 18 Project summary..................................................................................................................... 19

Output log files ............................................................................................................................. 24

Datatype coverage......................................................................................................................... 25 Well information ....................................................................................................................... 25 Directional Survey and Postional Log....................................................................................... 26 Material Sample......................................................................................................................... 27 Stratigraphy ............................................................................................................................... 27

Contents iv


Time-Depth................................................................................................................................ 28 Well Test ................................................................................................................................... 29 Wellbore Mechanical................................................................................................................. 30 GeoMaps.................................................................................................................................... 30 Seismic 2D................................................................................................................................. 31 Seismic 3D................................................................................................................................. 31

System design ............................................................................................................................... 33

Execution sequence....................................................................................................................... 35

Pre-requisites................................................................................................................................. 36

Installation..................................................................................................................................... 37

Configuration ................................................................................................................................ 41 Edits to $PE_HOME/conf/pe_dic-server.props ..................................................................... 43

Global Configuration................................................................................................................. 43

Information checklist .................................................................................................................... 45

OpenWorks® District Configuration............................................................................................ 46 Backup Verification................................................................................................................... 47 Email Notification ..................................................................................................................... 47

Select the Datatypes to Synchronize............................................................................................. 48 Available Datatypes to Synchronize.......................................................................................... 49

Available Sync Datatype........................................................................................................ 49 Update Datatype..................................................................................................................... 49 Delete Datatype...................................................................................................................... 50 Delete Datatype Attribute ...................................................................................................... 51

Datatype Selections ................................................................................................................... 51 Selection................................................................................................................................. 51 Selection Datatype ................................................................................................................. 52 Selection Update .................................................................................................................... 53 Selection Delete ..................................................................................................................... 53

Define synchronization specification for the project .................................................................... 54 Add Project Details – “Job” ...................................................................................................... 54

Verify OpenWorks® Project Database Information.............................................................. 54 Determine Last Successful Update for the Project ................................................................ 55 Synchronization Job ............................................................................................................... 56

Add Area of Interest – “Manage AOI”...................................................................................... 57 AOI Extent Display................................................................................................................ 61

Pick Interpreter Filter ................................................................................................................ 61 ADT File Override .................................................................................................................... 62

Testing the Configuration ............................................................................................................. 62 Testing the Job Specification..................................................................................................... 63 Backup Verification................................................................................................................... 64 Check Connections .................................................................................................................... 65 Check optimization results ........................................................................................................ 67

Contents v


Contents vi

Check data selection results....................................................................................................... 69

Run from command line ............................................................................................................... 72 Running the synchronization process ........................................................................................ 72 Checking the status of the synchronization process .................................................................. 73

Console log file ...................................................................................................................... 73 Advanced Data Transfer™ transfer log file ........................................................................... 74

Aborting the synchronization process ....................................................................................... 75 Running synchronization processes in parallel ......................................................................... 76 Results in OpenWorks® Projects .............................................................................................. 77

Run as a scheduled cron job.......................................................................................................... 77

Troubleshooting ............................................................................................................................ 78 Error status in email................................................................................................................... 78 PowerHub unavailability ........................................................................................................... 79 Advanced Data Transfer™ transfer errors ................................................................................ 83 Well Note Pad............................................................................................................................ 84 OpenWorks® project is down ................................................................................................... 84 No email notification................................................................................................................. 84 Advanced Data Transfer™ hangs.............................................................................................. 85 Network configuration issues .................................................................................................... 86

Swapping wellbore alias names in Corporate Data Store™ database .......................................... 88 Step 1. Initial state .................................................................................................................... 89 Step 2. Edit aliases in Corporate Data Store™ database.......................................................... 89 Step 3. Save changes and run synchronization......................................................................... 89 Step 4. Update wellbore alias in Corporate Data Store™ database ......................................... 90 Step 5. Save changes to Corporate Data Store™ database and run synchronization............... 90

Troubleshooting Advanced Data Transfer™ transfers ................................................................. 91 Step 1. Batch Advanced Data Transfer™ transfer gives error in email ................................... 91 Step 2. Check Advanced Data Transfer™ log file ................................................................... 91 Step 3. Find batch Advanced Data Transfer™ session file ...................................................... 94 Step 4. Launch Advanced Data Transfer™ software with session file .................................... 95 Step 5. Check output for errors................................................................................................. 95 Step 6. Resolve errors............................................................................................................... 95

Time-zone differences .................................................................................................................. 96

Example Area of Interests............................................................................................................. 97 Multiple geographic extents and attribute where clause ........................................................... 97 Text where clause only .............................................................................................................. 98

Migrate Corporate Data Store™- OpenWorks® Synchronization R5000 to 5000.2.1 ............... 98


Introduction

Corporate Data Store™ – OpenWorks® Synchronization is a tool for automated synchronization of Corporate Data Store™ well data to OpenWorks projects. It uses the Advanced Data Transfer™ application in batch mode for insert and updates to OpenWorks®

projects and the PowerHub™ API for cascading data deletion in Corporate Data Store™ database down to OpenWorks® projects.

Topics in this book

Target Audience on page 2

Functional Overview on page 3

Technical Overview on page 26

Installation and Configuration on page 29

Adding a New Project on page 42

Running the Synchronization Process on page 49

Special Workflows in page 65

Introduction 1


Target Audience

The intended audience of this book includes:

Data managers for OpenWorks® projects and Corporate Data Store™ databases.

System administrators for the software applications PowerExplorer®, PowerHub™ and Advanced Data Transfer™.

Much of the terminology and concepts used in the book assume basic knowledge and familiarity with the Landmark corporate data management technology suite as well as horizontal technologies such as XML and UNIX scripts. A list of pre-requisite skills needed for using this book effectively is given below:

Pre-requisite skills

Good working knowledge of PowerExplorer® software and Advanced Data Transfer™ software.

Ability to use PowerExplorer® TaskBuilder.

Knowledge of data quality control using PowerExplorer® client application projects (drilldown and merge results).

Ability to navigate and examine OpenWorks® projects and Corporate Data Store™ database data within PowerExplorer® software.

Knowledge of data models for both OpenWorks® projects and Corporate Data Store™ software, specifically datatypes/attributes included in Corporate Data Store™ - OpenWorks® transfer.

Knowledge of rules (mandatory attributes, integrity constraints) for Corporate Data Store™ attributes included in Corporate Data Store™ - OpenWorks® Synchronization.

Familiarity with Advanced Data Transfer™ log messaging - what common error / warning messages occur when loading data into OpenWorks® projects from Corporate Data Store™ databases and how to resolve.

Target Audience 2


Ability to perform manual transfer from Corporate Data Store™ database to OpenWorks® projects using Advanced Data Transfer™ application.

Basic UNIX scripting and crontab editing.

Basic XML editing.

Target Audience 3


Functional overview

Workflow

The Corporate Data Store™ - OpenWorks® Synchronization process follows a sequence of steps:

1. Select wellbores for synchronization. 2. Verify project backup. 3. Optimize using wellbore lists. 4. Insert and update to OpenWorks® projects using batch Advanced Data Transfer™

application. 5. Delete from OpenWorks® projects. 6. Complete temporary Advanced Data Transfer™ workarounds. 7. Receive email notification. 8. Review output log file.

These steps are described in detail below.

Select wellbores for synchronization

The list of database wellbores for synchronization comes from both Corporate Data Store™ and OpenWorks® projects. An Area of Interest (AOI) is used to define which Corporate Data Store™ wellbores should be included for synchronization. For OpenWorks® projects, an SQL where clause is used to define corporate wells which should be synchronized from Corporate Data Store™ software.

An optional “Global Area of Interest” can also be applied to all Area of Interests.

Area of Interest

The Area of Interest (AOI) defines which data should be synchronized from Corporate Data Store™ database to OpenWorks® projects. This definition can take the form of one or many geographical extents, combined with one or more attribute SQL where clauses. Examples of AOIs are:

Functional overview 4


Example 1 (51deg 20' 0''N to 61deg 40' 0''N

18deg 0' 0''W to 4deg 40' 0''W

and onshore_offshore = OFF)

or wellname = 'Well-1'

Example 2 (((71deg 50' 0''N to 61deg 10' 0''N

1deg 24' 0''E to 2deg 0' 0''E

or

71deg 20' 0''N to 61deg 20' 0''N

1deg 36' 0''E to 2deg 0' 0''E)

and country = UK)

union

(70deg 15' 00''N to 71deg 15' 00''N

1deg 40' 0'E to 2deg 20' 0''E

and country = Norway))

Example 3 All wellbores where country in (UK, France, Faroes)

The AOI definitions above are converted into an SQL where clause which runs against the Corporate Data Store™ well and wellbore tables, for example:

((well.preferred_latitude between 55.5 and 58 and well.preferred_longitude between 1.8 and 3.5 and wellbore.country_name='UNITED KINGDOM' and wellbore.kind='HYDROCARBON WELL' and (wellbore.initial_purpose IN ('EXPLORATION','APPRAISAL') or wellbore.current_purpose IN ('EXPLORATION','APPRAISAL'))) or (well.preferred_latitude between 55.5 and 58 and well.preferred_longitude between 1.8 and 15 and wellbore.country_name IN ('NORWAY','DENMARK') and (wellbore.initial_purpose IN ('EXPLORATION','APPRAISAL') or wellbore.current_purpose IN ('EXPLORATION','APPRAISAL'))))

If any new wellbores are added to Corporate Data Store™ databases and fall within the AOI they will be transferred to OpenWorks® projects. Any updates to wellbores within the AOI will be carried through to OpenWorks® projects.

Note: Coordinate system transformation is not performed on the values specified in the AOI. If two wellbores with the same preferred_latitude and preferred_longitude coordinates, but different geographic coordinate systems are present in Corporate Data Store™



databases, e.g. “55.3, 3.5” (WGS84) and “55.3, 3.5” (ED50), then both would be included if the AOI was set to “55.1, 2.0 to 60.0, 4.0”.

It is also possible to specify an optional “global AOI” which is automatically added to all project AOIs. For example,

Global AOI = “well.preferred_latitude IS NOT NULL and well.preferred_longitude IS NOT NULL”

Is added to the regular AOI to give:

((well.preferred_latitude between 55.5 and 58 and well.preferred_longitude between 1.8 and 3.5 and wellbore.country_name='UNITED KINGDOM' and wellbore.kind='HYDROCARBON WELL' and (wellbore.initial_purpose IN ('EXPLORATION','APPRAISAL') or wellbore.current_purpose IN ('EXPLORATION','APPRAISAL'))) or (well.preferred_latitude between 55.5 and 58 and well.preferred_longitude between 1.8 and 15 and wellbore.country_name IN ('NORWAY','DENMARK') and (wellbore.initial_purpose IN ('EXPLORATION','APPRAISAL') or wellbore.current_purpose IN ('EXPLORATION','APPRAISAL')))) and (well.preferred_latitude IS NOT NULL and well.preferred_longitude IS NOT NULL)

The global AOI is specified in the “cdssync.aoi.global” parameter in the PowerExplorer® “Global Configuration” task.

Corporate OpenWorks® Wells

The synchronization process will query the target OpenWorks® project for “corporate” wells and add those to the list of wellbores to be synchronized from the Corporate Data Store™ database. This step is necessary to ensure that wellbores added manually to the OpenWorks® project from the Corporate Data Store™ database which are outside the AOI are also included in the sychronization process. The OpenWorks® wells are defined as “corporate” by an SQL where clause, for example:

select * from well_master where well_uwi_type=’XXX’

It is also possible to constrain on a well list, for example:

select * from well_master, well_list where well_list_name=‘CORP_WELLS’

In practice, it is the PowerHub “OW Connect” metadata topic “ow$WellEntireList” which is used for this query, so any attribute present in this topic, including “Well List Name”, can be used in the constraint.

In summary, the list of wellbores to be synchronized from Corporate Data Store™ database to OpenWorks® project is the result of two SQL queries, one against Corporate Data Store™ database with an AOI, the other against OpenWorks® project for corporate wells. The figure below illustrates this selection:



Backup verification

Backup verification is an optional step in the Corporate Data Store™ - OpenWorks® Synchronization process. If backup verification is activated the synchronization process will check for the existence of a valid OpenWorks® project backup before continuing. If the backup either does not exist or is too old, then the synchronization process will stop for that project and notify the user by email.

Backup verification is performed by looking at the Oracle database and for an Oracle backup file on disk.

A configuration parameter “days old” is used to specify how recent a backup must be for Corporate Data Store™ - OpenWorks® Synchronization to continue. The default setting is 3 days old, but this can also be set for all projects within an OWDISTRICT level or for an individual project within an OWDISTRICT.



Backup verification is enabled by setting the “cdssync.verify.backup” parameter in the PowerExplorer® “Global Configuration” task to TRUE. Backup verification settings can be modified via the “Backup Verification” task in PowerExplorer®.

Backups in the Oracle database

When an OpenWorks® project is backed up an entry is made in the OE_PROJECT_HISTORY table as operation type “BACKUP”. The Corporate Data Store™ - OpenWorks® Synchronization will query for the latest entry in this table under “BACKUP” and will stop the synchronization process if the backup is too old.

SQL> select max(h.operation_date) from OWSYS.OE_PROJECT_HISTORY h, OWSYS.OE_PROJECT_DETAIL d where h.project_id=d.project_id and d.project_name='CDS_V180_TO_OW_UTM31' and h.operation='BACKUP';

MAX(H.OPE

---------

03-MAY-06

SQL>

Oracle project backup files

The Corporate Data Store™ - OpenWorks® Synchronization process will use FTP to search for the existence of an oracle project backup file. The FTP command will change to the directory containing the backup files and perform a file listing. The listing will be examined for the presence of a backup file and if the file does not exist, or is too small (<1 MB) or too old, the Corporate Data Store™ - OpenWorks® Synchronization process will stop. An example file listing is shown below:

bash-2.05b$ cat OWPROD.CDS_V180_TO_OW_UTM31.backup.txt

-rwxr-xr-x 1 oracle dba 4775225 Apr 30 20:17 OWPROD.cds_v180_to_ow_utm31.dmp.20060430.Z

-rwxr-xr-x 1 oracle dba 4766161 May 1 20:17 OWPROD.cds_v180_to_ow_utm31.dmp.20060501.Z

The syntax of the FTP operation which produces this listing is shown below:



server=$1

user=$2

pass=$3

dir=$4

sid=$5

project=$6

files=*$sid*$project*Z

ftp -n << EOF

open $server

user $user $pass

cd $dir

ls $files

quit

EOF

The backup files are assumed to have been named using the “<OWDISTRICT>.<project>.dmp.<YYYYMMDD>.Z” syntax, where <project> is the OpenWorks project, in lower case, and <YYYYMMDD> is the date of the backup in year, month, day format (e.g. 20100330).

Optimization and well lists

The Corporate Data Store™ - OpenWorks® Synchronization process uses an optimization technique based on Corporate Data Store™ lists and OpenWorks® lists, as well as SQL queries. There are two optimization goals. First, avoid calling Advanced Data Transfer™ unless wellbores within the AOI have changed.

Second, only pass to Advanced Data Transfer™ wellbores which have changed (inserted or updated). The optimization is peformed on a per datatype basis, so that Advanced Data Transfer™ software will only be called to transfer a datatype if changes have been made to that



datatype. The result is that if picks are the only datatype to have changed for wellbores within the AOI, then Advanced Data Transfer™ software will only be asked to transfer the pick datatype, and not well header, time-depth or directional surveys.

The optimization technique will maintain an active Corporate Data Store™ list of wellbores to be synchronized.

The list is refreshed with every synchronization run, with wellbores being added/removed as necessary.

For audit purposes a separate well list is also maintained in OpenWorks® project. The OpenWorks® project list is called “CDS_SYNC_WELLS” and is owned by the “LGC” interpreter. It can be used to highlight the wells in OpenWorks® project which are being synchronized with Corporate Data Store® database.

Insert and updates with batch Advanced Data Transfer™ software

The Advanced Data Transfer™ program is used in batch mode to perform the actual transfer of well data from Corporate Data Store™ databases to OpenWorks® projects. Advanced Data Transfer™ software will do insert and update of data, but not deletes, which are handled separately.

The Corporate Data Store™ - OpenWorks® Synchronization process simply creates Advanced Data Transfer™ selection and session files, which are then passed into the batch Advanced Data Transfer™ software program. The same selection and session files can also be read into regular Advanced Data Transfer™ software for troubleshooting purposes.

For a more detailed explanation of how Advanced Data Transfer™ transfers data from Corporate Data Store™ databases to OpenWorks® projects, please see the Advanced Data Transfer™ Reference Manual.

Advanced Data Transfer™ template files

There are two template files, a session file (.job.xml) and selection file (.sel.xml), for each of the supported datatypes. The session file contains three tags which are replaced by real values by the Corporate Data Store™ - OpenWorks® Synchronization process. The selection file is populated with the wellbores to be transferred from Corporate Data Store™ databases to OpenWorks® projects.


Data Selection The “*** DATA SELECTION ***” text is replaced by the name of a dynamically-generated selection file containing the wellbores to be synchronized from Corporate Data Store™ databases to OpenWorks® projects. For example:

<Option>

<Name>DataSelection</Name>

*** DATA SELECTION FILE ***



</Option>

Gets converted to:

<Option>

<Name>DataSelection</Name>

<Value>/glb/home/usjea0/dev/sync/adt_files/OWPROD.CDS_V180_TO_OW_UTM31.20060428_2342.well_header_selection.xml</Value>



</Option>

Target OpenWorks® project The “*** TARGET OPENWORKS ***” text is replaced by the name of target OpenWorks® project. For example:

<Option>

<Name>Moniker</Name>

*** TARGET OPENWORKS ***

</Option>

Gets converted to:

<Option>

<Name>Moniker</Name>

<Value>OpenWorks/OWPROD.CDS_V180_TO_OW_UTM31.OpenWorksData</Value>

</Option>

Target coordinate system The “*** COORDINATE_SYSTEM ***” text is replaced by the coordinate system of target OpenWorks® project. For example:


<Option>

<Name>Target Carto System</Name>

<Type>com.lgc.ow.ca.CaSys</Type>

<Value>OpenWorks/NAME.CoordinateSys.*** COORDINATE_SYSTEM ***</Value>

</Option>

Gets converted to:

<Option>

<Name>Target Carto System</Name>

<Type>com.lgc.ow.ca.CaSys</Type>

<Value>OpenWorks/NAME.CoordinateSys..ED50 / UTM Zone 31N</Value>

</Option>

Note: In Advanced Data Transfer™ software, the target coordinate system is looked up by the batch Advanced Data Transfer™ program and can be removed from the Corporate Data Store™ - OpenWorks® session template file.

Selection file The Advanced Data Transfer™ software selection files for well header, time-depth and directional survey contain a list of the UWIs for synchronization. The selection file for stratigraphy (picks) contains a listing of each pick to be transferred.

The “*** INSERT INSTANCES HERE ***” text is replaced by the UWI (or unique_wellbore_identifier) of the wellbore to be transferred to OpenWorks® projects by Advanced Data Transfer™ software. For example:

<DataSelection>

<TopLevelSelection name="Wellbore">

*** INSERT INSTANCES HERE ***

<Selection name="Wellbore_alias">

Gets converted to:

<DataSelection>




<Instance>

<Key name="unique_wellbore_identifier" value="19000099997001"/>

</Instance>

<Selection name="Wellbore_alias">

For picks, the selection file contains an entry for both the UWI and the individual picks to be transferred:

<DataSelection>


<Instance>

<Key name="unique_wellbore_identifier" value="19000099997801"/>

<ChildSelection name="Pick">

<Instance>

<Key name="pick_obs_no" value="1"/>

<Key name="pick_name" value="NAME"/>

<Key name="pick_interpreter" value="INTERP"/>

</Instance>

Note: Advanced Data Transfer™ software will fail to replace any OpenWorks® data with NULL values. So if updates are made to Corporate Data Store™ databases and data set to NULL, these changes will not occur in OpenWorks® projects. It is hoped that this is resolved in future Advanced Data Transfer™ software versions.

Cascade deletes

The Corporate Data Store™ - OpenWorks® synchronization will search for any deleted data in the Corporate Data Store™ database belonging to the wellbores within the AOI. If it finds deleted data, it will perform a deletion from the OpenWorks® project. Not all datatypes are currently supported, see the “Datatype coverage” section below for more details.



The cascade delete is an option which can be enabled or disabled on a per-project basis. The default setting is for cascade delete to be enabled.

Deleted data items in Corporate Data Store™ database There is an option in Corporate Data Store™ software for tracking “deleted data items”. The Corporate Data Store™ - OpenWorks® Synchronization relies on this option being activated in the Corporate Data Store™ software installation. Once activated, the “Deleted Data Instances” task in PowerExplorer® software can be used to query the Corporate Data Store™ database for deleted items for a particular datatype.

Data deletion mechanism The Corporate Data Store™ - OpenWorks® Synchronization uses the PowerHub™ API to first query for deleted data records and second, to delete the data from OpenWorks® project.

Deletion of wells The deletion of a well from Corporate Data Store™ databases will automatically delete its associated wellbores. In this case the only information recorded in Corporate Data Store™ databases is the delete of the well, not the wellbores for example:

instance_natural_key external_object_type_name data_source delete_date delete_user_id

{unique_well_identifier=190000999972} Well ITED 2006-05-03 23:07:27 USER

{unique_well_identifier=190000999905} well 2006-05-03 23:08:17 USER



The sync process will delete those wells in OpenWorks® projects which are associated to the deleted Corporate Data Store™ wells.

If OpenWorks® wells have sidetrack parents, then the synchronization will first set the parent_wellpath_uwi/id and well_location_uwi/id to NULL before deleting from OpenWorks® project. Therefore, both sidetracks and sidetrack parents will be deleted from OpenWorks® projects when the well is deleted from Corporate Data Store™ database, for example:

Uwi Well Name Well Location Uwi Parent Wellpath Uwi

19000099990501 Well1

19000099990502 Well2 19000099990501 19000099990501

If synchronization selects the wells “19000099990501” and “19000099990502” for deletion from OpenWorks® project, the following actions take place.

1. Set well_location_uwi to NULL and parent_wellpath_uwi to NULL.

2. Delete well from OpenWorks® project.



Deletion of wellbores Generally the cascade deletion of Corporate Data Store™ database wellbores down to OpenWorks® project wells is straightforward due to the direct mapping between Corporate Data Store™ unique_wellbore_identifier and OpenWorks® project well_uwi. For example:

instance_natural_key external_object_name data_source delete_date delete_user_id

{unique_wellbore_identifier=19000099996402} Wellbore SOURCEA 5/10/2006 1:42:14 PM NAME

{unique_wellbore_identifier=19000099990003} Wellbore SOURCEB 5/11/2006 3:35:50 PM NAME

This maps easily to OpenWorks® projects:

CDS deleted well

unique_well_identifier

OpenWorks well

well_uwi

19000099996402 19000099996402

1900009999003 19000099990003

In this case the OpenWorks® wells can be deleted with no problem by Corporate Data Store™ - OpenWorks® Synchronization.

Deletion of positional logs Since there is no direct one-to-one mapping between Corporate Data Store™ wellbore paths and OpenWorks® position logs, some special business logic is used when handling Corporate Data Store™ database deleted wellbore paths. The following table shows the rules for cascade delete of OpenWorks® position logs:

Case Deleted Corporate Data Store™ wellbore path has

directional survey?

Directional survey has other path as preferred?

*Delete position log from OpenWorks®

position logs?

1 NO - NO

2 YES YES NO

3 YES NO YES*

* If the OpenWorks® position log belongs to the same directional survey.



For case 1, the lack of a directional survey means that there is no way to tell whether the deleted Corporate Data Store™ wellbore path is the same as the OpenWorks® position log. Therefore, no attempt is made to deleted from the OpenWorks® project.

For case 2, the deleted Corporate Data Store™ wellbore path does have a directional survey, but the survey has another path set as “preferred”. Since the OpenWorks® positional log should have been sourced from the undeleted Corporate Data Store™ preferred path, then no attempt is made to delete from OpenWorks® project.

For case 3, the deleted Corporate Data Store™ wellbore path does have a directional survey, but that survey has no other preferred wellbore paths. In this case the decision is made that since the Corporate Data Store™ database contains no preferred path for that directional survey and a path has been deleted from Corporate Data Store™ database, then the position log should be deleted from the OpenWorks® projects.

Deletion of directional surveys When a directional survey is deleted from OpenWorks® projects, the Corporate Data Store - OpenWorks® Synchronization will also delete the postional log (if any) which belonged to that directional survey. The regular OpenWorks® dev kit does not perform this function (position log must be deleted separately), but it is included in Corporate Data Store™ - OpenWorks® Synchronization. So any directional survey deleted from Corporate Data Store™ software, will delete both directional survey and position log from OpenWorks® projects.

Deletion of time-depths The OpenWorks® dev kit will not automatically delete any records in child tables to TIME_DEPTH_CURVE, for example PREFERRED_TD_CURVE. When Corporate Data Store™ - OpenWorks® Synchronization attempts to delete time-depth from OpenWorks® projects it may have an “error”. In this case the reason is likely to be that the OpenWorks® time-depth record has associated data whose foreign key constraints prevent it from being deleted. The solution is to manually remove the child records from OpenWorks® projects before re-running the Corporate Data Store™ - OpenWorks® Synchronization process.



Email notification

The Corporate Data Store™ - OpenWorks® Synchronization will send out an email summarizing the results of the synchronization process. The email is sent on a per-OWDISTRICT or per-OWPROJECT basis, so the results of synchronization for each or all projects with a given OWDISTRICT can be sent to a different list of email addresses. The subject line in the email will be “Corporate Data Store™ Synchronization Summary Report” and the from address will depend on the value specified in the PowerExplorer® “Email” task.

If the email does not arrive when expected, then something has gone seriously wrong with the Corporate Data Store™ - OpenWorks® Synchronization process and the procedure in “Troubleshooting” should be followed to see what has happened.

Email summary The email will contain a short summary which lists the status of each project which was synchronized for that OWDISTRICT, together with some timing information, for example:

CDS-OW synchronization run for 14 projects. Took 15.6 minutes. Overall time was 20.82 minutes unchanged OWPROD.CDS_SYNC_PROJECTA unchanged OWPROD.CDS_SYNC_USWEST changed OWPROD.CDS_SYNC_NORWAY unchanged OWPROD.CDS_SYNC_ENGLAND unchanged OWPROD.CDS_SYNC_GULFOFMEXICO changed OWPROD.CDS_SYNC_PAKISTAN changed OWPROD.CDS_SYNC_INDONESIA unchanged OWPROD.CDS_SYNC_AUSTRALIA unchanged OWPROD.CDS_SYNC_FRANCE changed OWPROD.CDS_SYNC_INDIA unchanged OWPROD.CDS_NAME unchanged OWPROD.CDS_SYNC_RUSSIA changed OWPROD.CDS_SYNC_USEAST unchanged OWPROD.CDS_SYNC_USSOUTH

The summary shows that synchronization was run for 14 projects in the OWDISTRICT and that it took 15.6 minutes to complete. The “Overall time was 20.82 minutes” is for the entire synchronization process, which includes synchronization to other OWDISTRICTs.

The “unchanged” status indicates that no changes were made to the project, implying that none of the datatypes for the wellbores within the AOI for that project had changed in the Corporate Data Store™ database. If the synchronization performs a delete or invokes an Advanced Data Transfer™ transfer against that project, then the status



will show “changed”. Additional statuses are ‘skipped”, “error” and “no backup”, see table below for more details:

Status Description

unchanged No changes were made to the project

changed Changes were made to the project, either delete, insert or update

error An error occurred during the synchronization process to that project

skipped Another synchronization process was working on that project, so it was skipped

no backup The project did not have a suitable backup, in which case no changes are made on the project

Project summary The main body of the email includes a detailed summary of the synchronization process for each individual OpenWorks® project. For example:

---------------------------------------------------------------- Summary for OWPROD.CDS_SYNC_ENGLAND Coordinate system=ED50 / TM 0 N CDS Where clause=((well.preferred_latitude between 59 and 60 and well.preferred_longitude between 1 and 2.33333333 and wellbore.country_name='UNITED KINGDOM') or (well.preferred_latitude between 60 and 61 and well.preferred_longitude between -1 and 2.33333333 and wellbore.country_name='UNITED KINGDOM') or (well.preferred_latitude between 61 and 62 and well.preferred_longitude between 0 and 2 and wellbore.country_name='UNITED KINGDOM') or (well.preferred_latitude between 59 and 59.25 and well.preferred_longitude between 1.58333333 and 2 and wellbore.country_name='NORWAY') or (well.preferred_latitude between 59.25 and 61.5 and well.preferred_longitude between 1.58333333 and 2.33333333 and wellbore.country_name='NORWAY') or (well.preferred_latitude between 61.5 and 62 and well.preferred_longitude between 1.33333333 and 2 and wellbore.country_name='NORWAY')) Data types: Picks=yes Dir survey=yes Time depth=yes Verified database backup for OWPROD.CDS_SYNC_ENGLAND Verified file backup for OWPROD.CDS_SYNC_ ENGLAND Backup verification took 0.8 seconds Found 3491 wellbores for synchronization. Found 0 wellbores missing from OpenWorks. Finding CDS selection from AOI took 11.18 seconds Deleted 0 time-depths Deleted 0 picks



Cannot delete from OW: Dir survey (19000000000801 : UNKNOWN) has a preferred wellbore path. Deleted 1 pos logs 19000099991301 : PENG E01 : UNITED KINGDOM : UNKNOWN : UNKNOWN_minCurvature Deleted 1 dir surveys Pos-log deleted: 19000099991101 : PENG D01 : UNITED KINGDOM : UNKNOWN Dir-survey deleted: 19000099991101 : PENG D01 : UNITED KINGDOM : UNKNOWN Deleted 0 well status history records Deleted 0 well alias records Deleted 0 wellbores Cascade delete from CDS to OW took 11.65 seconds Last run date was:Tue May 02 00:09:00 CEST 2006 Starting batch ADT at Wed May 03 00:09:20 CEST 2006 Found 1 update to cds_well Optimize: Found 1 updated wellbores for well header. Took 6.91 seconds ADT wellbore header transfer took 1.11 minutes. WARNING: Job Summary: 1 ElevInfo rows skipped due to matching data 4 WellStatusHistory rows skipped due to matching data 1 RDataAcqType rows skipped due to matching data 1 WellEntire rows successfully updated 3 WellUwi rows skipped due to matching data Found 1 update to cds_wellbore_dir_survey Optimize: Found 1 updated wellbores for dir-survey. Took 0.69 seconds Found 1 update to cds_wellbore Optimize: Found 1 updated wellbores for pos-logs. Took 0.14 seconds ADT dir survey/pos-log transfer took 1.11 minutes. WARNING: Job Summary: 1 PosLog rows successfully updated 1 DirSurvey rows successfully updated 1 WellEntire rows skipped due to matching data Optimize: Found 0 updated wellbores for stratigraphy. Took 0.24 seconds Batch ADT: no updated wellbores for stratigraphy Optimize: Found 0 updated wellbores for time-depth. Took 0.24 seconds Batch ADT: no updated wellbores for time-depths Completed batch ADT at Wed May 03 00:11:39 CEST 2006 No updates to elev infos found for CDS_SYNC_ENGLAND wellbores. Performed 1 updates to OW WELL_MASTER.platform_slot_no Platform workaround took 0.12 seconds Update of OW list for 3491 wellbores took 6.52 seconds Sync took 2.94 minutes



----------------------------------------------------------------

An explanation of each part of the project summary is given below.

Header information

This section shows the target coordinate system for the project and the AOI expressed as an SQL where clause against Corporate Data Store® well and wellbore:

Coordinate system=ED50 / TM 0 N CDS Where clause=((well.preferred_latitude between 59 and 60 and well.preferred_longitude between 1 and 2.33333333 and wellbore.country_name='UNITED KINGDOM') or (well.preferred_latitude between 60 and 61 and well.preferred_longitude between -1 and 2.33333333 and wellbore.country_name='UNITED KINGDOM') or (well.preferred_latitude between 61 and 62 and well.preferred_longitude between 0 and 2 and wellbore.country_name='UNITED KINGDOM') or (well.preferred_latitude between 59 and 59.25 and well.preferred_longitude between 1.58333333 and 2 and wellbore.country_name='NORWAY') or (well.preferred_latitude between 59.25 and 61.5 and well.preferred_longitude between 1.58333333 and 2.33333333 and wellbore.country_name='NORWAY') or (well.preferred_latitude between 61.5 and 62 and well.preferred_longitude between 1.33333333 and 2 and wellbore.country_name='NORWAY'))

Datatype coverage

The types of data to be synchronized are shown, with a “yes” if they are to synchronized with OpenWorks® projects or “no” if they are to be ignored.

Data types: Picks=yes Dir survey=yes Time depth=yes

Backup verification

Confirmation of both valid file and database backups for the project is given:

Verified database backup for OWPROD.CDS_SYNC_PAKISTAN Verified file backup for OWPROD.CDS_SYNC_ENGLAND Backup verification took 0.8 seconds



Wellbores selected for synchronization

The number of wellbores which are found within the AOI is displayed along with how many of those wellbores do not currently exist in OpenWorks® projects.

Found 3491 wellbores for synchronization. Found 0 wellbores missing from OpenWorks. Finding CDS selection from AOI took 11.18 seconds

Deleted data items

A count of any deleted data is given for each datatype, along with a listing of the database natural keys to show exactly which data were deleted.

Deleted 0 time-depths Deleted 0 picks Cannot delete from OW: Dir survey (11000090010801 : UNKNOWN) has a preferred wellbore path. Deleted 1 pos logs 11000090011301 : PENG E01 : UNITED KINGDOM : UNKNOWN : UNKNOWN_minCurvature Deleted 1 dir surveys Pos-log deleted: 11000090011101 : PENG D01 : UNITED KINGDOM : UNKNOWN Dir-survey deleted: 11000090011101 : PENG D01 : UNITED KINGDOM : UNKNOWN Deleted 0 well status history records Deleted 0 well alias records Deleted 0 wellbores Cascade delete from CDS to OW took 11.65 seconds

The “Cannot delete from OW : Dir survey….” message informs that a path for wellbore 11000090010801 was deleted from Corporate Data Store™ database, but since the Corporate Data Store™ directional had another path set as preferred it would not delete anything from OpenWorks® projects. For more detail see the “Cascade deletes” section above.



Starting batch Advanced Data Transfer™ software

The last time synchronization was run against the project is displayed along with the current time it starts the batch Advanced Data Transfer™ software process.

Last run date was:Tue May 02 00:09:00 CEST 2006 Starting batch ADT at Wed May 03 00:09:20 CEST 2006

Optimization

A message will be displayed showing the results of the optimization process which lists how many data items have changed for the selected wellbores.

Found 1 update to cds_well Optimize: Found 1 updated wellbores for well header. Took 6.91 seconds

The text above shows that a single update was found to the “cds_well” Corporate Data table for the selected wellbores.

Optimize: Found 0 updated wellbores for stratigraphy. Took 0.24 seconds Batch ADT: no updated wellbores for stratigraphy Optimize: Found 0 updated wellbores for time-depth. Took 0.24 seconds Batch ADT: no updated wellbores for time-depths

The text above shows that no updates were found for stratigraphy or time-depths for the selected wellbores.

Batch Advanced Data Transfer™ Software

If any updates are found to the selected wellbores for a given datatype, then batch Advanced Data Transfer™ software is called and the transfer results displayed.

ADT dir survey/pos-log transfer took 1.11 minutes. WARNING: Job Summary: 1 PosLog rows successfully updated 1 DirSurvey rows successfully updated 1 WellEntire rows skipped due to matching data

This shows that one positional log and one directional survey were updated in OpenWorks® projects by Advanced Data Transfer™ software.



Closing remarks

The end of the project summary informs that the OpenWorks® well list was updated and notes the time taken for the synchronization process to complete for that project.

Update of OW list for 3491 wellbores took 6.52 seconds Sync took 2.94 minutes

Output log files

The Corporate Data Store™ - OpenWorks® Synchronization process produces two log files in the $SYNC_HOME/logs directory, an ASCII version of the email summary and a capture of the UNIX console output. For example:

rumba.lgc.com{jeremy}% pwd

/export/home/jeremy/dev/sync/logs

rumba.lgc.com{jeremy}%

rumba.lgc.com{jeremy}% ls -altr

total 624

drwxr-xr-x 12 jeremy wheel 4096 Mar 17 15:08 ../

-rw-rw-rw- 1 jeremy wheel 38264 May 1 00:12 sync_20060501_00_12_37.log

-rw-rw-rw- 1 jeremy wheel 262999 May 1 00:12 2006-05-01_00:05_sync_console.out

-rw-rw-rw- 1 jeremy wheel 38268 May 2 00:12 sync_20060502_00_12_40.log

-rw-rw-rw- 1 jeremy wheel 263001 May 2 00:12 2006-05-02_00:05_sync_console.out

drwxrwxr-x 2 jeremy wheel 12288 May 4 15:02 ./

rumba.lgc.com{jeremy}%

The “sync_2006xxxx.log” file contains an ASCII version of the emailed summary. The “2006-xx-xx-xx_sync_console.out” file is the UNIX console output from the Corporate Data Store™ - OpenWorks® Synchronization process.

The console output file contains detailed information about the Corporate Data Store™ - OpenWorks® Synchronization process and is useful for troubleshooting.



Datatype coverage

The list of datatypes supported by Corporate Data Store™ - OpenWorks® Synchronization is shown below.

Well information

Included in batch Advanced Data Transfer™ software



*Cascade delete from OpenWorks®

* OpenWorks® dev kit will also delete from any associated or child tables, apart from situations where the well to-be-deleted is the parent of other OpenWorks® wells, via the WELL_LOCATION_ID/UWI or PARENT_WELLPATH_ID/UWI attributes. In this case, the Corporate Data Store™ - OpenWorks® Synchronization will throw an “error” for that well and the solution is to manually correct the situation in OpenWorks® projects before re-running Corporate Data Store™ - OpenWorks® Synchronization.

** Deleted instances of wellbore_class.class_kind=’data acqusition type’ will result in OpenWorks® project well_master.data_acquisition_type being set to “UNKNOWN”

Directional Survey and Postional Log





* OpenWorks® dev kit will also delete from any associated or child tables

Note: Only wellbore paths in Corporate Data Store™ database with “preferred_flag=’TRUE’” are transferred by Advanced Data Transfer™ software to OpenWorks® projects.

Material Sample



Stratigraphy





* OpenWorks® dev kit will also delete from any associated or child tables

Time-Depth





*The OpenWorks® dev kit does not automatically delete child tables associated to TIME_DEPTH_CURVE, for example “PREFERRED_TD_CURVE” records are not deleted. In this case Corporate Data Store™ - OpenWorks® Synchronization will throw an “error” and the records from the associated child tables will need to be deleted manually.

Well Test





Wellbore Mechanical



GeoMaps





Seismic 2D



Seismic 3D





Currently not supported.



Technical overview

System design

The Corporate Data Store™ - OpenWorks® Synchronization design adopts a Service Oriented Architecture (SOA), where a loosely coupled collection of independent Service implementations cooperate to deliver the full Corporate Data Store™ - OpenWorks® Synchronization workflow. The Services are written in Java and typically wrap an out-of-box technology, such as Advanced Data Transfer™, PowerHub™ API, JDBC, XML parsing and JDBC. The figure below shows the SOA design for Corporate Data Store™ - OpenWorks® Synchronization:

Technical overview 33


OpenWorks CDS

ADT

PowerHub API

JDBC

XML parser

Javax mail

Application / Data Tier PowerHub

UNIX cron launch Manual launch

Synchronize

Process Tier

Service Tier

Email notification

Batch ADT wrapper

Temporary workarounds

Cascade deletion

Optimizer: find updates

Maintain well lists

Backup verification

Select wells in AOI

FTP




Execution sequence

The following diagram shows the execution sequence for the Corporate Data Store™ - OpenWorks® Synchronization process:

The synchronization process will loop over a list of target OpenWorks® project and process each project separately. If any errors occur during the processing of an OpenWorks® project, the sync process will flag that project with an “error” but still continue to work on that project and the others in the list.

Temporary workarounds

Maintain well lists

Cascade deletion

Select wells in AOI

Batch ADT wrapper

Optimizer: find updates

Backup verification

Email notification

Find sync jobs

Repeat for each OpenWorks project…


Installation and configuration

Pre-requisites

The Corporate Data Store™ - OpenWorks® Synchronization installation needs to be able to access a PowerExplorer® installation and a Advanced Data Transfer™ installation.

Requirement Reason

Access to PowerExplorer® installation ($PE_HOME) Java-run time

PowerHub API jar

Oracle JDBC jar

XML parser

JAVAX mail

Access to Advanced Data Transfer™ installation ($ADT_HOME)

Run Advanced Data Transfer™ software in batch mode.

Access to OpenWorks® run-time ($OWHOME) Run Advanced Data Transfer™ software in batch mode (required).

Access to Oracle database server running OpenWorks® projects

Network connectivity to the Oracle database server is required for Advanced Data Transfer™ software.

Access to PowerHub™ server Network access is required for both CDS-OW synchronization and batch Advanced Data Transfer™ software to the PowerHub™ server.

Generic LINUX/UNIX account This is optional, but a recommended practice to use a generic account for “automated” synchronization, for example “s_cdsync”.

Manage credentials for Corporate Data Store™ software and OpenWorks® projects

The synchronization process will create Corporate Data Store™ software lists which requires “cds_full_access” access, as well as MANAGE access for each target OpenWorks® project.

Access to the “CDS to OpenWorks” Synchronization tasks in PowerExplorer® and the CDS2OW PowerHub™ dictionary

The CDS-OW synchronization configuration is stored in the CDS2OW PowerHub™ dictionary. Access to this configuration requires the PowerHub™ dictionary database account. Access to the “CDS to OpenWorks” Synchronization tasks in PowerExplorer

Installation and configuration 36


requires “cds_admins” access.

Note: The Advanced Data Transfer™ installation should be configured to run in “standalone” mode.

The synchronization process can be run from a separate machine than the PowerHub™ server, provided it can see the $PE_HOME installation.

A good rule of thumb is that Advanced Data Transfer™ software needs to be launched and used to transfer data from Corporate Data Store™ database to OpenWorks® projects from the same machine and with the same LINUX/UNIX user as used for Corporate Data Store™-OpenWorks® Synchronization.

Installation

New Installation

The Corporate Data Store™-OpenWorks® Synchronization files are installed by the Corporate Data Store™ installer under the $PE_HOME/sync directory. As part of the installation, sample data is imported into the CDS2OW PowerHub™ dictionary tables as references. By default these sample jobs are set to TRUE for synchronization. To prevent these sample jobs from synchronizing, either modify them to meet your needs or set them to FALSE in the PowerExplorer® “Synchronization -> CDS to OpenWorks -> Manage Job -> Job” task.

Upgraded Installation

The Corporate Data Store™-OpenWorks® Synchronization upgrade assumes that the R5000 synchronization files are located under the existing $PE_HOME/sync directory. The files from the previous release must exist under the $PE_HOME/sync directory prior to running the Corporate Data Store™ upgrader because the upgrader will upgrade the existing $PE_HOME in place. The Corporate Data Store™ upgrader creates a backup of the previous $PE_HOME/sync directory as $PE_HOME/sync_DD-MM-YY_hh_mm. It then installs the new $PE_HOME/sync files for the release and copies the following files from the previous $PE_HOME/sync_DD-MM-YY_hh_mm directory into the new $PE_HOME/sync directory:

- adt_files / ADTUser.properties



- conf / email.xml

- conf / local.props

- jobs / rundate.xml

- jobs / syncjobs.xml

The existing sync jobs and configuration in these files are then imported into the CDS2OW PowerHub™ dictionary. After the content of these files are imported into the CDS2OW PowerHub™ dictionary, all configuration for the Corporate Data Store™-OpenWorks® Synchronization are done via PowerExplorer®.

NOTE: If you do not see the content of these files in PowerExplorer® after the installation/upgrade, you can use the $PE_HOME/sync/bin/runImportSyncJobs script to re-try the import.

A description of the Corporate Data Store™-OpenWorks® Synchronization folders and their contents is given below:

Folder Reason Comment

sync/adt_files Contains Advanced Data Transfer™ session and selection files created dynamically by Corporate Data Store™-OpenWorks® Synchronization, as well as the log files from the batch Advanced Data Transfer™ software run.

Also contains ADTUser.properties file which defines the PowerHub™ server, default OpenWorks® project and default measurement system.

The Advanced Data Transfer™ session, selection and log files should be deleted on a regular basis.

The Advanced Data Transfer™ log file can be used (tail –f) to check the status of the batch Advanced Data Transfer™ process.

sync/adt_templates Contains templates for Advanced Data Transfer™ session and selection files for each datatype.

These files are shipped with the Corporate Data Store™-OpenWorks® Synchronization installation. As part of the installation/upgrade, the session files are automatically edited with the PowerHub™ server and ADT_HOME values entered during the installer/upgrader.

If need be, review and edit these files to meet your needs. These files do not need to be edited on a regular basis.

sync/bin Contains the scripts used to call Corporate Data Store™-OpenWorks® Synchronization.

The relevant variables in these scripts are automatically edited during installation/upgrade.



The “runSync” script is used to launch the synchronization process.

The “runImportSyncJobs” script is used to import the content of the synchronization xml files into the CDS2OW PowerHub™ dictionary. This script is automatically invoked during the installation/upgrade process to populate the dictionary with this initial configuration. NOTE: When executed from the Unix prompt, this script will delete the existing configuration in the CDS2OW PowerHub™ dictionary and reimport the content in the xml files. As such, use this script only when there is a need to completely refresh the synchronization configuration in the CDS2OW PowerHub™ dictionary.

sync/conf Contains parameter files. The *_env parameter files are automatically edited with the values entered during the Corporate Data Store™-OpenWorks® Synchronization installation/upgrade.

Review and edit these files as needed. Normally, these files do not need to be edited after the Corporate Data Store™-OpenWorks® Synchronization installation/upgrade.

The content of the email.xml and local.props file are imported into the CDS2OW PowerHub™ dictionary during the installation/upgrade process. Edits to these configuration, such as when new projects are added, can then be made using PowerExplorer®.

sync/jars Contains Java executable for Corporate Data Store™-OpenWorks® Synchronization.

No edits required.

sync/jobs Contains description of each synchronization “Job” – the AOI and datatypes for each project.

Also contains the “rundate.xml” file which stores the date the of the last successful synchronization process on a per-project basis.

The content of these xml files (available datatypes to sync, jobs, aoi, rundate, etc.) are imported into the CDS2OW PowerHub™ dictionary during the installation/upgrade process. Edits to the jobs configuration, such as when new projects are added, can then be made



using PowerExplorer®.

sync/logs Contains the results of the Corporate Data Store™-OpenWorks® Synchronization process.

Use “ls –altr” to find the latest console output file, and then “tail –f” to monitor progress.

The log and console files should be deleted on a regular basis.

sync/test Contains several scripts useful for testing certain components of the Corporate Data Store™-OpenWorks® Synchronization process, but without starting the whole process.

sync/tmp Used to store temporary files generated by the Corporate Data Store™-OpenWorks® Synchronization process.

If the Corporate Data Store™-OpenWorks® Synchronization is manually aborted (e.g. CTRL-C), be sure to delete any “.lck” files present in this directory before running the next synchronization process. Otherwise the next synchronization job will skip the project.

In this release, configuration of the Corporate Data Store™-OpenWorks® Synchronization is done via PowerExplorer®. The Corporate Data Store™-OpenWorks® Synchronization tasks are located under the “Synchronization -> CDS to OpenWorks” folder in PowerExplorer®. Access to these tasks requires a PowerExplorer® account with “cds_admins” access and the PowerHub™ dictionary account. A description of the files/xml-based configuration and the corresponding PowerExplorer® task it is mapped to is provided below:

File PowerExplorer® Task Comment

conf / local.props Global Configuration All of the cds.* and cdssync.* parameters in the local.props file are stored in the Global Configuration task.

conf / local.props Backup Verification The backup and ftp parameters in the local.props file are stored in the Backup Verfication task.

conf / local.props Job The OWDISTRICT.OWPROJECT database and PowerHub parameters in the local.props file are stored in the Job task.

conf / email.xml Email



jobs / syncjobs.xml Tasks under the “Manage Job” and “Manage Selection” folders.

Each OWDISTRICT.OWPROJECT job to sync is stored in the main Job task, with the AOI, AOI Extent, Pick Interpreter Filter, and ADT File Override tasks storing other relevant information for the OWDISTRICT.OWPROJECT job.

The partitions and data types to sync for each OWDISTRICT.OWPROJECT job is configured and managed via the tasks under the “Manage Selection” folder.

jobs / rundate.xml Job

Last Successful Update

The last successful run date is stored in the Job task. The Last Successful Update task is provided as a convenience to view the last successful run of all jobs.

jobs / sync_datatypes.xml Available Sync Datatype

Update Datatype

Delete Datatype

All supported partitions and data types available to sync are stored in these three tasks.

jobs / delete_datatypes.xml Delete Datatype

Delete Datatype Attribute

Information on the data types available for sync deletion is stored in these 2 tasks.

Configuration

The following information should be gathered / verified before proceeding with the configuration:

Parameter Value Description Parameter file / PowerExplorer® Task

ADT_HOME Prepopulated by the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Location of Advanced Data Transfer™ installation

conf/adt_env

ORACLE_HOME Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Needed for Advanced Data Transfer™ software

conf/adt_env

ORACLE_SID Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Needed for Advanced Data Transfer™ software (defaulted to Corporate Data Store™ database)

conf/adt_env



TWO_TASK Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Needed for Advanced Data Transfer™ software

conf/adt_env

PE_HOME Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Location of PowerExplorer® installation

conf/sync_env

SYNC_HOME Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Must be $PE_HOME/sync

Location of Corporate Data Store™ - OpenWorks® Synchronization installation

conf/sync_env

cdssync.home Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Must be $PE_HOME/sync

Location of Corporate Data Store™ - OpenWorks® Synchronization installation

PE Task: Global Configuration

cdssync.ow.schema Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Name of the OpenWorks® schema of Corporate Data Store™ database


cdssync.ow.selection.where Where clause to define “corporate” wells in OpenWorks® projects using PowerExplorer® “Well Header” task.

NOTE: This is only relevant for Wells-based synchronization (Sync_type of “Wells”).


cdssync.aoi.global Optional global AOI to be added to all project AOIs for Well-based data types.

NOTE: This is only relevant for Wells-based synchronization (Sync_type of “Wells”).


cdssync.email.from From address to use in email notification


cdssync.email.server SMPT server from which to send email notification


cdssync.batch.script runBatchADT Name of batch Advanced Data Transfer™ script.

Should not be changed!


cdssync.adtlog.url Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

URL to Advanced Data Transfer™ log files


cdssync.verify.backup TRUE or FALSE Whether or not to perform backup verification of the projects.


cdssync.ftp.script <SYNC_HOME>/bin/runFTP_wrap Fully qualified name of the FTP PE Task: Global



script for backup verification.

Should not be changed!

Configuration

cds.dbuser Name of Corporate Data Store™ database user.


cds.dbpasswd Password for Corporate Data Store™ database user.


cds.dbdriver oracle.jdbc.driver.OracleDriver Should not be changed! PE Task: Global Configuration

cds.dburl jdbc:oracle:thin:@<machine>:<port>:<database>

URL to Corporate Data Store™ database.


cds.dbname Prepopulated by the the Corporate Data Store™-OpenWorks® Synchronization installer/upgrader.

Name of the Corporate Data Store™ schema.


cds.phurl jdbc:scwapi://machine_name/ph_server_name;YOUR_PE_USER;YOUR_PE_PASSWORD;CDS5000;cds_dev;YOUR_CDSDB_USER;YOUR_CDSDB_PASSWORD

URL to access Corporate Data Store™ database via PowerHub™ server.


cds.phdriver com.lgc.dam.phs.client.jdbc.PhsJDBCDriver

Should not be changed! PE Task: Global Configuration

Edits to $PE_HOME/conf/pe_dic-server.props The “delete data instances” tracking needs to be activated in the PowerHub™ dictionary. Edit the PowerHub™ dictionary properties file (e.g. pe_dic.props) found in $PE_HOME/conf and add these two lines:

# Record delete data instances

RECORD_DATA_DELETES=TRUE

RECORD_REF_DATA_DELETES=TRUE

Save and restart the PowerHub™ server for the changes to take effect. When data are deleted from the Corporate Data Store™ database, a record will be added to the “Deleted data items” table.

Global Configuration

Once gathered, log in to PowerExplorer® as a user with “cds_admins” access. Navigate to the “Synchronization -> CDS to OpenWorks” folder. To access any of the tasks under this folder, you will need to have access to the CDS2OW PowerHub™ dictionary (PowerHub™ dictionary database account).



The “Global Configuration” task contains the cdssync.* and cds.* parameters mentioned in the Configuration table above. Most of these parameters are automatically populated / updated by the Corporate Data Store™-OpenWorks® Synchronization installation / upgrade. Review and edit these parameters accordingly. An example is provided below:



Adding a new project

Adding a new project to the Corporate Data Store™-OpenWorks® Synchronization process requires the following steps:

1. Add the OWDISTRICT and OWPROJECT to the backup verification and email notification (if not done previously).

2. Select the “Sync_type” to synchronize: Wells or the new Interpretation Data (GeoMaps, Seismic 2D and Seismic 3D).

3. Define synchronization specification for the project, including user credentials.

4. Set the last run date for the project.

Information checklist

The following information should be gathered before adding a new project to Corporate Data Store™-OpenWorks® Synchronization:

Requirement Value Description

Project OWDISTRICT The OpenWorks® DISTRICT in which the project exists.

Project Name The name of the project.

Database URL URL to the OpenWorks® project, includes database server name, port and database name.

External OpenWorks® user

e.g. “s_cdsync” Used by Advanced Data Transfer™ software. MANAGE role is required.

Internal OpenWorks® user and password

e.g. “s_cdsync_i” Used by cascade delete and workarounds. MANAGE role is required.

Project is accessible through PowerExplorer® software

N/A You can display well data from the project in PowerExplorer® software.

PowerExplorer® user and password

A PowerExplorer® user and password is needed to connect to via PowerHub™ to Corporate Data Store™ software and OpenWorks® projects.

Define Area of Interest Define which Corporate Data Store™ wellbores you want to synchronize with

Adding a new project 45


OpenWorks® by geographical extent(s) and/or attribute where clause (e.g. country_name).

For the Interpretation Data Sync_type (GeoMaps, Seismic 2D and Seismic 3D), define what you want to synchronize with OpenWorks® by geographical extent(s). Specifying the Coordinate System is required as part of the Area of Interest definition. In this release, the attribute where clause is not supported for these Interpretation Data Sync_type.

Select datatypes Choose whether to synchronize “Wells” or “Interpretation Data”.

For the “Wells” Sync_type, choose whether or not to synchronize Well Information, Well Test, Wellbore Mechanical, Material Sample, Stratigraphy (picks), Directional Surveys and Time-Depths.

For the “Interpretation Data” Sync_type, choose whether or not to synchronize GeoMaps, Seismic 2D, and Seismic 3D.

Choose pick interpreters Optional: choose which interpreters to use when transferring picks from Corporate Data Store™ database to OpenWorks® projects. If left blank, all picks for selected wellbores will be transferred from Corporate Data Store™ database to OpenWorks® projects.

OpenWorks® District Configuration

If a Corporate Data Store™ – OpenWorks® Synchronization has not been previously configured to run against a project in the OpenWorks® District, then the following steps are required. If Corporate Data Store™ – OpenWorks® Synchronization already runs against projects in the OpenWorks® District, then no further configuration is necessary at the OpenWorks® District level and the following steps can be skipped.



Backup Verification

This section can be skipped if you are not using backup verification.

For backup verification by FTP, the following information is required:

Parameter Value Description

ftp directory Directory containing the backup files.

ftp machine Machine which contains the oracle backup files for the OpenWorks® project.

ftp user User with read access to the backup files.

ftp passwd Password for the ftp user.

days old Age of the backup – to determine if the synchronization process should continue. Currently, this value can not be greater than 24 days old.

Navigate to the “Synchronization -> CDS to OpenWorks -> Backup Verification” task in PowerExplorer®. Backup verification can be configured per OpenWorks® District or per OpenWorks® project. An example is provided below:

NOTE: The backup files are assumed to have been named using the “<OWDISTRICT>.<project>.dmp.<YYYYMMDD>.Z” syntax, where <project> is the OpenWorks project, in lower case, and <YYYYMMDD> is the date of the backup in year, month, day format (e.g. 20100330).

Email Notification

Add a list of email addresses for people who are interested in Corporate Data Store™ – OpenWorks® Synchronization summary for any projects in the OpenWorks® District.

For email notifications, the following information is required:




Job_Name <ALL> or specific job The default value is <ALL>. The synchronization process will send one email for all jobs for the OpenWorks® district / project. It is best to keep this value as <ALL>.

District_Name Name of the OpenWorks® District to send email notification for. Used in conjunction with the “Project_Name” value to determine if an email should be sent per district or per project.

Project_Name <ALL> or specific project The default value is <ALL>.

If <ALL> is specified, the synchronization process will send one email for all OpenWorks® projects in the “District_Name” value.

If a specific project is specified, the synchronization process will send an email for the specified OpenWorks® project.

Email Email address of the person receiving the synchronization notification.

Navigate to the “Synchronization -> CDS to OpenWorks -> Email” task in PowerExplorer®. Email notifications can be configured per OpenWorks® District or per OpenWorks® project. An example is provided below:

Select the Datatypes to Synchronize

The Corporate Data Store™ - OpenWorks® Synchronization process supports synchronizing “Wells” and “Interpretation Data”.



Available Datatypes to Synchronize

The supported list of datatypes available for synchronization is provided under the PowerExplorer® “Synchronization -> CDS to OpenWorks -> Manage Datatype” folder tasks. These tasks list the supported datatypes Corporate Data Store™ administrators can use to build the datatype selection to synchronize for the project. These tasks should not need to be modified.

Available Sync Datatype Navigate to the “Available Sync Datatype” task to view the list of datatype partitions available to be selected for synchronization:

For the “Wells”-based Sync_type, the datatype partitions supported are: dir_survey, material_sample, picks, stratigraphy_without_picks, time_depth, well_header, well_test, and wellbore_mechanical.

For the “Interpretation Data”-based Sync_type, the datatype partitions supported are: 2dseismic, 3dseismic, and geomaps.

The “Processor_Name” attribute in the “Available Sync Datatype” task is used for special code that creates the .sel.xml and .job.xml for a specific partition. In the example above, the “picks” partition contains a special processor.

Update Datatype Navigate to the “Update Datatype” task to view the list of datatypes available to be selected for synchronization via the Advanced Data Transfer™ software:



Delete Datatype Navigate to the “Delete Datatype” task to view the list of datatypes available to be selected for the synchronization process to delete from the OpenWorks® project:



The “Processor_Name” attribute in the “Delete Datatype” task is used to call special code to do the delete on the OpenWorks® side for a specific datatype (e.g. wellbore_comment, well_alias, etc.).

Delete Datatype Attribute Navigate to the “Delete Datatype Attribute” task to view the attribute details of the datatypes listed in the “Delete Datatype” task:

Datatype Selections

Specify the datatypes to include in the synchronization jobs by modifying the PowerExplorer® tasks under the “Synchronization -> CDS to OpenWorks -> Manage Selection” folder. These tasks reference the available datatypes listed in the tasks under the “Manage Datatype” folder.

Selection Navigate to the “Selection” task to create a selection container for the datatypes to be included in the synchronization process. Determine whether the selection container will include “Wells” or “Interpretation Data” datatypes. A selection can be used by multiple synchronization jobs. An example of different selections is provided below:



Selection Datatype Once a selection is created, navigate to the “Selection Datatype” task to choose the datatype partitions to be included in the selection. By default, all the datatype partitions for the specified Sync_type are set to TRUE for synchronization. The “Selection Datatype” task generates its list of datatype partitions by querying the “Available Sync Datatype” topic.

So for a selection of Sync_type “Wells”, the following datatype partitions are automatically selected to be synchronized: dir_survey, material_sample, picks, stratigraphy_without_picks, time_depth, well_header, wellbore_mechanical, and well_test.

For a selection of Sync_type “Interpretation Data”, the following datatype partitions are automatically selected to be synchronized: 2dseismic, 3dseismic, and geomaps.

Set the “Use” attribute to “TRUE” or “FALSE” to specify whether or not the datatype partition should be included in the synchronization process. An example is provided below:



Selection Update After using the “Selection Datatype” task to choose the datatype partitions to be included in the selection, navigate to the “Selection Update” task to further filter the specific datatypes to be synchronized via the batch Advanced Data Transfer™ software. By default, all the datatypes in the partition are set to TRUE for synchronization. The “Selection Update” task generates its list of datatypes by querying the “Update Datatype” topic.

Set the “Use” attribute to “TRUE” or “FALSE” to specify whether or not the datatype should be checked for update to synchronize. An example is provided below:

Selection Delete Navigate to the “Selection Delete” task to further filter the specific datatypes to be synchronized for delete from the OpenWorks® project. By default, all the datatypes in the partition are set to TRUE for the synchronization process to check for Cascade Delete. The “Selection Delete” task generates its list of datatypes by querying the “Delete Datatype” topic.

Set the “Use” attribute to “TRUE” or “FALSE” to specify whether or not the datatype should be checked for delete to synchronize. An example is provided below:



Define synchronization specification for the project

Configuration for synchronizing the OpenWorks® project is provided under the PowerExplorer® “Synchronization -> CDS to OpenWorks -> Manage Job” folder tasks. The specification for the OpenWorks® project synchronization job requires the following information:

- Project Details – “Job”

o OpenWorks® Project Database Information

o Determine Last Successful Run Date

o Selection of datatypes to be synchronized

o User credentials for the OpenWorks® Project

- Area of Interest / where clause

- Pick Interpreter Filter (optional)

- ADT File Override (optional)

Add Project Details – “Job”

Verify OpenWorks® Project Database Information Entries for the OpenWorks® District and Project must exist in the PowerHub™ dictionary.

Navigate to the “System Administration -> Dictionary -> Topics -> Districts” task to add an entry for the OpenWorks® District. An example is provided below:



Navigate to the “System Administration -> Dictionary -> Topics -> Databases” task to add a database entry for the OpenWorks® Project.

To modify these tasks, log in with the PowerHub™ dictionary database account.

Determine Last Successful Update for the Project The entire Corporate Data Store™ – OpenWorks® Synchronization process is driven by a “last successful run” date. This date represents the last time a successful (i.e. no errors) synchronization (delete, insert and update) took place from the Corporate Data Store™ database to the OpenWorks® project. When synchronizing a project with Corporate Data Store™ database for the first time, a decision needs to be made as to which date to use as the “last successful run” date.

If the project has been manually updated from Corporate Data Store™ database using Advanced Data Transfer™ software, the “last successful run” date could be set to the date of the last manual update.

If the project has never received any data from Corporate Data Store™ database, the “last successful run” date could be set to a fictious (very early) date such as “1800-01-01”. This would ensure the project is “wholly up-to-date” with the latest corporate data.

Note: When using a fictious update date the Corporate Data Store™ – OpenWorks® Synchronization could take a long time – depending on the volume of data present in the Area of Interest. For example, with an update date of “1800-01-01” it took 21 hours to run Corporate Data Store™ – OpenWorks® Synchronization for 11,000 wellbores, 5,000 dir surveys and position logs, 4,000 time-depths and 150,000 picks.

The last successful runs for the synchronization process can be displayed by navigating to the PowerExplorer® “Synchronization -> CDS to OpenWorks -> Last Successful Update” task:



Setting the “last successful run” date for the project is done via the “Jobs” task.

Synchronization Job Navigate to the PowerExplorer® “Synchronization -> CDS to OpenWorks -> Manage Job -> Job” task to add an entry for the OpenWorks® project.

The following project job details are required:


Job_Name 20-character name to describe the Job. This name is used as part of the naming of the CDS select lists used for managing the synchronization process.

District Name of the OpenWorks® District to synchronize. This must be a valid OpenWorks® District entry in the PowerHub™ dictionary “Districts” and “Databases” topic.

Project_Name Name of the OpenWorks® projects in the District to synchronize. Used in conjuction with the “District” value, this must be a valid OpenWorks® district/project database entry in the PowerHub™ dictionary “Databases” topic.

Synchronize TRUE / FALSE Flag to determine whether or not the district/project job should be synchronized.

Last_Successful_Run Date of the last successful synchronization of the project.

Selection_Name Name of the “Selection” that specifies the datatypes chosen to be included in the synchronization process.

The datatypes selected to be synchronized are chosen via the tasks under the “Synchronization -> CDS to OpenWorks -> Manage Selection” folder.

The “Selection_Name” value must be a valid entry



in the “Synchronization -> CDS to OpenWorks -> Manage Selection -> Selection” task.

Sync_Type “Wells” or “Interpretation Data”

Derived from the “Selection_Name” value, as specified in the “Synchronization -> CDS to OpenWorks -> Manage Selection -> Selection” task.

A single synchronization job for the project can only synchronize either Wells-based datatypes or Interpretation-based (GeoMaps, Seismic 2D and 3D) datatypes, not both.

PH_Server URL of the PowerHub™ Server that accesses the OpenWorks® project.

Syntax: jdbc:scwapi://<machine name>/<powerhub server name>

PH_Userid PowerHub™ user account for the PowerHub™ Server that accesses the OpenWorks® project.

PH_Password Password for the PowerHub™ user account.

DB_Userid Database (SQL) user account for the OpenWorks® project.

DB_Password Password for the database (SQL) user account for the OpenWorks® project.

OW_Role MANAGE Default – always MANAGE role.

Cascade_Delete TRUE / FALSE Enable or disable cascade delete for the project. The default is set to TRUE, for cascade delete to be enabled for the project.

An example of project synchronization jobs is provided below:

Add Area of Interest – “Manage AOI”

Specifying the area of interest to synchronize for the project are done via the PowerExplorer® tasks under the “Synchronization -> CDS to OpenWorks -> Manage Job -> Manage AOI” folder.

Job AOI



Navigate to the PowerExplorer® “Job AOI” task to constrain the OpenWorks® project by an area of interest.

For a synchronization job of Sync_Type “Wells”, a global AOI query, if specified in the “Global Configuration”.“cdssync.aoi.global” parameter, is applied to all OpenWorks® projects Area of Interests. For a specific project, an additional where clause can be used to further filter the AOI query.

The syntax of the Job AOI where clause must be a valid SQL clause. If the Job AOI will contain any AOI Extent entry, include the “and” or “or” keyword at the beginning of the “Where_Clause” attribute.

For a synchronization job of Sync_Type “Interpretation Data”, the “Global Configuration”.“cdssync.aoi.global” query is not applicable. Neither is the “Where_Clause” attribute in the “Job AOI” task. To filter an “Interpretation Data” synchronization job by AOI, select a valid Coordinate System. This will synchronize all “Interpretation Data” records that match the specified Coordinate System.


Job_Name Name of the job to synchronize.

District_Name Name of the OpenWorks® District to synchronize.

Project_Name Name of the OpenWorks® projects in the District to synchronize

AOI_Name Name of the AOI entry.


Derived from the Job “Selection_Name” value.

Signify whether the AOI is for Wells-based datatypes or Interpretation-based (GeoMaps, Seismic 2D and 3D) datatypes.

Coordinate_System Valid only if the Sync_Type is “Interpretation Data”.

Where_Clause Valid only if the Sync_Type is “Wells”.

An example of different Job AOIs is provided below:



AOI Extent

Navigate to the PowerExplorer® “AOI Extent” task to further constrain the OpenWorks® project area of interest with specific extents.

For a synchronization job of Sync_Type “Wells”, the Job AOI can be further filtered by one or many geographical extents, combined with one or more attribute SQL where clause.

The syntax of the AOI Extent “Attribute_Where” clause must be a valid SQL clause, with the “and” or “or” keyword included at the beginning of the clause.

The syntax of the “Min_Lat”, “Min_Long”, “Max_Lat”, “Max_Long” attributes must include the correct degrees, minutes, seconds separators. Values must be entered exactly as follows:

1) Type the number of degrees.

2) Type the word deg.

3) Type a space.

4) Type the number of minutes.

5) Type a single quote: ' .

6) Type a space.

7) Type the number of seconds.

8) Type a single quote ('') twice. Note: Typing a double quote will fail.

9) Type the direction (E,W,N,S).

For a synchronization job of Sync_Type “Interpretation Data”, the AOI Extent “Attribute Where” clause is not applicable. To filter an “Interpretation Data” synchronization job with an AOI Extent, enter a numeric value in the minimum/maximum X/Y values in the “Min_Lat”, “Min_Long”, “Max_Lat”, “Max_Long” attributes. This will synchronize all “Interpretation Data” records whose rectangular spatial outline falls within the specified AOI rectangle for the Coordinate System specified in the “Job AOI”. Any record for the project that satisfies the following criteria will be synchronized:

If Min_X >= AOI_Min_Lat AND Max_X <= AOI_Max_Lat



AND Max_Y >= AOI_Min_Long AND Max_Y <= AOI_Max_Long

Note: Coordinate system transformation is not performed on the values specified in the AOI.


Job_Name Name of the job to synchronize.

District_Name Name of the OpenWorks® District to synchronize.

Project_Name Name of the OpenWorks® projects in the District to synchronize

AOI_Name Name of the Job AOI entry the extents are to be associated with.


Derived from the Job “Selection_Name” value.

Signify whether the AOI is for Wells-based datatypes or Interpretation-based (GeoMaps, Seismic 2D and 3D) datatypes.

Min_Lat If the Sync_Type is “Wells”, the correct DMS separators must be present for the minimum latitude value:

- “deg” for degrees

- “'” for minutes

- “''” for seconds

If the Sync_Type is “Interpretation Data”, enter a numeric value to denote the minimum X value of the AOI rectangle.

Min_Long If the Sync_Type is “Wells”, the correct DMS separators must be present, as specified above, for the minimum longitude value.

If the Sync_Type is “Interpretation Data”, enter a numeric value to denote the minimum Y value of the AOI rectangle.

Max_Lat If the Sync_Type is “Wells”, the correct DMS separators must be present, as specified above, for the maximum latitude value.

If the Sync_Type is “Interpretation Data”, enter a numeric value to denote the maximum X value of the AOI rectangle.

Max_Long If the Sync_Type is “Wells”, the correct DMS separators must be present, as specified above, for



the maximum longitude value.

If the Sync_Type is “Interpretation Data”, enter a numeric value to denote the maximum Y value of the AOI rectangle.

Attribute_Where Valid only if the Sync_Type is “Wells”.

An example of different AOI Extents is provided below:

More examples of Area of Interests with multiple extents and where clauses are given in the Appendix.

AOI Extent Display Navigate to the “AOI Extent Display” task or drilldown to it from the “AOI Extent” task to display the geographical extents for the synchronization jobs in the PowerExplorer® GisView.

Note: Synchronization jobs without geographical AOI extents will not be displayed in the GisView. There is no CRS conversion performed on the coordinates either. They will be treated in the GisView as “WGS84”.

Pick Interpreter Filter

This is an optional step to constrain by interpreter the picks which are transferred from Corporate Data Store™ database to OpenWorks® projects. To add a filter on pick interpreter, navigate to the PowerExplorer® “Pick Interpreter Filter” task:



In the example above, for the “STUDY_NORTH” project, only picks for the following interpreters will be transferred from Corporate Data Store™ database to OpenWorks® projects: “ANOTH”, “LGC”, and “CORP”.

If a pick interpreter filter is not specified, then all picks for the wellbore are transferred from Corporate Data Store™ database to OpenWorks® projects.

ADT File Override

This is an optional step to use a custom ADT session and selection file. To override the default templates shipped with Corporate Data Store™ - OpenWorks® Synchronization, navigate to the PowerExplorer® “ADT File Override” task to add an entry for the job:

In the example above, only the ADT session file (“mywellheader.job.xml”) is being overridden. The ADT selection file for the job remains the default (“well_header.sel.xml”). These are the name of the files located under the $PE_HOME/sync/adt_templates directory.

Testing the Configuration

The synchronization job configuration settings can be validated by running standalone test scripts which do not invoke the whole Corporate Data Store™ – OpenWorks® Synchronization process, but test one component in isolation:

Script What is tested

runJobBuilder Verifies the jobs configured for synchronization. Queries the PowerExplorer® tasks under the “Manage Job” folder. Only those jobs with the “Synchronize” parameter set to “TRUE” are verified.

runCheckBackups Checks whether or not suitable backups exist for projects. Queries the PowerExplorer® “Backup Verification” task.



runCheckConnections Confirms that database and PowerHub credentials entered in the PowerExplorer® “Global Configuration” and “Job” tasks.are valid.

runDataTypes Prints out the datatypes selected for synchronization. Queries the PowerExplorer® tasks under the “Manage Selection” folder.

runDataSelection Performs a selection of wellbores or top-level interpretation data types (geomaps, seismic 2D and 3D) within the AOI and writes a file.

runOptimize Performs the optimization part of Corporate Data Store™ – OpenWorks® Synchronization, writing the results to a file.

Note: None of these scripts will cause any actual data to be transferred from Corporate Data Store™ – OpenWorks®.

The scripts are located in the “sync/test” directory.

Testing the Job Specification

The project job specification configured for synchronization can be verified using the “runJobBuilder” script, for example:

{cdssync}% pwd

/d01/cds/pehome/sync/test

{cdssync}% ./runJobBuilder

Mar 23, 2010 10:31:41 PM com.lgc.dam.cds.owsync.verify.DoBuildSyncJobs loadProperties

…

Found 3 sync jobs.

Checking SyncJob: *** cds_sync_sample.STUDY_NORTH ***

Do cascade delete=true

CDS AOI=((((well.preferred_latitude between 56 and 62 and well.preferred_longitude between 1.46666667 and 3) or (well.preferred_latitude between 62.16666667 and 62.5 and well.preferred_longitude between 1.46666667 and 3)) and wellbore.country_name='United Kingdom') or (((well.preferred_latitude between 58.41666667 and 62 and well.preferred_longitude between 3.16666667 and 4.16666667 and wellbore.country_name='Norway')))) and (well.preferred_latitude IS NOT NULL and well.preferred_longitude IS NOT NULL)

Checking SyncJob: *** cds_sync_sample.STUDY_WELLS ***




CDS AOI=(wellbore.country_name IN ('Italy','Spain','France')) and (well.preferred_latitude IS NOT NULL and well.preferred_longitude IS NOT NULL)

Checking SyncJob: *** MYOWDISTRICT.myowproject ***


CDS AOI=((x_min >= 1000 and x_max <= 3000 and y_min >= 1000 and y_max <= 3000) or (x_min >= 200 and x_max <= 500 and y_min >= 200 and y_max <= 500)) and coordinate_system = 'World Geodetic System 1984'….

{cdssync}%

This prints out the project name along with the Area of Interest converted to a Corporate Data Store™ SQL where clause.

Backup Verification

The current status of the project backups can be tested using the “runCheckBackups” script. This will also test the database connections as well as the FTP method for verification of the project backup file. For example:

{cdssync}% pwd


{cdssync}% ./runCheckBackups

(…)

Got 3 jobs

(…)

Mar 23, 2010 11:21:02 PM com.lgc.dam.cds.owsync.backup.FTPRunnerImpl writeBackupFile

INFO:

Calling /d01/cds/pehome/sync/bin/runFTP_wrap with Ljava.lang.String;@7e3bc473

OUTPUT>machine= myftpmachine

OUTPUT>user= ora_backup

OUTPUT>pass= ora_passwd

OUTPUT>dir= /ora_data/orabackup/ow_proj_backups



OUTPUT>sid= MYOWDISTRICT

OUTPUT>project= myowproject

OUTPUT>output= /d01/cds/pehome/sync/tmp/MYOWDISTRICT.myowproject.backup.txt

ExitValue: 0

Mar 23, 2010 11:21:02 PM com.lgc.dam.cds.owsync.backup.FTPRunnerImpl writeBackupFile

INFO:

Finished /d01/cds/pehome/sync/bin/runFTP_wrap gave 0

Mar 23, 2010 11:21:02 PM com.lgc.dam.cds.owsync.backup.BackupVerifierImpl verify

INFO:

Backup verification took 0.14 seconds

Finished backup checker. Output written to ../tmp/backups.txt

{cdssync}%

The “sync/tmp/backups.txt” file will show the current state of backup verification, for example:

{cdssync}% cat ../tmp/backups.txt

cds_sync_sample.STUDY_NORTH backup: OK

cds_sync_sample.STUDY_WELLS backup: OK

MYOWDISTRICT.myowproject backup: OK

{cdssync}%

The “OK” shows that both database and file backup verification has been successful for the projects. A “FAIL” would indicate that a suitable backup has not been found for the project. If Corporate Data Store™ - OpenWorks® Synchronization were to run, then that project would be skipped.

Check Connections

The “runCheckConnections” script can be used to validate the Corporate Data Store™ and OpenWorks® database and PowerHub™ connection details entered in the PowerExplorer® “Global



Configuration” and “Job” tasks. It will also validate the avaibility of Landmark licenses.

For example:

{cdssync}% pwd


{cdssync}% ./runCheckConnections

(…)

Executing alter session set current_schema=cds_dev

PowerHub(client) 5000.2.1 connecting to //mymachine/pe_dic-server

PowerHub(client) 5000.2.1 connected to //mymachine/pe_dic-server (PowerHub 5000.2.1) 0.092 seconds

Logged in to PowerHub. 0.168 seconds

Checking connections for cds_sync_sample.STUDY_NORTH

Checking connections for MYOWDISTRICT.myowproject

Finished connection checker. Output written to ../tmp/conn.txt

{cdssync}%

The “sync/tmp/conn.txt” file contains the results of the connection checks. The connections performed are:

Corporate Data Store™ database – JDBC connection

Corporate Data Store™ database – PowerHub™ connection

OpenWorks® projects – JDBC connection

OpenWorks® projects – PowerHub™ connection

The results will show “OK” for a good connection and “FAIL” for a bad connection. A bad connection is likely to be the result of typos in the configuration or occasionally a problem with license availability (for PowerHub). Example of results:

{cdssync}% head ../tmp/conn.txt

# Good connections=6 # Bad connections=0

CDS JDBC Connection: OK



CDS PH Connection: OK

cds_sync_sample.STUDY_NORTH OW PH Connection: OK

cds_sync_sample.STUDY_NORTH JDBC Connection: OK

MYOWDISTRICT.myowproject OW PH Connection: OK

MYOWDISTRICT.myowproject JDBC Connection: OK

Check optimization results

The “runOptimize” script performs the optimization checks on Corporate Data Store™ database to find whether or not any wellbores have been updated for the seven main datatypes supported by Corporate Data Store™ – OpenWorks® Synchronization: wellbore information (well header), deviation data (directional surveys and position logs), time-depths, stratigraphy (including picks), material samples, well test, and wellbore mechanical.

For the “Interpretation Data” Sync_type, the script performs the optimization checks on Corporate Data Store™ to determine whether or not any of the seven top-level GeoMaps (contour set, fault center line set, grid, mapping polygon set, point set) and Seismic datatypes (seismic 2D line, seismic 3D survey) have been updated.

Note: Some limitations exist with this script:

any new wellbores or any of the seven interpretation data datatypes added to Corporate Data Store™ database within the project’s AOI will not be included.

will not work on projects which have not previously been synchronized.

This is due to the fact that the Corporate Data Store™ database select list used for optimization is created/refreshed by the Corporate Data Store™ – OpenWorks® Synchronization process and not by the optimization process.

A example of running “runOptimize” script is given below:

{cdssync}% pwd


{cdssync}% ./runOptimize

(…)



Mar 24, 2010 11:00:23 AM com.lgc.dam.cds.owsync.verify.DoOptimize process

INFO:

Last run date was 2010-01-01

Mar 24, 2010 11:00:23 AM com.lgc.dam.cds.owsync.verify.DoOptimize process

INFO:

Messages:

Found 1 wellbores for synchronization.

Found 1 wellbores missing from OpenWorks.

Finding CDS selection from AOI took 2.29 seconds

Found 1 updates in cds_well for 1 wellbore

Found 1 updates in cds_well_operator for 1 wellbore

Found 1 updates in cds_wellbore for 1 wellbore

Optimize: Found 1 for well_header. Took 0.07 seconds

Found 1 updates in cds_computed_lithology_header for 1 wellbore

Found 1 updates in cds_computed_lithology_curve for 1 wellbore

Optimize: Found 1 for stratigraphy_without_picks. Took 0.01 seconds

Optimize: Found 0 for picks. Took 0 seconds

Optimize: Found 0 for dir_survey. Took 0.01 seconds

Optimize: Found 0 for time_depth. Took 0 seconds

Optimize: Found 0 for material_sample. Took 0.01 seconds

Optimize: Found 0 for wellbore_mechanical. Took 0.02 seconds

Optimize: Found 0 updated wellbores for picks. Took 0 seconds

Finished optimize. Output written to ../tmp/optimize.txt

{cdssync}%



The output is written to the “sync/tmp/optimize.txt” file, which contains a list of how many wellbores or top-level geomaps and seismic datatypes were updated for each datatype, for example:

{cdssync}% more ../tmp/optimize.txt

***** Starting Optimize for MYOWDISTRICT.myowproject *****

Found 1 wellbores

Last run date=2010-01-01

well_header: 1 updates

stratigraphy_without_picks: 1 updates

picks: 0 updates

dir_survey: 0 updates

time_depth: 0 updates

material_sample: 0 updates

wellbore_mechanical: 0 updates

Stratigraphy (inc. picks): 0 updates

***** Finished Optimize for MYOWDISTRICT.myowproject *****

Check data selection results

The Area of Interest definition for the project can be tested with the “runDataSelection” script. This script will connect to the OpenWorks® project and Corporate Data Store™ databases and perform the wellbore, geomaps or seismic selection phase of the Corporate Data Store™ –OpenWorks® Synchronization process. It will put the results of the selection into an ASCII file.

For example:

{cdssync}% pwd


{cdssync}% ./runDataSelection

Will produce one file for each project in the sync/tmp directory:

{cdssync}% pwd




{cdssync}% ls –l *.txt

-rw-rw-r-- 1 cdssync users 304 Mar 24 11:07 myowproject.txt

-rw-rw-r-- 1 cdssync users 304 Mar 24 11:07 STUDY_NORTH.txt

-rw-rw-r-- 1 cdssync users 304 Mar 24 11:07 STUDY_SOUTH.txt

-rw-rw-r-- 1 cdssync users 304 Mar 24 11:07 STUDY_WELLS.txt

{cdssync}%

The .txt file contains a list of the wellbores or top-level geomaps and seismic datatypes within the Area of Interest for that project.

For example:

{cdssync}% head STUDY_WELLS.txt

cds_sync_sample.STUDY_WELLS

(wellbore.country_name IN ('Italy','Spain','France','United Kingdom')) and (well.preferred_latitude IS NOT NULL and well.preferred_longitude IS NOT NULL)

# CDS wellbores=916

# OW wellbores=926

total=916 wellbores for synchronization

{cdssync}%

This prints the Area of Interest in Corporate Data Store™ SQL, together with a count showing that 916 wellbores were found in Corporate Data Store™ database and that 926 “corporate” wellbores were present in OpenWorks® projects. Which suggests 10 corporate wellbores were added to OpenWorks® projects outside of defined the Area of Interest.

The rest of the file contains a listing of the wellbores to be synchronized, including the source of the wellbore:



“both” – the wellbore is within the Area of Interest and exists in both Corporate Data Store™ database and OpenWorks® projects.

“CDS” – the wellbore is within the Area of Interest but exists only in Corporate Data Store™ database and not in OpenWorks® server.

“OW” – the wellbore exists in OpenWorks® projects but does not fall within the defined Area of Interest.

19000099997201,211/24-1,Italy,CDS

19000099997202,211/24-1Z,Spain,CDS

19000099997301,211/24-2,UK,OW

19000099997401,211/24-3,United Kingdom,both

…



Running the synchronization process

The Corporate Data Store™ – OpenWorks® Synchronization process can be run manually from the command line or automatically as part of a scheduled UNIX “cron” job.

Run from command line

Running the synchronization process

To run the synchronization process follow the steps below

Login with appropriate LINUX/UNIX user

Change to the “sync/bin” directory

Execute the “runSync” script

For example:

{cdssync}% ./runSync

Starting CDS-OW sync.

Please check ../logs/2006-05-08_20:31_sync_console.out for status

Note: Do not type “Ctrl-C” in this window unless you wish to abort the synchronization process.

The synchronization process will print to the window when it has finished and restore the UNIX prompt, for example:

{cdssync}% ./runSync

Starting CDS-OW sync.

Please check ../logs/2006-05-08_20:31_sync_console.out for status

Finished CDS-OW sync.

{cdssync}%

Check your email in-box for the email notification, with subject “CDS Synchronization Summary Report”.

Running the synchronization process 72


Checking the status of the synchronization process

There are two ways to check the status of the synchronization process after it has been started:

Check the console log file

Check the Advanced Data Transfer™ transfer log file

The console log will print-out status from the various phases of the synchronization process, for example selecting wellbores within Area of Interest, cascade delete, running batch Advanced Data Transfer™ software and updating the well lists in Corporate Data Store™ database and OpenWorks® projects. The Advanced Data Transfer™ software transfer log file shows the status of the batch Advanced Data Transfer™ process.

Console log file The console log file is found in sync/logs directory and is named with a time-stamp at the time the “runSync” script is executed.

Change to sync/logs directory

Type “ls –altr” to find the lastest (ie active) console file

Type “tail –f” to use the UNIX tail command to print synchronization status updates in the file to the window

If the console output may “pause” while it waits for batch Advanced Data Transfer™ software to finish, in which case the following text will be displayed:

++++++++++++++++++++++++++++++ doRun() ++++++++++++++++++++++++++++++++++++++++

jobName=OWPROD.CDS_V180_TO_OW_UTM31.20060508_2023.well_header

jobFile=/glb/home/usjea0/dev/sync/adt_files/OWPROD.CDS_V180_TO_OW_UTM31.20060508_2023.well_header_session.xml

jobFile=/glb/home/usjea0/dev/sync/adt_files/OWPROD.CDS_V180_TO_OW_UTM31.20060508_2023.well_header_session.xml

May 8, 2006 8:23:28 PM com.lgc.dam.cds.owsync.runadt.BatchAdtRunnerImpl run

INFO:

Calling /glb/home/usjea0/dev/sync/bin/runBatchADT with OWPROD.CDS_V180_TO_OW_UTM31.20060508_2023.well_header,/glb/home/usjea0/dev/sync/adt_files/OWPROD.CDS_V180_TO_OW_UTM31.20060508_2023.well_header_session.xml

….



(…..)

Mon May 08 20:23:51 CEST 2006: ERROR> Using In-Process Message Server.

Mon May 08 20:23:51 CEST 2006: ERROR>

Mon May 08 20:24:08 CEST 2006: ERROR> May 8, 2006 8:24:08 PM com.lgc.im.dataio.db.objectserver.WriterImpl jobEvent

Mon May 08 20:24:08 CEST 2006: ERROR> SEVERE: Starting database writer.

The “ERROR>” text printed here does not signify that an error has occurred in Advanced Data Transfer™ software, but simply that “standard error” is being used to pass back messages to the console.

When the console log file “stops” at this position, check the Advanced Data Transfer™ transfer log file for status. The console log will display the following text when the sync process is complete:

************************ FINISHED CDS-OW SYNC at Mon May 08 20:32:29 CEST 2006 took 48.49 seconds************************

Advanced Data Transfer™ transfer log file The Advanced Data Transfer™ transfer logs are generated for each batch Advanced Data Transfer™ software run. They are found in the sync/adt_files directory.

Change to sync_adt/files directory

Type “ls –altr” to find the latest (current) Advanced Data Transfer™ transfer log

Type “tail –f” to see what Advanced Data Transfer™ software is doing

Advanced Data Transfer™ transfer messages will scroll past:

FINE: SkipRedundant: VcCompany: companyName=UNKNOWN

INFO: SkipRedundantTLS: WellEntire: uwi=11000010021201 Cumulative Top Levels: = 1

FINE: Insert: TimeDepthTable: wellid=11521 tdName=RAMOS-CHK-FIELD B D46

FINE: processed TimeDepthTable children of WellEntire: uwi=11000010021201



When finished the Advanced Data Transfer™ log will show its usual summary output:

WARNING: Job Summary:



1 VcCompany rows skipped due to matching data

1 TimeDepthTable rows successfully inserted

7 WellEntire rows skipped due to matching data

WARNING: Finished database writer 05/08/2006 08:28:53.457 PM

Disconnecting from message server.

Jobname: OWPROD.CDS_V180_TO_OW_UTM31.20060508_2023.time_depth

reason: Normal end of data

End of job JVM memory statistics:

Used (internal JVM): 30.0 Mb

Free (internal JVM): 44.0 Mb (59.0%)

JVM size: 74.0 Mb

JVM Max available: 644.0 Mb (96.0%).

JVM Max allowable: 674.0 Mb

Aborting the synchronization process

The Corporate Data Store™ – OpenWorks® Synchronization process can be aborted by simply pressing “Ctrl-C” in the window in which the “runSync” was launched. The current project on which the synchronization process was working could have had some modifications from Corporate Data Store™ database (for example, deletes) but not others (batch Advanced Data Transfer™ inserts or deletes). However the “last run date” will remain at the date of the previous successful synchronization process, so Corporate Data Store™ – OpenWorks® Synchronization can simply be re-run for the full changes to take effect.

Note: You may need to manually delete any project lock files (.lck) from sync/tmp directory before re-running synchronization after a manual abort. If this is not done then these projects could be “skipped” by the synchronization process.

The transaction size for the batch Advanced Data Transfer™ process can be adjusted to set the “commit interval”. This is set in the Advanced Data Transfer™ session file templates in the sync/adt_templates directory:

<Name>Transaction batch size</Name>



<Type>java.lang.Integer</Type>

<Value>20</Value>

Here the commit occurs after every 20 records. Setting a higher value (e.g. 1000000000) would ensure commits only occur at the end of the Advanced Data Transfer™ transfer job. However there would need to be sufficient Oracle temp/rollback segment space and this could create prevent other applications from writing to OpenWorks® projects whilst the batch Advanced Data Transfer™ process was running.

Running synchronization processes in parallel

It is possible to run several synchronization processes in parallel, but these processes are all using the same job definition as defined in the PowerExplorer® “Synchronization -> CDS to OpenWorks” tasks.

Each Corporate Data Store™ – OpenWorks® Synchronization process will create a “lock” file in the sync/tmp directory for a specific project. For example:

bash-2.05b$ pwd /glb/home/s_cdsync/sync/tmp bash-2.05b$ ls -altr *lck -rw-rw-rw- 1 s_cdsync u_010089 0 Apr 12 21:31 OWPROD.CDS_SYNRUSSIA.lck -rw-rw-rw- 1 s_cdsync u_010089 0 Apr 12 21:32 OWPROD.CDS_SYNC_NIGERIA.lck bash-2.05b$

Shows two lock files from two different Corporate Data Store™ – OpenWorks® Synchronization process, one working on “..SYNRUSSIA” project, the other on “..NIGERIA”.

The results email will flag projects as “skipped” if the synchronization process finds that the lock file for that project already exists, which indicates another process is working on the project at the same time, for example:

CDS-OW synchronization run for 14 projects. Took 1 minutes. Overall time was 5.41 minutes unchanged OWPROD.CDS_SYNC_PROJECTA skipped OWPROD.CDS_SYNC_USWEST unchanged OWPROD.CDS_SYNC_NORWAY skipped OWPROD.CDS_SYNC_ENGLAND unchanged OWPROD.CDS_SYNC_GULFOFMEXICO skipped OWPROD.CDS_SYNC_PAKISTAN unchanged OWPROD.CDS_SYNC_INDONESIA skipped OWPROD.CDS_SYNC_AUSTRALIA unchanged OWPROD.CDS_SYNC_FRANCE skipped OWPROD.CDS_SYNC_INDIA unchanged OWPROD.CDS_NAME unchanged OWPROD.CDS_SYNRUSSIA unchanged OWPROD.CDS_SYNC_USEAST skipped OWPROD.CDS_SYNC_USSOUTH



Results in OpenWorks® Projects

The results of the Corporate Data Store™ – OpenWorks® Synchronization process can be flagged in OpenWorks® projects as create_user_id and update_user_id. The create_user_id will be the external LINUX/UNIX user used to run the synchronization process, the update_user_id could either be the external LINUX/UNIX user or the internal database user depending on what changes were performed by the synchronization process.

For example, if the synchronization process is run with the external LINUX/UNIX user “s_cdsync” and the internal OpenWorks® user “s_cdsync_i” the following appears in the OpenWorks® tables:

Uwi Well Name (License) Create Date Create User Id Update Date Update User Id

12000020504001 WELL ABC 4/6/2006 S_CDSYNC 4/28/2006 S_CDSYNC_I

12000020504002 WELL2 4/6/2006 S_CDSYNC 4/28/2006 S_CDSYNC_I

12000020504003 WELL 156 4/6/2006 S_CDSYNC 4/28/2006 S_CDSYNC_I

11000010000001 WELL XYZ 4/6/2006 S_CDSYNC 4/6/2006 S_CDSYNC

11000010003401 START WELL 4/6/2006 S_CDSYNC 4/6/2006 S_CDSYNC

11000010003402 FINISH WELL 4/6/2006 S_CDSYNC 4/6/2006 S_CDSYNC 11000010003403 EXPLORATORY 1 4/6/2006 S_CDSYNC 4/6/2006 S_CDSYNC

11000010003501 INFILL 4 4/6/2006 S_CDSYNC 4/6/2006 S_CDSYNC

The external user (“s_cdsync”) is used by Advanced Data Transfer™ software for inserts and updates. The internal user (“s_cdsync_i”) is used for the temporary workarounds (insert and update) as well as the cascade deletes.

Run as a scheduled cron job

The Corporate Data Store™ – OpenWorks® Synchronization process can be scheduled to run as a regular LINUX/UNIX cron job by the following these steps:

Login as Corporate Data Store™ – OpenWorks® Synchronization LINUX/UNIX account

Type “crontab –e” to bring up the default cron editor

Add an entry for “runSync” for example

05 00 * * * /glb/home/s_cdsync/sync/bin/runSync

~



"crontab.15065" 2L, 49C written

This will run the Corporate Data Store™ – OpenWorks® Synchronization at 12:05 am every day.

Troubleshooting

Error status in email

The general approach to troubleshooting Corporate Data Store™ – OpenWorks® Synchronization issues is to first check for “error” status in the email summary. If any errors occurred, then check the email body for clues. Typically the cause of the error will be flagged.

For example:

CDS-OW synchronization run for 14 projects. Took 15.6 minutes. Overall time was 20.82 minutes unchanged OWPROD.CDS_SYNC_PROJECTA unchanged OWPROD.CDS_SYNC_USWEST changed OWPROD.CDS_SYNC_NORWAY error OWPROD.CDS_SYNC_ENGLAND unchanged OWPROD.CDS_SYNC_GULFOFMEXICO

The email says that the ENGLAND project had an error. The next step is to look in the ENGLAND project’s summary in the email for causes for the error. For example:

Batch ADT failed: Failed to check out CDS license.

Problem running batch ADT: Error running batch ADT at Tue Apr 18 15:36:07 CEST 2006

Shows that the PowerHub™ server or Landmark license server needs to be checked for license availability.

Any errors in the Advanced Data Transfer™ transfer will also cause the project to have “error” status in the email. For example:

ADT wellbore header transfer took 1.19 minutes.


2 ElevInfo rows skipped due to matching data

6 WellStatusHistory rows skipped due to matching data

2 WellEntire rows successfully updated

2 WellEntire rows skipped due to matching data

7 WellUwi rows skipped due to matching data

2 WellUwi rows not transferred due to errors



In this case, the appropriate Advanced Data Transfer™ transfer log file in sync/adt_files should be examined for possible causes of the error.

Note: when a project has “error” in the email summary the Corporate Data Store™ – OpenWorks® Synchronization will not update its “last run date”, which will remain set at the date of the previous successful Corporate Data Store™ – OpenWorks® Synchronization. Thus the next Corporate Data Store™ – OpenWorks® Synchronization process will use the old (last successful) date for that project. This will continue until the “error” status is solved for the project.

PowerHub unavailability

Since Corporate Data Store™ – OpenWorks® Synchronization will typically be run as a cron job in the early morning there may be scheduled maintainence on networks, databases or license servers which cause PowerHub™ server to be unavailable for a short time. For example, the following synchronization summary shows errors for 2 out of 19 projects:

CDS-OW synchronization run for 19 projects. Took 8.32 minutes. Overall time was 8.33 minutes

unchanged OWPROD.CDS_SYNC_AM_IRELAND

unchanged OWPROD.CDS_SYNC_GULF

unchanged OWPROD.CDS_SYNC_PROJECTA

unchanged OWPROD.CDS_SYNC_ENGLAND

unchanged OWPROD.CDS_SYNC_INDONESIA

unchanged OWPROD.CDS_SYNC_NORWAY

error OWPROD.CDS_SYNC_GULFOFMEXICO

error OWPROD.CDS_SYNC_NIGERIA

unchanged OWPROD.CDS_SYNC_PAKISTAN

unchanged OWPROD.CDS_SYNC_AUSTRALIA

unchanged OWPROD.CDS_SYNC_NOV_USWEST

unchanged OWPROD.CDS_SYNC_NSEA_97

unchanged OWPROD.CDS_SYNC_USEAST

unchanged OWPROD.CDS_SYNC_INDIA

unchanged OWPROD.CDS_SYNC_FRANCE

unchanged OWPROD.CDS_SYNC_USSOUTH

unchanged OWPROD.CDS_NAME



unchanged OWPROD.CDS_SYNRUSSIA

unchanged OWPROD.CDS_SYNC_USWEST

The summary shows the order of execution and since GULFOFMEXICO and NIGERIA which are grouped together suggest the same error condition affected the synchronization to each project, but was resolved for the following “PAKISTAN” project. Scrolling down to the error text in the GULFOFMEXICO and NIGERIA shows that the problem occurred in the “select wellbores” process::

----------------------------------------------------------------

Summary for OWPROD.CDS_SYNC_GULFOFMEXICO

Coordinate system=ED50 / TM 0 N

CDS Where clause=((well.preferred_latitude between 57.53333333 and 57.78333333 and well.preferred_longitude between 0.95 and 1.38333333) or (well.preferred_latitude between 57.5 and 57.55 and well.preferred_longitude between 1.2 and 1.38333333) or (well.preferred_latitude between 57.5 and 57.66666667 and well.preferred_longitude between 1.38333333 and 1.6)) and wellbore.wellbore_name NOT LIKE 'FORTIES%' and wellbore.wellbore_name NOT LIKE 'IGS%'

Data types:

Picks=yes

Dir survey=yes

Time depth=yes

Verified database backup for OWPROD.CDS_SYNC_GULFOFMEXICO

Verified file backup for OWPROD.CDS_SYNC_GULFOFMEXICO

Backup verification took 0.99 seconds

Error finding wellbores for OWPROD.CDS_SYNC_GULFOFMEXICO

Error message=com.pgs.dm.slegge.server.rmi.RmiDictionaryImpl_Stub

Select wellbores failed for OWPROD.CDS_SYNC_GULFOFMEXICO

Sync took 4.72 seconds

Error executing sync for OWPROD.CDS_SYNC_GULFOFMEXICO

----------------------------------------------------------------

----------------------------------------------------------------

Summary for OWPROD.CDS_SYNC_NIGERIA

Coordinate system=UTM32



CDS Where clause=((well.preferred_latitude between 62 and 68.41666667 and well.preferred_longitude between 2 and 12 and wellbore.country_name='NORWAY') or (well.preferred_latitude between 61.5 and 62 and well.preferred_longitude between 1 and 4 and wellbore.country_name='NORWAY') or (well.preferred_latitude between 61.25 and 62 and well.preferred_longitude between 4 and 5 and wellbore.country_name='NORWAY'))

Data types:

Picks=yes

Dir survey=yes

Time depth=yes

Verified database backup for OWPROD.CDS_SYNC_NIGERIA

Verified file backup for OWPROD.CDS_SYNC_NIGERIA

Backup verification took 1 seconds

Error finding wellbores for OWPROD.CDS_SYNC_NIGERIA

Error message=Login to application server failed

com.pgs.dm.slegge.server.rmi.RmiConnectionImpl_Stub

Select wellbores failed for OWPROD.CDS_SYNC_NIGERIA

Sync took 1.91 seconds

Error executing sync for OWPROD.CDS_SYNC_NIGERIA

----------------------------------------------------------------

The error text in the summary email does not provide enough to ascertain the cause of the problem, so the console log file needs to be examined for more detail. The console log files are located in the sync/logs directory. For the above errors, the console log file shows a Java stack-trace:

Selecting wellbores within AOI for CDS_SYNC_GULFOFMEXICO

Connecting to //amsdc2-n-s00008/pe_dic-server

Connected to //amsdc2-n-s00008/pe_dic-server

PEServer: java.rmi.UnmarshalException: Error unmarshaling return header; nested exception is:

java.io.EOFException

ERROR: server connection closed.

java.lang.ClassCastException: com.pgs.dm.slegge.server.rmi.RmiDictionaryImpl_Stub



at com.pgs.dm.slegge.server.rmi.RmiDataSourceImpl_Stub.connect(Unknown Source)

at com.lgc.dam.phs.client.dictionary.PhsDataSource.connect(PhsDataSource.java:208)

at com.lgc.dam.phs.client.jdbc.PhsJDBCConnection.<init>(PhsJDBCConnection.java:229)

at com.lgc.dam.phs.client.jdbc.PhsJDBCDriver.connect(PhsJDBCDriver.java:130)

at java.sql.DriverManager.getConnection(DriverManager.java:525)


at com.lgc.dam.cds.company.owsync.connections.ConnectionFactoryImpl.getPHConnectionOW(ConnectionFactoryImpl.java:325)

at com.lgc.dam.cds.company.owsync.selection.SelectWellboresImpl.select(SelectWellboresImpl.java:57)

at com.lgc.dam.cds.company.owsync.run.SyncJobExecutorImpl.doExecute(SyncJobExecutorImpl.java:141)

at com.lgc.dam.cds.company.owsync.run.SyncJobExecutorImpl.execute(SyncJobExecutorImpl.java:69)

at com.lgc.dam.cds.company.owsync.run.SyncRunner.run(SyncRunner.java:88)

at com.lgc.dam.cds.company.owsync.run.SyncRunner.main(SyncRunner.java:58)

ERROR: new PhsJDBCConnection instance creation failed:com.pgs.dm.slegge.server.rmi.RmiDictionaryImpl_Stub

java.sql.SQLException: com.pgs.dm.slegge.server.rmi.RmiDictionaryImpl_Stub

at com.lgc.dam.phs.client.jdbc.PhsJDBCDriver.connect(PhsJDBCDriver.java:137)









May 16, 2006 12:07:13 AM com.lgc.dam.cds.company.owsync.connections.ConnectionFactoryImpl getPHConnectionOW

WARNING:

Unable to connect to jdbc:scwapi://amsdc2-n-s00008/pe_dic-server;passwd123;cds_admin;OW2003;OWPROD.CDS_SYNC_GULFOFMEXICO;s_cdsync_i;passwd123

java.lang.Exception: com.pgs.dm.slegge.server.rmi.RmiDictionaryImpl_Stub









May 16, 2006 12:07:13 AM com.lgc.dam.cds.company.owsync.selection.SelectWellboresImpl select

WARNING:


Error message=com.pgs.dm.slegge.server.rmi.RmiDictionaryImpl_Stub

com.lgc.dam.cds.company.owsync.selection.SelectException:


This error print-out should then be sent to the PowerHub administrator for further analysis.

Advanced Data Transfer™ transfer errors

The Corporate Data Store™ – OpenWorks® Synchronization process will look for any mention of the text “error” in the Advanced Data Transfer™ log file and if found will flag the synchronization job to that project as an “error”. Typically the “error” text in Advanced Data Transfer™ software occurs in two situations:

ADT log message Situation

“3 WellUwi rows not transferred due to errors” Did attempt to write data to OpenWorks® projects, but failed

“No data was written, no errors were generated”

No attempt made to write data to OpenWorks® projects, the problem occurred before write attempt could be made

In these situations a useful means to confirm the Advanced Data Transfer® error is to launch ADT in GUI mode and open the job session file created by Corporate Data Store™ – OpenWorks® Synchronization. The transfer can then be re-run in ADT to check the error reported by Corporate Data Store™ – OpenWorks® Synchronization. For more details see Troubleshooting Advanced Data Transfer™ transfers.



Well Note Pad

In order to delete a Wellbore History record on the OpenWorks® side (Well Note Pad) the user has to do a round trip of the data. The user has to transfer the Well Note Pad data into Corporate Data Store™ Wellbore History and then delete the record on the Corporate Data Store™ side. Corporate Data Store™ – OpenWorks® Synchronization will then delete the record.

OpenWorks® project is down

If the target OpenWorks® project is unavailable when Advanced Data Transfer™ software attempts the Corporate Data Store™ – OpenWorks® transfer then the project is flagged with “error” in the email and in the project summary the following text is present:

Problem running batch ADT: Failed to find log file for ADT job :OWPROD.CDS_SYNC_INDONESIA.20060817_0033.well_header at Thu Aug 17 00:34:11 BST 2006 Error occured : message= Problem running batch ADT: Failed to find log file for ADT job :OWPROD.CDS_SYNC_INDONESIA.20060817_0033.well_header at Thu Aug 17 00:34:11 BST 2006

One of the reasons for lack of the Advanced Data Transfer™ log file is that Advanced Data Transfer™ software was unable to connect to the OpenWorks® project. To confirm this, open the “xxx.console.out” file present in the sync/logs directory and scroll down to when Advanced Data Transfer™ software starts to connect to that project, for example:

Thu Aug 17 00:34:04 BST 2006: OUTPUT> Connecting to //amsdc2-n-s00008/pe_dic-server

Thu Aug 17 00:34:04 BST 2006: OUTPUT> Connected to //amsdc2-n-s00008/pe_dic-server

Thu Aug 17 00:34:11 BST 2006: OUTPUT> ORA-01034: ORACLE not available

Thu Aug 17 00:34:11 BST 2006: OUTPUT> ORA-27101: shared memory realm does not exist

Thu Aug 17 00:34:11 BST 2006: OUTPUT> Linux-ia64 Error: 2: No such file or directory

No email notification

If no email notification has been received, there are two likely causes.

First, the Corporate Data Store™ – OpenWorks® Synchronization process could still be running. In which case, check the status of the console and Advanced Data Transfer™ transfer log files described above.

Second, the Corporate Data Store™ – OpenWorks® Synchronization process could have been “killed” –either manually or from the



operating system. In this case, check the contents of the console log file to see what may have caused the problem.

Advanced Data Transfer™ hangs

If the scheduled sync process does not send out an email notification and subsequent attempts to investigate what has happened show that the synchronization process is still running and is waiting for batch Advanced Data Transfer™ software to return, it is possible to manually abort batch Advanced Data Transfer™ software, yet still allow the synchronization process to continue. The project for which the batch Advanced Data Transfer™ process was aborted will be flagged as “error” by the synchronization process.

Example for this scenario:

Expected email notification from scheduled synchronization process at 12:05 am not received

Check latest console log file under sync/logs directory

Console log file not updated since 12:24 am

Use “ps –ef |grep <sync user>” to show active processes

Active processes shown for <sync user>

Tail console log file, shows “calling batch ADT” as status

Check latest Advanced Data Transfer™ transfer log file under sync/adt_files directory

Advanced Data Transfer™ transfer log file shows no updates since 12:25 am

Use “ps –ef |grep <sync user> | grep ADT” to show active Advanced Data Transfer™ processes

Stop the Advanced Data Transfer™ processes with “kill -9”

Check the console log file in sync/logs – the sync process should show continuing status

The console log file should show a record of any system errors reported by Advanced Data Transfer™ when it was “hung”.



Network configuration issues

Since the synchronization process makes several calls to networked machines and databases there may be occasions when network configuration changes affect the scheduled synchronization process. For example, if no email notification is received, and subsequent checking of the console log file shows “Verifying backup for <project>”:

bash-2.05b$ tail -f 2006-11-28_23:05_sync_console.out

Nov 28, 2006 11:07:05 PM com.lgc.dam.cds.company.owsync.run.SyncJobExecutorImpl doExecute

INFO:

=========================== Starting sync for AM_IRELAND at Tue Nov 28 23:07:05 GMT 2006 ===========================

Nov 28, 2006 11:07:05 PM com.lgc.dam.cds.company.owsync.run.SyncJobExecutorImpl doExecute

INFO:

Verifying backup for AM_IRELAND

The “Verifying backup..” is the last entry in the console log file and suggests that the Corporate Data Store™ – OpenWorks® Synchronization process is “stuck” in the backup verification process. In the case above, the problem was that network configuration changes caused the “AM_IRELAND” project to be unavailable to the Corporate Data Store™ – OpenWorks® Synchronization process and so caused it to enter a “hanging” state. The solution is to simply find and kill the Java process for the Corporate Data Store™ – OpenWorks® Synchronization, then remove the lock file for that project. For example:

bash-2.05b$ ps -ef |grep s_cdsync |grep java

s_cdsync 23035 23009 0 Nov28 ? 00:00:00 /usr/bin/ksh ./runSync_java

s_cdsync 23037 23035 0 Nov28 ? 00:00:40 java -cp /glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/CUSTOM/sync/cds2ow/jars/cds_sync.jar:/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/www/jars/phs.jar:/glb/apps/3rdparty/oracle/jdbc/lib/ojdbc14.jar:/glb/apps/3rdparty/PowerExplorer

s_cdsync 2561 14962 0 15:22 pts/4 00:00:00 grep java

bash-2.05b$

bash-2.05b$ kill -9 23037

bash-2.05b$

bash-2.05b$ pwd

/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/CUSTOM/sync/cds2ow/tmp



bash-2.05b$ ls -altr *lck

-rw-rw---- 1 s_cdsync u_010089 0 Nov 28 23:07 OWPROD.AM_IRELAND.lck

bash-2.05b$ rm OWPROD.AM_IRELAND.lck

bash-2.05b$

To confirm that network configuration issues have been resolved, run the “runCheckConnections” script, for example:

bash-2.05b$ pwd

/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/CUSTOM/sync/cds2ow/test

bash-2.05b$ ./runCheckConnections

CLASSPATH /glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/CUSTOM/sync/cds2ow/jars/cds_sync.jar:/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/www/jars/phs.jar:/glb/apps/3rdparty/oracle/jdbc/lib/ojdbc14.jar:/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/jars/mail.jar:/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/jars/mailapi.jar:/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/jars/activation.jar:/glb/apps/3rdparty/PowerExplorer/r2003.13/LinuxRH_73/jars/jdom.jar

Starting connection checker

…

Finished connection checker. Output written to ../tmp/conn.txt

bash-2.05b$ cat ../tmp/conn.txt

# Good connections=44 # Bad connections=0

The synchronization process can now be run again manually or left for the scheduled nightly job.



Special workflows

Swapping wellbore alias names in Corporate Data Store™ database

The requirement to swap wellbore alias names between two different wellbores requires a multi-step process in order to synchronization the results into OpenWorks® projects. Certain datatypes in Corporate Data Store™ database and OpenWorks® projects have unique database constraints which prevent duplicate versions of data being stored. For example, a wellbore alias of a certain type (e.g. DTI/CDA) must be unique within the Corporate Data Store™ database and OpenWorks® projects. This causes problems when data need to be cleaned-up, for example when swapping the alias between two different wellbores.

Since the database unique constraints cannot be relaxed, the workaround is to perform the alias swap as a sequence of separate steps. This is shown below:

Special workflows 88


Step 1. Initial state

The aim is to swap the aliases for wellbores “190000999916001” and “19000099991602”.

Step 2. Edit aliases in Corporate Data Store™ database

Change the alias for “19000099991601” to a temporary “dummy” value. For example, you could change the alias to name by adding an the letters “ZZ” to the existing alias. Then change the alias for “91000099991602” by adding, for example, a “K” to the end of existing alias.

Step 3. Save changes and run synchronization

The synchronization performs the updates to OpenWorks® WELL_UWI_ALT:

Found 2 updates to cds_wellbore_alias Optimize: Found 2 updated wellbores for well header. Took 3.86 seconds ADT wellbore header transfer took 1.03 minutes. WARNING: Job Summary: 2 ElevInfo rows successfully updated 6 WellStatusHistory rows skipped due to matching data 2 TdInfo rows skipped due to matching data 3 RDataAcqType rows skipped due to matching data 3 WellEntire rows successfully updated 1 WellEntire rows skipped due to matching data 2 WellUwi rows successfully updated 7 WellUwi rows skipped due to matching data



Step 4. Update wellbore alias in Corporate Data Store™ database

Next update the temporary alias for “19000099991601” with the “J” alias.

Step 5. Save changes to Corporate Data Store™ database and run synchronization

The synchronization performs the update to OpenWorks® projects:

Found 1 update to cds_wellbore_alias Optimize: Found 1 updated wellbores for well header. Took 3.86 seconds ADT wellbore header transfer took 56.02 seconds. WARNING: Job Summary: 1 ElevInfo rows successfully updated 3 WellStatusHistory rows skipped due to matching data 1 TdInfo rows skipped due to matching data 1 RDataAcqType rows skipped due to matching data 1 WellEntire rows successfully updated 1 WellUwi rows successfully updated 4 WellUwi rows skipped due to matching data

Now the aliases for the wellbores have been swapped both in Corporate Data Store™ databases and OpenWorks® projects.



Troubleshooting Advanced Data Transfer™ transfers

Occasionally the batch Advanced Data Transfer™ component of the Corporate Data Store™ – OpenWorks® Synchronization process will give errors. If the error message is not immediately discernable from the Corporate Data Store™ – OpenWorks® Synchronization summary, further invesitgation can be performed using Advanced Data Transfer™ software in GUI mode. The steps to follow are:

Look for batch Advanced Data Transfer™ error in email

Check Advanced Data Transfer™ log file

Find batch Advanced Data Transfer™ session file

Launch Advanced Data Transfer™ with session file

Run transfer

Check output for errors

Step 1. Batch Advanced Data Transfer™ transfer gives error in email

The email summary shows that an error occurred during the batch Advanced Data Transfer™ process:

ADT wellbore header transfer took 1.05 minutes. WARNING: Job Summary: No data was written; no errors were generated. ADT error for transfer OWPROD.CDS_SYNC_INDONESIA.20060516_1050.well_header

Step 2. Check Advanced Data Transfer™ log file

Use the name of the project (e.g. INDONESIA) and datatype (well header) and search the sync/adt_files directory for the latest Advanced Data Transfer™ log file, for example:

bash-2.05b$ ls -altr *INDONESIA*well_header*log

-rw-rw-rw- 1 s_cdsync u_010089 100787 Apr 5 10:51 ADT-CDS_SYNC_INDONESIA.20060405_1046.well_header-060405-104740.639.log







-rw-rw-rw- 1 s_cdsync u_010089 5506 Apr 19 16:49 ADT-OWPROD.CDS_SYNC_INDONESIA.20060419_1647.well_header-060419-164841.867.log





-rw-rw-rw- 1 s_cdsync u_010089 3863 May 3 00:13 ADT-OWPROD.CDS_SYNC_INDONESIA.20060503_0012.well_header-060503-001254.365.log






bash-2.05b$

Check the log file for any useful error messages:

bash-2.05b$ cat ADT-OWPROD.CDS_SYNC_INDONESIA.20060516_1050.well_header-060516-105131.456.log

ADT Log file

Build: 2003.18.0

File created: 05/16/2006 10:51:37.56 AM

=========================================================================================

WARNING: Carto Converter Configuration:

Source SID: "PROJECTA" Target SID: "PROJECTA"

Target Project CRS: "ED50 / TM 0 N"



Conversion scheme: "Must Convert"

Connected to message server.

Jobname: OWPROD.CDS_SYNC_INDONESIA.20060516_1050.well_header

SEVERE: OWPROD.CDS_SYNC_INDONESIA.20060516_1050.well_header started at 05/16/2006 10:51:37.268 AM

description: SOURCE: CDS5000://[email protected]_EPECDS PIPELINE: CDS-OWDB TARGET: OpenWorksData://OWPROD.CDS_SYNC_INDONESIA PARTITION: Well Information TIMESTAMP: 060516:105131.580

INFO: WellEntire: uwi=19000099997001 has no surface coordinates related to attribute 'origCrsId'. Fallback conversion logic unavailable.

WARNING: SUPPRESSING ELEMENT: WellEntire: uwi=19000099997001 due to parameter settings.

FINE: Suppressing element due to business rule 'RULE_PREVENTS_WRITE' AppCordTrfm: sourceCordSys=663 coordinateTrfmNm=ED50**Common Offshore**Bursa 1 rGeodSourceNm=null targetCordSys=370

FINE: Suppressing element due to business rule 'RULE_PREVENTS_WRITE' CoordinateTrfm: coordinateTrfmNm=663_672_Transverse Mercator

FINE: suppressing CordTrfmVal due to parent failure CordTrfmVal: coordinateTrfmNm=663_672_Transverse Mercator rGeodSourceNm=User valueUom=meters remark=null realValue=500000.0 stringValue=null cordTrfmParId=9

FINE: suppressing CordTrfmVal due to parent failure CordTrfmVal: coordinateTrfmNm=663_672_Transverse Mercator rGeodSourceNm=User valueUom=meters remark=null realValue=0.0 stringValue=null cordTrfmParId=10

FINE: suppressing CordTrfmVal due to parent failure CordTrfmVal: coordinateTrfmNm=663_672_Transverse Mercator rGeodSourceNm=User valueUom=unitless remark=null realValue=0.9996 stringValue=null cordTrfmParId=6

FINE: suppressing CordTrfmVal due to parent failure CordTrfmVal: coordinateTrfmNm=663_672_Transverse Mercator rGeodSourceNm=User valueUom=dega remark=null realValue=0.0 stringValue=null cordTrfmParId=7

FINE: suppressing CordTrfmVal due to parent failure CordTrfmVal: coordinateTrfmNm=663_672_Transverse Mercator rGeodSourceNm=User valueUom=dega remark=null realValue=0.0 stringValue=null cordTrfmParId=8

FINE: Suppressing element due to business rule 'RULE_PREVENTS_WRITE' AppCordTrfm: sourceCordSys=663 coordinateTrfmNm=null rGeodSourceNm=null targetCordSys=672


No data was written; no errors were generated.

WARNING: Finished database writer 05/16/2006 10:51:44.961 AM

Disconnecting from message server.

Jobname: OWPROD.CDS_SYNC_INDONESIA.20060516_1050.well_header

reason: Normal end of data

End of job JVM memory statistics:



Used (internal JVM): 30.0 Mb

Free (internal JVM): 39.0 Mb (57.0%)

JVM size: 69.0 Mb

JVM Max available: 644.0 Mb (96.0%).

JVM Max allowable: 674.0 Mb

bash-2.05b$

In this case there are several warnings, including one about “uwi=19000099997001 has no surface coordinates”. The next step is to try the same transfer from Advanced Data Transfer™ GUI using the same batch Advanced Data Transfer™ session file.

Step 3. Find batch Advanced Data Transfer™ session file

Use the name of the project (e.g. INDONESIA) and datatype (well header) and search the sync/adt_files directory for the latest session file, for example:

bash-2.05b$ ls -altr *INDONESIA*well_header*session.xml

-rw-rw-rw- 1 s_cdsync u_010089 10691 Apr 5 10:46 CDS_SYNC_INDONESIA.20060405_1046.well_header_session.xml



-rw-r--r-- 1 s_cdsync u_010089 10691 Apr 6 16:03 CDS_SYNC_INDONESIA.20060406_1603.well_header_session.xml



-rw-rw-rw- 1 s_cdsync u_010089 10699 Apr 19 16:48 OWPROD.CDS_SYNC_INDONESIA.20060419_1647.well_header_session.xml





-rw-rw-rw- 1 s_cdsync u_010089 10699 May 3 00:12 OWPROD.CDS_SYNC_INDONESIA.20060503_0012.well_header_session.xml








bash-2.05b$

Step 4. Launch Advanced Data Transfer™ software with session file

1. Launch Advanced Data Transfer™ software and use “Job -> Job Definition -> Open” to open the session file.

2. Select “All files” since the batch session files are not saved with “.JOB.xml” syntax.

3. Use a filter (*project*session*) to limit the search down to Advanced Data Transfer™ session files for that project:

4. Select the desired session file and open in Advanced Data Transfer™ software. The transfer job parameters are loaded and Advanced Data Transfer™ software is ready to transfer.

Step 5. Check output for errors

Run the Advanced Data Transfer™ transfer and check output for errors. The output errors are same same as with batch Advanced Data Transfer™ software.

Step 6. Resolve errors

Resolve any errors. Rerun Advanced Data Transfer™ software. When there are no errors in the run you have finished the process.



Time-zone differences

If the Corporate Data Store™ database is in a different time-zone than the machine running Corporate Data Store™ – OpenWorks® Synchronization, this may influence the results of the Corporate Data Store™ – OpenWorks® Synchronization process.

For example:

Corporate Data Store™ database is in CET Corporate Data Store™ – OpenWorks® Synchronization runs

on a machine in BST (one hour behing CET)

1. Data updated in Corporate Data Store™ behind database: update_date is June 30 2006 14:05 CET (June 30 2006 13:05 BST)

2. Last update in synchronization was June 29 00:05 (BST)

3. Synchronization is run manually at June 30 2006 13:45 BST

4. Updates are synchronized from Corporate Data Store™ database to OpenWorks® projects

5. Last update is now June 30 2006 13:45 BST

6. Synchronization is run again, at June 30 2006 13:50 BST

7. Updates are synchronized from Corporate Data Store™ database to OpenWorks® projects: since updates are found at 14:05 (CET) after last run time of 13:45 (BST)

8. Same delete/insert/update operations will be repeated, but since they have already occurred in the earlier synchronization, no changes should be effected on the target OpenWorks® projects

A best practice is to simply avoid running multiple manual synchronization transfers when time-zone differences occur between “sync machine” and “database server”. Leave the synchronization process for the scheduled nightly cron job.



Appendix

Example Area of Interests

Multiple geographic extents and attribute where clause

Job AOI task (record 1)

Where_Clause: and wellbore.country_name='UNITED KINGDOM'

AOI Extent task (record 1)

Min_Lat: 60deg 50' 0''N

Max_Lat: 61deg 10' 0''N

Min_Long: 1deg 24' 0''E

Max_Long: 2deg 0' 0''E


Min_Lat: 65deg 10' 0''N</min_lat>

Max_Lat: 68deg 20' 0''N</max_lat>

Min_Long: 5deg 36' 0''E</min_lon>

Max_Long: 6deg 0' 0''E</max_lon>

Job AOI task (record 2)


Min_Lat: 60deg 15' 0''N</min_lat>

Max_Lat: 61deg 15' 0''N</max_lat>

Min_Long: 1deg 40' 0''E</min_lon>

Max_Long: 2deg 20' 0''E</max_lon>

Attribute_Where: and wellbore.country_name='NORWAY'

This is resolved into the following SQL:

(((well.preferred_latitude between 60.83333333 and 61.16666667

and well.preferred_longitude between 1.4 and 2)

or

(well.preferred_latitude between 61.16666667 and 61.33333333

and well.preferred_longitude between 1.6 and 2))

Appendix 97


and wellbore.country_name='UNITED KINGDOM')

or

(((well.preferred_latitude between 60.25 and 61.25

and well.preferred_longitude between 1.66666667 and 2.33333333

and wellbore.country_name='NORWAY')))

Note: the attribute where clause can be placed either at the “Job AOI” or “AOI Extent” level.

Text where clause only

Job AOI task:

Where_Clause: wellbore.country_name IN ('UNITED KINGDOM','FRANCE','FAROE ISLANDS')

Gets resolved to the following SQL:

wellbore.country_name IN ('UNITED KINGDOM','FRANCE','FAROE ISLANDS')

Note: In this case there is no geographical extent (“AOI Extent”) so the attribute where clause does not need to include an “and” or “or”. Compare to examples which have a geographical extent – the attribute where clause needs to start with “and” or “or”.

Migrate Corporate Data Store™- OpenWorks® Synchronization R5000 to 5000.2.1

Starting conditions:

The 5000.2.1 Corporate Data Store™ Upgrader assumes that the R5000 Corporate Data Store™ – OpenWorks® Synchronization files are located under the existing $PE_HOME/sync directory. The Upgrader upgrades the existing $PE_HOME in place. It backups the existing R5000 Corporate Data Store™ – OpenWorks® Synchronization configuration into a new $PE_HOME/sync_DD-MM-YY_hh_mm directory and copies the following existing configuration files into the new 5000.2.1 $PE_HOME/sync:

o adt_files / ADTUser.properties o conf / email.xml o conf / local.props

Appendix 98


o jobs / rundate.xml o jobs / syncjobs.xml

After the 5000.2.1 Corporate Data Store™ Upgrader has been run, the current situation is

similar to the following: /d01/cds/pehome/sync_31-03-10_20_45 Contains R5000 Corporate Data

Store™ – OpenWorks® Synchronization configuration

/d01/cds/pehome/sync Contains 5000.2.1 Corporate Data Store™ – OpenWorks® Synchronization configuration:

- new 5000.2.1 files - the aforementioned R5000

files

The target OpenWorks® project has been patched from R5000 to OpenWorks® 5000.0.2.2.

Impact on Corporate Data Store™ select list naming – The naming of the Corporate Data

Store™ select lists used for managing the sync process has changed from the <DISTRICT>.<PROJECT> convention to <Job_s SK>_<DATATYPE>, where DATATYPE is one of the following top-level data types:

o WELLBORE o CONTOUR_SET o FAULT_CENTER_LINE_SET o GRID o MAPPING_POLYGON_SET o POINT_SET o SEISMIC_LINE_2D o SEISMIC_SURVEY_3D

Last run date for the synchronization jobs – Navigate to the PowerExplorer® “Job” task

and set the “Last Successful Run” date to AFTER Corporate Data Store™ was upgraded, as the upgrade process will have caused update_dates to change for some dates.

The ADTUser.properties file from the R5000 sync/adt_files directory was automatically

migrated over to the new 5000.2.1 sync/adt_files directory by the Corporate Data Store™ Upgrader. This has been tested and is compatible with the 5000.2.1 Corporate Data Store™ – OpenWorks® Synchronization. After you install the 5000.2.1 Advanced Data Transfer™ software, you can choose to overwrite the sync/adt_files/ADTUser.properties file with the one from the 5000.2.1 $ADT_HOME directory. But ensure that you update the default UOM, the OpenWorks® server and Corporate Data Store™ monikers and login values.

Appendix 99


Appendix 100

After the migration process, the test scripts under the sync/test folder can be run to verify the migrated configuration.

Support for OpenWorks® Interpretation Project:

User can configure and transfer the data into the interpretation project without any change in configuration. Corporate Data Store™ – OpenWorks® Synchronization application will recognize interpretation project and master project and create OpenWorks® moniker accordingly.

corporate data store™ - openworks® synchronization user

Documents