Geoprobe Ow Dataserver 1.8.1: Release Notes

Landmark GeoProbe OW DataServer
GeoProbe
OW DataServer 1.8.1
Release Notes
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
System Recommendations
SGI ..................................... 3
SUN .................................... 3
Linux. ................................... 4
Installation
IRIX . .................................... 7
Solaris .................................. 8
Linux. ................................... 9
Verifying the Installation . . . . . . . . . . . . . . . . . . . . . 10
Customizing the installation . . . . . . . . . . . . . . . . . . 11
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Enhancements and New Functionality . . . . . . . . . 17
Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.8.1 Release Notes Page 1 of 20 April 2006

Introduction
This document contains information pertinent to the GeoProbe OW DataServer 1.8.1 release. Both
system administrators and users should read it carefully. The Known Problems section is
particularly important. Reading this section prior to using the software will assist you in attaining
maximum performance from the application.
GeoProbe OW DataServer is used to move data between Landmarks OpenWorks/SeisWorks and

GeoProbe. The 1.8.1 release supports the transfer of the following data types:
Seismic Data
Using GeoProbe OW DataServer, users can migrate their 2D (.2v2_glb) and 3D (.3dh,
.3dv, .bri, .cmp) seismic data from SeisWorks to GeoProbes 2D data format (.2dd) and
volume format (.vol), respectively.
Horizons
GeoProbe OW DataServer allows users to transfer SeisWorks horizons to GeoProbe
horizons (.hzn) and gridview surfaces (.gvw), and to transfer GeoProbe horizons and
surfaces back to the SeisWorks database.
Faults
Fault data from OpenWorks can be transferred to GeoProbes Faults subdirectory as
ezFaults (.eds), and vice versa. In addition, GeoProbe OW DataServer allows the user to
transfer OpenWorks fault data as GeoProbe Shape files (Open Inventor .iv format).
Well Data
Using GeoProbe OW DataServer, well related data including well trajectory, well markers,
well logs, checkshots and synthetics in OpenWorks can be transferred to GeoProbe well
formats (.wl, .wl.dat).
Colormaps
OpenWorks colormaps (.clm) can be transferred to GeoProbe as *.clm files, at which point
the user can save them to *.gpc files after manipulation.
Map Overlays
Map overlays (.zgf) from OpenWorks can be transferred to GeoProbe shape files (.iv).

System Recommendations
The hardware and software recommendations for GeoProbe OW DataServer are listed below.
Operating Systems
GeoProbe OW DataServer was tested on the following configurations:
SGI
IRIX version 6.5.25m operating system.
The best way to determine if an existing system can run GeoProbe OW DataServer is to check the
SGI system model and version of IRIX (the operating system). To determine the IRIX version of
an existing system, type the following command in a shell window:
% uname -R
SUN
Solaris 8, update 7 (2/02) operating system (which includes Sun OS 5.8).
SUN system model and version of Solaris (the operating system). To determine the Solaris version
of an existing system, type the following command in a shell window (8 or 5.8 may be returned,
either is correct):
% cat /etc/release

Linux
GeoProbe OW DataServer was tested on Linux 32-bit workstations with Red Hat EWS 3.0,
Update 4 and on Linux 64-bit workstations with Red Hat EWS 3.0, Update 6 with the mptfusion
fix detailed below:
In Red Hat Enterprise Linux 3 Update 6, Red Hat and Landmark Graphics located an issue with the
mptfusion driver version 2.06.16i.01 within the Direct I/O codepath. This will be corrected in the
upcoming release of Red Hat Enterprise Linux 3 Update 7 which is due out in February 2006.
In the interim, we have provided instructions on removing this module from the Red Hat Enterprise Linux
3 Update 6 and installing another version of the mptfusion driver to rectify this issue (see instructions
below). Red Hat will provide limited support if you update this module and may ask that the issue is
reproduced on a Red Hat stock kernel.
To avoid potential support ramifications or complications, Red Hat and Landmark Graphics request that
you update to Red Hat Enterprise Linux 3 U7, once it becomes available and has been tested with
GeoProbe, as it addresses the Direct I/O codepath issue.
To replace the mptfusion driver, you will require files from Red Hat Enterprise Linux 3 Update 5. These
files are stored in the GeoProbe installation directory: ${GEOPROBE_HOME}/GeoProbe/Linux64/
3.2.2/RPM. Here is the procedure for replacing these file and remaking the boot images for both the EL
and ELsmp kernels:
% cd /lib/modules/2.4.21-37.EL/kernel/drivers/message/fusion/
% mv mptbase.o mptbase.o-stock
% mv mptscsih.o mptscsih.o-stock
% cp ${GEOPROBE_HOME}/Linux64/3.2.2/RPM/mptbase.o.EL mptbase.o
% cp ${GEOPROBE_HOME}/Linux64/3.2.2/RPM/ mptscsih.o.EL mptscsih.o
% cd /lib/modules/2.4.21-37.ELsmp/kernel/drivers/message/fusion/
% mv mptbase.o mptbase.o-stock
% mv mptscsih.o mptscsih.o-stock
% cp ${GEOPROBE_HOME}/Linux64/3.2.2/RPM/mptbase.o.ELsmp mptbase.o
% cp ${GEOPROBE_HOME}/Linux64/3.2.2/RPM/ mptscsih.o.ELsmp mptscsih.o
% cd /boot
% ls init*
% mv initrd-2.4.21-37.EL.img initrd-2.4.21-37.EL.img-stock
% mkinitrd /boot/initrd-2.4.21-37.EL.img 2.4.21-37.EL
% mv initrd-2.4.21-37.ELsmp.img initrd-2.4.21-37.ELsmp.img-stock
% mkinitrd /boot/initrd-2.4.21-37.ELsmp.img 2.4.21-37.ELsmp
% more /proc/scsi/mptscsih/0
% more /proc/scsi/mptscsih/1
% dmesg
% sync
% reboot
Linux system model and version of Linux (the operating system). To determine the Linux version
of an existing system, type the following command in a shell window:
% uname -s -r

Software
GeoProbe OW DataServer 1.8.1 has been tested for use in conjunction with Landmarks
OpenWorks 2003.12 release.

Installation
Installing GeoProbe OW DataServer requires several steps to copy files to the computer, check the
hardware and set environmental variables.
Before installing, it is a good idea to determine if the workstation can run GeoProbe OW
DataServer. Check the System Recommendations first.
WARNING!
Do not install this software when running as root on your UNIX workstation.
Installing GeoProbe OW DataServer as root will limit the write permissions to the
data directories. Running the program as root is also not recommended.
Accessing the CDROM
The files on a CDROM drive are normally under /CDROM on IRIX, /cdrom/cdrom0 on Solaris
and /mnt/cdrom on Linux. After you place the CD in the drive, wait a minute before the files appear
in this directory.
Some workstations may not have a CDROM drive. Check with the system administrator on how
to remotely mount the CDROM. As a last resort, use ftp to copy all the files from the CDROM to
a temporary directory and install from that directory.
Before you Begin
If there is a prior production installation of DataServer and this is an update to that production
installation, then all users should run the following utility to shut down DataServer itself and
TaskLogServer. (TaskLogServer is a utility started in the background by an initial DataServer
session and which runs until it times out after not seeing a DataServer session for 10 hours.)
% Dataserver/<OS>/bin/kill_servers

IRIX
Install GeoProbe OW DataServer from a Distribution CD
To install GeoProbe OW DataServer from the Distribution CDROM, perform the following steps
in a shell window. Please note that the directory /home/magic is used only as an example.
GeoProbe OW DataServer will install and run in any directory configuration, but it does need its
own directory. Make sure Read and Execute permissions are available to all users planning to run
this program.
Using an Appserver
When GeoProbe OW DataServer is installed, it determines the operating system

from the machine being installed upon. It is therefore important to install the
Solaris executable from a SUN and the IRIX executable from an SGI. The
installation can be put on any networked drive, even on Linux. This enables the
use of an Appserver, where all the installations are on a single server.
1. Go to the location where you wish to install the application. The installation script will create
a GeoProbe OW DataServer Install Directory in this location. For example:
% cd /home/magic
2. Determine the location of the installation media (such as /CDROM/cd_owds181Ir64 for Irix)
and the Install directory (such as /home/magic). Run the following command, optionally
specifying the installation media as SOURCE and Install directory as TARGET. Please
specify the SOURCE and TARGET directories using absolute paths (starting with /). If the
TARGET directory is the same as your current working directory (pwd), you may omit
TARGET=/home/magic. If the path of the makefile (gpinst.mk) is the same as the installation
media, you may omit SOURCE=/CDROM/cd_owds181Ir64.
% /bin/make -f /CDROM/cd_owds181Ir64/gpinst.mk dataserver

[SOURCE=/CDROM/cd_owds181Ir64] [TARGET=/home/magic]
Note
The specific location of the make file may be different on a machine to machine
basis. Check with your IT Administrator for the correct location.

Solaris
this program.
Using an Appserver

% cd /home/magic
2. Determine the location of the installation media (such as /cdrom/cdrom0/owds181Sn64 for

Sun) and the Install directory (such as /home/magic). Run the following command, specifying
the installation media as SOURCE and optionally specifying the Install directory as TARGET.
Please specify the SOURCE and TARGET directories using absolute paths (starting with /). If
the TARGET directory is the same as your current working directory (pwd), you may omit
TARGET=/home/magic.
% /usr/ccs/bin/make -f /cdrom/cdrom0/cd_owds181Sn64/gpinst.mk
dataserver SOURCE=/cdrom/cdrom0/cd_owds181Sn64 [TARGET=/home/
magic]
Note

Linux
this program.
Using an Appserver

% cd /home/magic
2. Determine the location of the installation media (such as /mnt/cdrom/cd_owds181Lx32 for

32-bit Linux and cd_owds181Lx64 for 64-bit Linux) and the Install directory (such as /home/
magic). Run the following command, specifying the installation media as SOURCE and
optionally specifying the install directory as TARGET. Please specify the SOURCE and
TARGET directories using absolute paths (starting with /). If the TARGET directory is the
same as your current working directory (pwd), you may omit TARGET=/home/magic. You
must always include the SOURCE parameter.
% /usr/bin/make -f /mnt/cdrom/cd_owds181Lx32/gpinst.mk dataserver

SOURCE=/mnt/cdrom/cd_owds181Lx32 [TARGET=/home/magic]
or
% /usr/bin/make -f /mnt/cdrom/cd_owds181Lx64/gpinst.mk dataserver

SOURCE=/mnt/cdrom/cd_owds181Lx64 [TARGET=/home/magic]
Note

Verifying the Installation
1. Check that the link bin in the Dataserver/<OS> directory is pointing to the correct version of
GeoProbe OW DataServer, and change if necessary.
2. At some sites, the user's account is automatically configured to access OpenWorks, i.e. the
environment variables used by OpenWorks and SeisWorks are set by the .login or .profile. If
this is not the case, or just to be sure the environment is correct, use the OpenWorks Command
Menu, by clicking on System > Unix Window, to bring up an xterm window. This xterm
window is running a shell that has the environment variables correctly set for accessing
OpenWorks and SeisWorks. If you have more than one version of OpenWorks at your site,
start the correct version of the OpenWorks Command Menu for the data you wish to transfer.
3. In the launched xterm, type:
% cd /home/magic/Dataserver/<OS>/bin
% ./dataserver
A flashscreen will first appear, then the main DataServer window. The title of the window will
specify the OpenWorks Release it is accessing, the DataServer version, and the date of its most
recent component.
4. The first time an account is used, there will be some generated messages in the xterm window
because of missing state files - ignore them because the missing files are automatically created
in ~/gpdslogs,
5. If TaskLogServer is not running, you will see a warning message in the xterm window saying
"failed to resolve task log" - ignore it because Dataserver will automatically start
TaskLogServer in the background.

Customizing the installation
While opening an OpenWorks unix window is useful for checking the base install, it is not
normally convenient for users. There are a number of routes for convenient user access to this
application:
1. At some sites the OpenWorks environment is automatically set up by setting the appropriate
environment variables in the user's login script. In this case, a link to Dataserver/<OS>bin/
dataserver may be placed in a bin directory in the user's path.
2. At some sites the OpenWorks environment is automatically set up by CAI and a GUI button is
created that executes Dataserver/<OS>/bin/dataserver.
3. At sites where the OpenWorks environment is not automatically set up, a script may be used
to correctly set up the environment and then start DataServer. In Dataserver/<OS>/bin there is
an example of a script template:
startDataServer.sh
Edit and configure this template. Then run ./configure to generate the corresponding scripts.
Configuration is simple, just define values for environment variables that correspond to the
correct OpenWorks environment. To see what values to specify, just list the environment
variables (env) in the corresponding OpenWorks window.
4. Generic OpenWorks set-up: If a launcher is configured to start DataServer, DataServer will

start with the projects in the plist.dat file accessible by the usual OpenWorks rules - look first
in $OW_PMPATH and then in $OWHOME/conf if no plist.dat is found.
DataServer requires that the OpenWorks environment variable to be set so that it can access
SeisWorks/OpenWorks - see the Troubleshooting section for more information.

5. CAI configuration: Under CAI the user chooses a district (Oracle db) and when he selects
the 'GeoProbe DataServer', CAI prompts for a project, sets-up a configuration for that project
and starts DataServer. The project name is set in environment variable SEIS_PROJ and
DataServer uses this to show only that SeisWorks project.
Add entries to the CAI launcher configuration:
- in APPlaunch.sh in $CAIHOME/sh add function and reference:
#=======================================================
#================= Application Startup FUNCTIONS ============
#=======================================================
#======================== GeoProbe()======================
# GeoProbe
#=======================================================
#
GeoProbe() {
#open_xterm
/xxx/Dataserver/<OS>/bin/dataserver 2>$HOME/run/GeoProbe.err 1>&2 &

return 0
...
case ${APP} in
GeoProbe) GeoProbe
break
;;
...
- in ApplicationList.dat in $CAIHOME/dat directory

"Magic Earth" "Geoprobe DataServer" GeoProbe IRIX SEISMICALL /lm/i2000p

Troubleshooting
1. GeoProbe OW DataServer accesses SeisWorks/OpenWorks using the executable Dataserver/

<OS>/1.8.1/bin/gpdssw_<OW version>. These use shared libraries in directory Dataserver/
<OS>/1.8.1/owhome/lib_<OW version>. The shared library should be added to the library
paths before trying to run the executable:
% setenv LD_LIBRARY_PATH Dataserver/<OS>/1.8.1/owhome/lib_<OW

version>
% setenv LD_LIBRARYN32_PATH Dataserver/<OS>/1.8.1/owhome/lib_<OW

version>
The executable gpdssw can be run in line mode to check that the environment is correct,
e.g.:
% gpdssw_<OW version> project_list
should return a list of SeisWorks project names in plist.dat.
The command:
% gpdssw_<OW version> LIST devnor Seismic
should return a list of all the SeisWorks files in the devnor project.
The command:
% gpdssw_<OW_version> LIST devnor Faults(Interpreter=DEV)
should return a list of faults from OpenWorks.
2. Below are some examples of errors from inadequate configurations (or trying to run the
executables manually without the correct environment variables set):
Case 0:
Check that the OpenWorks command menu can be launched.

Check that SeisWorks can be started from the command menu.
Check that SeisWorks can display the project's seismic data.
Check that GeoProbe can be launched.
If there are any problems here, then there is something wrong with OpenWorks:
Oracle data base not running,

Oracle tns names listener not running,
NetD not running,
license server not running,
license manager not running,
no oracle account for user,

no permission to access the project,
or GeoProbe: no or outdated license file.
Case 1:
% gpdssw_2003.12
<pid>:gpdssw_2003.12: rld: Fatal Error: Cannot Successfully map
soname 'libclntsh.so.8.0' under any of the filenames:
<list of pathnames using directories in LD_LIBRARY_PATH>
% setenv LD_LIBRARY_PATH $(DATASERVER)/owhome/lib_2003.12
The script, dataserver, sets this before starting the DataServer GUI interface.
Case 2:
% gpdssw_<OW version> LIST devnor seismic

/vobs/ow/src/lib/owenv/lgc/lgc_getenv.c:228 213100302 lgc_getenv:
Unable to open config file
PID ERR CODE MESSAGE

==============================================================
19913 313100103 lgc_getdir: OW_PMPATH is undefined
Unable to log project on all drives
ERROR: Unable to log project devnor on all drives
project name='devnor'
OW_DDF='<not set>'
OW_PMPATH='<not set>'
OWHOME='/export/home/hayman'
DataServer gpdssw is trying to open a SeisWorks project and failing. In this example
OWHOME home was set incorrectly. However, for the LIST function, only the location of
the dir.dat file is required and it may be passed by correctly setting any of OW_DDF,
OW_PMPATH, or OWHOME.
Case 3:
% export OW_DDF=/backup/magicearth/owhome/conf/dir.dat
% gpdssw_<OW version> LIST devnor seismic

OWProjManageDir: OW_PMPATH is undefined, is OpenWorks installed ?

count 8

comp_5.cmp
istart=1&iend=21&jstart=1&jend=20&tstart=0&tend=2200&tinc=2
brick.bri
dev3201.3dv
dev0801.3dv
END OF LIST
DataServer gpdssw tries to open OpenWorks, fails, but continues and successfully opens
SeisWorks and lists the seismic content. Correctly setting OWHOME or OW_PMPATH
will fix the error messages. Of course, if there is no OpenWorks component for a project,
then other errors will be reported.
Case 4:
% gpdssw_<OW version> LIST devnor faults(Interpreter=DEV)

OWProjManageDir: OW_PMPATH is undefined, is OpenWorks installed ?

ERROR: Could not get OpenWorks project for seismic project.
DataServer gpdssw tries to open OpenWorks, fails. faults come from the OpenWorks
component of a project, so the list fails. This is remedied by correctly setting OWHOME or
OW_PMPATH.
Case 5:
% gpdssw_OW version> LIST devnor faults(Interpreter=DEV)

/vobs/ow/src/lib/owenv/get/getsid.c:154 317709199
getHostsOfSIDs: could not find tnsnames.ora
/vobs/ow/src/lib/owenv/get/getsid.c:290 317709199 getHostOfSID:
cannot get list of SIDs and hosts
/vobs/ow/src/lib/datman/prj/prjGetSysSID.cpp:138 317700699
prjGetSysSID: Not a valid SID for connection
ERROR: Could not connect to OpenWorks project SWDEVKIT
DataServer gpdssw successfully finds the OpenWorks project, but can not connect to the
Oracle database. This may mean that ORACLE_HOME is not set, or it may mean that
$ORACLE_HOME/network/admin/tnsnames.ora needs to be configured properly.
Case 6:

% gpdssw_<OW version> LIST devnor faults(Interpreter=DEV)

/vobs/ow/src/lib/datman/prj/prjGetSysSID.cpp:138 317700699
prjGetSysSID: Not a valid SID for connection
ERROR: Could not connect to OpenWorks project SWDEVKIT
Similar to above, but ORACLE_HOME was set to an Oracle home directory.

Unfortunately, it was not the one where Landmark OpenWorks database is registered.
Case 7:
% gpdssw_<OW version> LIST devnor Seismic

nliChkOut: lc_checkout(): Cannot find SERVER hostname in network
database (-14,7:145) Connection timed out
ier from owiCheckoutRuntime: 298500001
Could not get OpenWorks license. SeisWorks project
initialization failed
ERROR: Could not obtain an OpenWorks license
project name='devnor'
OW_DDF='<not set>'
OW_PMPATH='<not set>'
OWHOME='/backup/magicearth/owhome'
Landmark license problem: in this case the license server is not accessible.

Enhancements and New Functionality

The following section gives a brief overview of the new features and functionality of the GeoProbe
OW DataServer 1.8.1 release.
New Features
OpenWorks 2003.12 is now the supported OpenWorks platform.
Horizons from SeisWorks are now transferred by default to GeoProbe horizons, as opposed to
.gvw Surfaces. In addition, horizons picked in GeoProbe can now be transferred back to
SeisWorks.
SeisWorks horizons transferred into GeoProbe, will be saved in a binary format.
Well synthetics can now be transferred from OpenWorks into GeoProbe.
Fixed Problems
2D Data transfers are now working as expected, and are occurring in the correct positions
within the project. (#711579, #711196)

Known Problems
The following problems can be found on all workstations unless otherwise noted. Numbers in
parentheses denote the items id number in the bug tracking system.
When transferring volumes, if the first volume in the GeoProbe sub-directory list is incorrectly
oriented, the Grid Comparison dialog will have incorrect information. This dialog only looks
at the first volume in the list for this information; therefore, a workaround would be to remove
the bad volume from the directory. (#712942)
The GeoProbe OW DataServer will not work if ERR_LEVEL is set to 0. As a workaround, set
the ERR_LEVEL to 1. (#716097)

Support
Landmark/Asia Pacific Landmark/EAME Landmark/The Americas
11th Floor Menara Tan & Tan Hill Park South Building 1, Suite 200, 2101 CityWest
207 Jalan Tun Razak Springfield Drive Houston, TX 77042
50400 Kuala Lumpur Leatherhead, Surrey GU22 7NL P.O. Box 42806, Houston, TX 77242
Malaysia England U.S.A.
Tel: 011-60-3-2164-1121 Tel: 011-44 (0) 1372 868-600 Tel: 713-839-2000

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

All other trademarks, service marks and product or service names are the trademarks or names of their respective
owners.

Geoprobe Ow Dataserver 1.8.1: Release Notes

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Geoprobe Ow Dataserver 1.8.1: Release Notes

Încărcat de

Drepturi de autor:

Formate disponibile

Landmark GeoProbe OW DataServer

1.8.1 Release Notes Page 1 of 20 April 2006

GeoProbe OW DataServer is used to move data between Landmarks OpenWorks/SeisWorks and

1.8.1 Release Notes Page 2 of 20 April 2006

GeoProbe OW DataServer was tested on the following configurations:

IRIX version 6.5.25m operating system.

Solaris 8, update 7 (2/02) operating system (which includes Sun OS 5.8).

1.8.1 Release Notes Page 3 of 20 April 2006

1.8.1 Release Notes Page 4 of 20 April 2006

1.8.1 Release Notes Page 5 of 20 April 2006

Accessing the CDROM

Before you Begin

1.8.1 Release Notes Page 6 of 20 April 2006

Install GeoProbe OW DataServer from a Distribution CD

When GeoProbe OW DataServer is installed, it determines the operating system

% /bin/make -f /CDROM/cd_owds181Ir64/gpinst.mk dataserver

1.8.1 Release Notes Page 7 of 20 April 2006

Install GeoProbe OW DataServer from a Distribution CD

When GeoProbe OW DataServer is installed, it determines the operating system

2. Determine the location of the installation media (such as /cdrom/cdrom0/owds181Sn64 for

1.8.1 Release Notes Page 8 of 20 April 2006

Install GeoProbe OW DataServer from a Distribution CD

When GeoProbe OW DataServer is installed, it determines the operating system

2. Determine the location of the installation media (such as /mnt/cdrom/cd_owds181Lx32 for

% /usr/bin/make -f /mnt/cdrom/cd_owds181Lx32/gpinst.mk dataserver

% /usr/bin/make -f /mnt/cdrom/cd_owds181Lx64/gpinst.mk dataserver

1.8.1 Release Notes Page 9 of 20 April 2006

Verifying the Installation

3. In the launched xterm, type:

1.8.1 Release Notes Page 10 of 20 April 2006

Customizing the installation

4. Generic OpenWorks set-up: If a launcher is configured to start DataServer, DataServer will

1.8.1 Release Notes Page 11 of 20 April 2006

Add entries to the CAI launcher configuration:

- in APPlaunch.sh in $CAIHOME/sh add function and reference:

/xxx/Dataserver/<OS>/bin/dataserver 2>$HOME/run/GeoProbe.err 1>&2 &

- in ApplicationList.dat in $CAIHOME/dat directory

1.8.1 Release Notes Page 12 of 20 April 2006

1. GeoProbe OW DataServer accesses SeisWorks/OpenWorks using the executable Dataserver/

% setenv LD_LIBRARY_PATH Dataserver/<OS>/1.8.1/owhome/lib_<OW

% setenv LD_LIBRARYN32_PATH Dataserver/<OS>/1.8.1/owhome/lib_<OW

% gpdssw_<OW version> project_list

should return a list of SeisWorks project names in plist.dat.

% gpdssw_<OW version> LIST devnor Seismic

% gpdssw_<OW_version> LIST devnor Faults(Interpreter=DEV)

should return a list of faults from OpenWorks.

Check that the OpenWorks command menu can be launched.

Oracle data base not running,

1.8.1 Release Notes Page 13 of 20 April 2006

no permission to access the project,

or GeoProbe: no or outdated license file.

% setenv LD_LIBRARY_PATH $(DATASERVER)/owhome/lib_2003.12

% gpdssw_<OW version> LIST devnor seismic

PID ERR CODE MESSAGE

% gpdssw_<OW version> LIST devnor seismic

OWProjManageDir: OW_PMPATH is undefined, is OpenWorks installed ?

1.8.1 Release Notes Page 14 of 20 April 2006

% gpdssw_<OW version> LIST devnor faults(Interpreter=DEV)

OWProjManageDir: OW_PMPATH is undefined, is OpenWorks installed ?

% gpdssw_OW version> LIST devnor faults(Interpreter=DEV)

1.8.1 Release Notes Page 15 of 20 April 2006

% gpdssw_<OW version> LIST devnor faults(Interpreter=DEV)

Similar to above, but ORACLE_HOME was set to an Oracle home directory.