Rell Capitals

TIBCO OpenSpirit
Data Connector for

OpenWorks
Release Notes
Software Release 2.4.0
September 2017
ii
Important Information
SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR
BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD-ON
FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT
LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.
USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A
LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT,
OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT
WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS
DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR
CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE LICENSE FILE(S) OF
THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR
USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.
This document contains confidential information that is subject to U.S. and international copyright laws and treaties.
No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.
TIBCO, OpenSpirit, and TIBCO OpenSpirit Data Connector for OpenWorks are either registered trademarks or
trademarks of TIBCO Software Inc. in the United States and/or other countries.
All other product and company names and marks mentioned in this document are the property of their respective
owners and are mentioned for identification purposes only.
THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL
OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME
TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC
OPERATING SYSTEM PLATFORM.
THIS DOCUMENT IS PROVIDED AS IS WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, OR NON-INFRINGEMENT.
THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES
ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN
NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR
CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.
THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY OR INDIRECTLY,
BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO
ANY RELEASE NOTES AND "READ ME" FILES.
Copyright 2000-2017 TIBCO Software Inc. ALL RIGHTS RESERVED
TIBCO Software Inc. Confidential Information
iii
Table of Contents
Preface ........................................................................................................................................v
Typographical Conventions ................................................................................................... vi
Connecting with TIBCO Resources ...................................................................................... vii
How to Join TIBCOmmunity............................................................................................ vii
How to Access All TIBCO Documentation ...................................................................... vii
How to Contact TIBCO Support ...................................................................................... viii
Release Notes..............................................................................................................................1
New Features ..............................................................................................................................2
Release 2.4.0 ...........................................................................................................................2
Release 2.3.0 ...........................................................................................................................2
Release 2.2.0 ...........................................................................................................................2
Release 2.1.0 ...........................................................................................................................3
Release 2.0.0 ...........................................................................................................................3
Changes in Functionality .............................................................................................................4
Release 2.4.0 ...........................................................................................................................4
Release 2.3.0 ...........................................................................................................................4
Release 2.2.0 ...........................................................................................................................4
Release 2.1.0 ...........................................................................................................................4
Release 2.0.0 ...........................................................................................................................4
Deprecated and Removed Features ..............................................................................................5
Release 2.4.0 ...........................................................................................................................5
Release 2.3.0 ...........................................................................................................................5
Release 2.2.0 ...........................................................................................................................5
Release 2.1.0 ...........................................................................................................................5
Release 2.0.0 ...........................................................................................................................5
Migration and Compatibility .......................................................................................................6
Release 2.4.0 ...........................................................................................................................6
Migration ............................................................................................................................6
Compatibility ......................................................................................................................6
Certified Data Stores ...........................................................................................................6
Release 2.3.0 ...........................................................................................................................8
Migration ............................................................................................................................8
iv
Compatibility ......................................................................................................................8
Certified Data Stores ...........................................................................................................8
Release 2.2.0 .........................................................................................................................10
Migration ..........................................................................................................................10
Compatibility ....................................................................................................................10
Certified Data Stores .........................................................................................................10
Release 2.1.0 .........................................................................................................................11
Migration ..........................................................................................................................11
Compatibility ....................................................................................................................11
Release 2.0.0 .........................................................................................................................12
Closed Issues ............................................................................................................................13
Known Issues ............................................................................................................................22
v
Preface
TIBCO OpenSpirit Data Connectors provides the ability for applications to connect to diverse
data store through a consistent programing interface. Applications may connect and use the
OpenSpirit common data model and then be shielded from having to understand the differences
between different vendors data models and storage formats. Alternatively, for most data
connectors, an application may choose to connect and access data through the full underlying
native data model - still using a consistent programming interface.
The TIBCO OpenSpirit Data Connector for OpenWorks version 2.4.0 is designated with U.S.
Department of Commerce Export Control Classification Number EAR99.
vi
Typographical Conventions
The following typographical conventions are used in this manual.
Table 1 - General Typographical Conventions
Convention Use
TIBCO_HOME Many TIBCO products must be installed within the same home
directory. This directory is referenced in documentation as
ENV_HOME
TIBCO_HOME. The default value of TIBCO_HOME depends on
OSP_ HOME the operating system. For example, on Windows systems, the
default value is C:\tibco.
Other TIBCO products are installed into an installation
environment. Incompatible products and multiple instances of the
same product are installed into different installation environments.
An environment home directory is referenced in documentation as
ENV_HOME. The default value of ENV_HOME depends on the
operating system. For example, on Windows systems the default
value is C:\tibco.
TIBCO < ProductName > installs into a directory referenced in
documentation as OSP_HOME . The default value of OSP_HOME
depends on the operating system. For example on Windows
systems, the default value is
C:\Progam Files\OpenSpirit.
code font Code font identifies commands, code examples, filenames,

pathnames, and output displayed in a command window. For
example:
Use MyCommand to start the foo process.
bold code font Bold code font is used in the following ways:
In procedures, to indicate what a user types. For example:
Type admin.
In large code samples, to indicate the parts of the sample that
are of particular interest.
In command syntax, to indicate the default parameter for a
command. For example, if no parameter is specified,
MyCommand is enabled:
MyCommand [enable | disable]
vii
italic font Italic font is used in the following ways:

To indicate a document title. For example: See TIBCO
ActiveMatrix BusinessWorks Concepts .
To introduce new terms For example: A portal page may
contain several portlets. Portlets are mini-applications that run
in a portal.
To indicate a variable in a command or code syntax that you
must replace. For example: MyCommand PathName
Key combinations Key name separated by a plus sign indicate keys pressed
simultaneously. For example: Ctrl+C.
Key names separated by a comma and space indicate keys pressed
one after the other. For example: Esc, Ctrl+Q.
The note icon indicates information that is of special interest or

importance, for example, an additional action required only in
certain circumstances.
The tip icon indicates an idea that could be useful, for example, a
way to apply the information provided in the current section to
achieve a specific result.
The warning icon indicates the potential for a damaging situation,

for example, data loss or corruption if certain steps are taken or not
taken.
Connecting with TIBCO Resources
How to Join TIBCOmmunity

TIBCOmmunity is an online destination for TIBCO customers, partners, and resident experts, a
place to share and access the collective experience of the TIBCO community. TIBCOmmunity
offers forums, blogs, and access to a variety of resources. To register, go to
http://www.tibcommunity.com .
How to Access All TIBCO Documentation

After you join TIBCOmmunity , you can access the documentation for all supported product
versions here:
https://docs.tibco.com
viii
How to Contact TIBCO Support

For comments or problems with this manual or the software it addresses, please contact TIBCO
Support as follows.
For an overview of TIBCO Support, and information about getting started with TIBCO
Support, visit this site:
http://www.tibco.com/services/support
If you already have a valid maintenance or support contract, visit this site:
https://support.tibco.com
Entry to this site requires a user name and password. If you do not have a user name, you
can request one.
Release Notes | 1
Release Notes
Check the TIBCO Product Support web site at https://support.tibco.com for product
information that was not available at release time. Entry to this site requires a username
and password. If you do not have a username, you can request one. You must have a
valid maintenance or support contract to use this site.
Topics
New Features
Changes in Functionality
Deprecated and Removed Features
Migration and Compatibility
Closed Issues
Known Issues
OpenSpirit Data Connector for OpenWorks Release Notes

2 | New Features
New Features
This section lists features added since the last major release of this product.
Release 2.4.0
The following are new features in this release:
Added support for OpenWorks R5000.10.6 running on Linux RHEL Server
release 6 or 7 (64-bit only)
Added support for OpenWorks R5000.10.6 running on the Windows platform
(Windows-7/10 64-bit only)
Release 2.3.0
Added support for OpenWorks R5000.10.5 running on Linux RHEL Server
release 6 or 7 (64-bit only).
Release 2.2.0
Three new tables were added to the OpenWorks native data model:
district_dat, dir_dat and dir_dat_folder.
o The district_dat table returns the contents of the OW district.dat file.
o The dir_dat table returns the contents of each of the OW district's dir.dat
file.
o The dir_dat_folder table returns some basic information about each
seismic directory for the dir.dat directories.
The district_dat and dir_dat tables are read/only.
The dir_dat_folder table allows selects, inserts, and deletes (only if the directory
is empty).
This gives the client apps the ability to create seismic directories on specific
dir.dat folders if they don't like the default behavior of new seismic directories
being created on all possible (non-read/only) dir.dat folders.
Added the Seismic2D and Seismic3D tables to the native data model:
o Seismic2D is the file control record for 2d seismic datasets populated from
the external binary file; not from Oracle database.
o Seismic3D is the file control record for 3d seismic datasets populated from
the external binary file; not from Oracle database.

New Features | 3
The OpenSpirit common data model was modified recently and the following
attributes added:
o EpiInterpretation_FaultPolyline
PostStack2d
PostStack2dName
PostStack3d
PostStack3dName
o EpiInterpretation_HorizonGrid1dProperty
PostStack2d
PostStack2dName
o EpiInterpretation_HorizonGrid2dProperty
PostStack3d
PostStack3dName
Release 2.1.0
The following are new features in this release.
Added support for OpenWorks R5000.10 running on RHEL Server release 5 or 6
(64-bit only).
Release 2.0.0
This release was included in the TIBCO OpenSpirit Runtime 4.1.0 release. Please refer
to the Release Notes for that release for further details.

4 | Changes in Functionality
Changes in Functionality
This section lists changes in functionality since the last major release of this product.
Release 2.4.0
There are no changes in functionality for this release.
Release 2.3.0
Release 2.2.0
Release 2.1.0
Release 2.0.0

Deprecated and Removed Features | 5
Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may
be useful alternatives to the deprecated features. Any use of a deprecated feature should
be discontinued as it may be removed in a future release. You should avoid becoming
dependent on deprecated features and become familiar with the suggested alternative
features.
This section also lists features that are removed (if any).
Release 2.4.0
The following are deprecated or removed features in the release:
Dropped support for OpenWorks R5000.8
Release 2.3.0
There are no deprecated and/or removed features this release.
Release 2.2.0
Release 2.1.0
Release 2.0.0

6 | Migration and Compatibility
Migration and Compatibility

This section explains how to migrate from a previous release to this release and version
compatibility.
Release 2.4.0
Migration
TIBCO OpenSpirit Data Connector for OpenWorks 2.4.0 is a full-installation of the data
connector, decoupled from the TIBCO OpenSpirit Runtime release.
See the Installation Guide for further details.
Hotfix Runtime-v4.2.0-HF05 must be installed into the OpenSpirit Runtime 4.2.0

Master installation prior to installing the OpenSpirit Data Connector for OpenWorks
2.4.0.
You can download Hotfixes from the TIBCO Support Customer Portal
(https://support.tibco.com).
Log in using your username and password from the TIBCO Support Web page:
Select Download
Select Hotfixes
Select AvailableDownloads
Select OpenSpirit
Select Runtime
Select 4.2.0
Select HF05
Compatibility
The OpenSpirit Data Connector for OpenWorks requires the following products to be
previously installed and available:
TIBCO OpenSpirit Runtime 4.2.0
o Runtime-v4.2.0-HF05
OpenWorks R5000.10.x (see Certified Data Stores below)
Certified Data Stores

OpenWorks R5000.10.1 running on Linux RHEL Server release 5.4 or 6.7
(64-bit only)

Migration and Compatibility | 7

(64-bit only)
OpenWorks R5000.10.5 running on Linux RHEL Server Release 6.7 or 7.2
(64-bit only)
(64-bit only)
OpenWorks R5000.10.6 running on Windows 7 or Windows 10 (64-bit only)
Certified Operating Systems

See the TIBCO OpenSpirit Runtime 4.2.0 Release Notes.
Estimated Hardware Requirements

Estimated Disk Requirements

Binary installation 172 MB

Release 2.3.0
Migration
Hotfix Runtime-v4.2.0-HF03 must be installed into the OpenSpirit Runtime 4.2.0

Master installation prior to installing the OpenSpirit Data Connector for OpenWorks
2.3.0.
You can download Hotfixes from the TIBCO Support Customer Portal
(https://support.tibco.com).
Log in using your username and password from the TIBCO Support Web page:
Select Download
Select Hotfixes
Select AvailableDownloads
Select OpenSpirit
Select Runtime
Select 4.2.0
Select HF03
Compatibility
o Runtime-v4.2.0-HF03
OpenWorks R5000.x (see Certified Data Stores below)

OpenWorks R5000.8 running on Linux RHEL Server release 5 x86_64 using
Oracle 11.2.0.1
(64-bit only)
(64-bit only)





Release 2.2.0
Migration
This version is included with the TIBCO OpenSpirit Runtime 4.2.0 release.
Compatibility
OpenWorks R5000.x (see Certified Data Stores below)

Oracle 11.2.0.1
OpenWorks R5000.10 running on Linux RHEL Server release 5 or 6 (64-bit only)




Release 2.1.0
Migration
connector, decoupled from the TIBCO OpenSpirit Runtime 4.1.0 release. This version
can be installed into a TIBCO OpenSpirit Runtime v4.1.0 master installation using the
InstallConfig tool.
Compatibility
TIBCO OpenSpirit Runtime 4.1.0 HF04
The Runtime hotfix TIBCO OpenSpirit Runtime 4.1.0 HF04 must be
installed BEFORE installing the Data Connector for OpenWorks.
External Dependencies
OpenWorks R5000.x (see Certified Data Stores below).
Certified OpenWorks Data Stores

OpenWorks R5000.0.3.0 running on Linux RHEL Server release 5 x86_64 using
Oracle 11.2.0.1.
Oracle 11.2.0.1.
OpenWorks R5000.10 running on Linux RHEL Server release 5 or 6 (64-bit only)




Release 2.0.0

Closed Issues | 13
Closed Issues
There following are closed issues in this release series.
Closed in
CR # Summary
Release
2.4.0 OSPOW- The EpiInterpretation_HorizonFaultBoundarySet and
3 EpiInterprtetation_HorizonFaultBoundary tables now return both
EXCLUSIVE and INCLUSIVE fault polygons. Previously, only the
EXCLUSIVE fault polygons were returned.
2.4.0 OSPOW- Added support of "Mercator (Variant A)", EPSG code 9804 in this
26 release.
2.4.0 OSPOW- Modified OpenWorks DC and trim the 2d dataset to the 2d line if
43 the 2d dataset's trace maximum is 500,000 in the oracle
database (visible using the native Landmark Seismic Data
Manager).
2.4.0 OSPOW- The OpenWorks 5000.10.6 data connector now computes the 3d
60 seismic horizon EpiInterpretation_HorizonGrid2dProperty's
DataExtent much faster. The performance is still the same if the
client is running against earlier OpenWorks 5000.10 versions
(e.g. 10.1, 10.3). This is due to Landmark finally fixing a memory
leak in their SeisWorks 5000.10.6 SDK when reading 3d seismic
horizons.
2.4.0 OSPOW- No longer need to specify ORACLE_HOME when configuring
93 R5000.10.x data stores since the Oracle libraries are included
under $OWHOME
2.4.0 OSPOW- Make sure the Horizon data keys remain valid even if more
169 horizons are created with the same name but different
stratigraphic columns. For example, previously the Horizon data
key you get back from the INSERT might not the same as what
you get back from the SELECT which can cause table join
problems.
2.4.0 OSPOW- The LM_LICENSE_FILE is now included in the error message if
174 the OpenWorks DC failed to checkout an OpenWorks runtime
license.
2.4.0 OSPOW- OpenWorks DC was modified to do better data validation when
176 returning EpiSeismic_PostStack3d StorageOrder attribute in case
it is <null> in the OpenWorks database so it doesn't prevent the
volumes from being returned (e.g. DataSelector).
2.4.0 OSPOW- Corrected a problem querying for well zones. If the well zone
177 name contained a single quote ('), a duplicate row would be
returned.

14 | Closed Issues
Closed in
CR # Summary
Release
2.4.0 OSPOW- The 2d seismic directory will no longer be created as
178 "UNKNOWN" if a 2d line (EpiSeismic_LineGeometry2d) is
inserted and SeismicProject is supplied but it is an empty string.
The 2d seismic directory will now default to the 2d survey name
just like if SeismicProject is not specified on the insert statement.
2.4.0 OSPOW- Now supporting DC-OpenWorks running on Windows platform
180 with 5000.10.6 version. The windows host to run the DC must
have OpenWorks installed locally for it to operate correctly.
2.4.0 OSPOW- When the geographic system is used for the project and any data
181 type, OpenSpirit will now honor the coordinate system name
instead of using the datum name as the coordinate system name.
2.4.0 OSPOW- Corrected a problem when inserting or updating a WellBore with
191 a CompletionDate or SpudDate Timestamp value with a
millisecond component.
Originally released with OpenWorks_DC_v230_HF02
2.4.0 OSPOW- Fixed a memory leak that occurred when copying all wells, picks,
193 zones and zone parameters. Prior to this fix you would get an
OutOfMemory error if a large enough data set was being copied.
2.4.0 OSPOW- We have updated the datum mappings based upon OpenWorks
194 R5000.10.6.
2.4.0 OSPOW- Improved performance retrieving the wellbores for a wellbore list.
195 Originally, a wellbore list with 8100 wellbores took 45 seconds to
display in the data selector. Now it takes about 8 seconds.
2.4.0 OSPOW- Improved error handling and reported when there are problems
196 reading the OW_CONF_DIR/district.dat file.
2.4.0 OSPOW- Corrected a problem retrieving the WellBore BottomLocation
198 when the WellBore Elevation was null.
2.4.0 OSPOW- The OpenWorks data connector has been enhanced to perform
208 more validation on the 3d survey's corner points before the
survey is created.
2.4.0 OSPOW- Better error detection in the OpenWorks run script if the
211 $OW_CONF_DIR is not accessible.
2.4.0 OSPOW- The OpenWorks native model table gdiGeodeticDatum_t now
214 returns all datums in the database instead of just the datums for
the active project.
2.4.0 OSPOW- Modified to not compute a two point WellBore Path column value
228 if the TotalDepth and Elevation are equal, preventing a Path
value with only one unique point.

Closed Issues | 15
Closed in
CR # Summary
Release
2.4.0 OSPOW- The gdiWellLocationRemark_t now has a relationship to
232 gdiWellLocation_t so it is now possible to view information from
gdiWellLocation_t when using the DataSelector and the native
OpenWorks data model and viewing the
gdiWellLocationRemark_t table. This is also useful if running
Scan jobs using the OpenWorks native model.
2.4.0 OSPOW- The OpenWorks data connector now does a better job of
233 preserving surface attributes (e.g. surface age, data source,
remarks, surface type) when copying stratigraphic units from one
OpenWorks project to another. Stratigraphic units are associated
to a top and bottom surface.
2.4.0 OSPOW- Fixed the HorizonFaultBoundarySet DatumElevation processing
234 so if copying these from a target OpenWorks project to a source
OpenWorks project the datum will be <null> in the target if it was
<null> in the source project. Previously, it would have been
copied and set to zero in the target project.
2.4.0 OSPOW- The gdiWellLocationUwiAlt_t now has a relationship to
235 gdiWellLocation_t so it is now possible to view information from
gdiWellLocation_t when using the DataSelector and the native
OpenWorks data model and viewing the gdiWellLocationUwiAlt_t
table. This is also useful if running Scan jobs using the
OpenWorks native model.
2.4.0 OSPOW- The OpenWorks data connector has been modified so if the client
241 application (e.g. CopyManager) is writing data using
PostStack3dAccessor's setCube(), then the volume's storage
order is taken into account. For example, if the volume is INLINE
optimized the data is written using inline planes; if the volume is
XLINE optimized the data is written using xline planes.
2.4.0 OSPOW- OpenWorks often assumes that the NAD83 is the same as
244 WGS84. It gives the transform from source datum to NAD83
instead of WGS84. When the option to use EPSG code is
turned on in the data source configuration, we have added more
logic to add the extra transform to form a compound fallback
transform to make sure that the required transform with WGS84
as target exists.
2.3.0 OSPOW- Improved performance querying for EpiWell_WellPick when using
7 a PickType='value' constraint.
2.3.0 OSPOW- The OpenWorks R5000 data connector now supports inserting
8 PropertyAlias for 3d seismic horizon properties
(EpiInterpretation_HorizonGrid2dProperty).
2.3.0 OSPOW- The OpenWorks data connector now returns synthetic seismic
12 logs as EpiWell_WellLogTraces.

16 | Closed Issues
Closed in
CR # Summary
Release
2.3.0 OSPOW- Now, 2d datasets (EpiSeismic_PostStack2d) and 2d horizons
20 (EpiInterpretation_HorizonGrid1d,
EpiInterpretation_HorizonGrid1dProperty) are now clipped based
on their associated 2d line's trimmed trace range to honor IP
clipping parameters and also to mimic the behavior of native
Landmark applications (e.g. SeisWorks, DecisionSpace). There is
no change of behavior if the 2d line's overall and trimmed trace
ranges are the same.
2.3.0 OSPOW- The "coordinate frame rotation" transform method is now
23 supported by the TIBCO OpenSpirit OpenWorks data connector.
Please note that this transform method only works with the
OpenWorks R5000.10.3 version with the 10.3.02.01 patch
installed.
2.3.0 OSPOW- Support for new functionality has been added in OpenWorks Data
24 Connector v2.3.0. Users have the option to use the EPSG codes
provided by the OpenWorks native coordinate reference systems.
A checkbox has been added to the OpenWorks data source
configuration panel. If the "Use EPSG codes" checkbox is
checked, OpenSpirit will take advantage of the EPSG codes for
projection system, geographic system, and the datum transform.
The coordinate reference system will be created based on valid
EPSG codes. In the event that an EPSG code is not valid, the
existing mechanism will be used create the coordinate reference
system from the parameters.
2.3.0 OSPOW- The OpenWorks data connector does a better job of setting the
39 file permissions of new external files (2d/3d seismic datasets, 3d
horizons) for the situations when the seismic directories already
exist and do not need to be created. The file permissions will be
based on the permissions of the parent seismic directories. For
example, if one of the writable parent seismic directories is world
writable then the new files will also be world writable. If the
seismic directories are only group writable then the new files will
only be group writable. If neither world or group are writable, then
the new files will be private.
2.3.0 OSPOW- The OpenWorks data connector now supports insert, update,
41 delete operations for the EpiInterpretation HorizonPointSet,
HorizonPointSetProperty, FaultPointSet, FaultPointSetProperty
tables.
Copy rules were modified to support copying horizon/fault point
sets from OpenWorks or Studio source projects to an OpenWorks
target project.
2.3.0 OSPOW- Fixed problems with the depth-based HorizonFaultBoundary
47 Points z values having the wrong sign if retrieved more than
once.

Closed Issues | 17
Closed in
CR # Summary
Release
2.3.0 OSPOW- The OpenWorks data connector no longer gets a
55 NullPointerException for incomplete 3d surveys (e.g. if the
gdiSeisGeomSet3DSurvey record exists but not the
gdiBinsetGrid3DGrid record does not).
2.3.0 OSPOW- Added spatial data for the following native entities:
61 gdiWellLocation_t
gdiWell_t
gdiWellEntire_t
geiWellShort_t
gdiBinsetGrid3DGrid_t
gdiSeis3DSurvey_t
gdiSeis2DLine_t
gdiSeisGeomSet2DLine_t
gdiFaultPolygonSet
gdiFaultSegment
gdiFaultTrimesh
gdiFgrid
gdiGrid
GdiRgrid
gdiMappingPolySet
gdiPointSet
gdiPosLog
2.3.0 OSPOW- The OpenWorks data connector now honors the
63 EpiSeismic_PostStack3d StorageOrder if supplied on the insert
statement. For example, if the client application is creating a
TRACE or BRICK (StorageOrganization) volume and they want it
to be crossline optimized then they would set StorageOrder to
XLINE_INLINE_Z. The OpenWorks volume is created and the
'opt_direction' flag in the oracle database is now set to 'xline'.
Previously, the 'opt_direction' defaulted to 'inline'. This is before
any seismic traces are written. However, the SeisWorks SDK will
automatically set the 'opt_direction' based on how the seismic
traces are physically written to the file. If the volume is created
with "xline" but the seismic traces are written using inline planes
then the SeisWorks SDK will automatically change 'opt_direction'
from 'xline' to 'inline' and vice versa.
2.3.0 OSPOW- Corrected a problem copying a Well from Studio to OpenWorks if
64 the Studio UWI is null.

18 | Closed Issues
Closed in
CR # Summary
Release
2.3.0 OSPOW- The OpenWorks data connector no longer returns horizon/fault
69 point sets with NaN for the XY values even though it is possible to
load data into the OpenWorks database with NaN XY values.
OpenSpirit returns the spatial data using a MultiPoint. This
affects the EpiInterpretation_HorizonPointSet's and
EpiInterpretation_FaultPointSet's Points attribute. If the point set
has bad XY points filtered out then the associated property
values are also filtered out to keep the Points attribute and the
point set property values in sync.
2.3.0 OSPOW- The EpiInterpretation_HorizonGrid2d's DatumElevation is ignored
74 when inserting 3d seismic horizons because the datum is
determined by the associated 3d survey. Now when you retrieve
the DatumElevation from a newly inserted HorizonGrid2d
(seismic) it will be the 3d survey's datum instead of whatever was
specified on the insert statement.
2.3.0 OSPOW- Enhanced the OW native model for gdiWellLocation_t; added the
77 following GEOMETRY (Point) attributes: orig_x_lon_y_lat,
surface_xy_coordinate, surface_latitude_longitude.
2.3.0 OSPOW- CopyManager now has the capability to copy WellZones into
83 OpenWorks.
2.3.0 OSPOW- Corrected an exception that occurred in the OpenWorks data
85 connector when querying for well zone parameters for all selected
well zones in the data selector.
2.3.0 OSPOW- Corrected a problem querying WellZone with a StratColumnName
86 constraint. Corrected a problem querying WellZoneParameter
with a WellZone constraint. Corrected a problem retrieving
TopMD and BaseMD values from the WellZone table when the
TopPick and BasePick columns were not requested.
2.3.0 OSPOW- The OpenWorks data connector now does a better job handling
90 the condition when a client is accessing multiple OW projects in
different OW districts at the same time. Previously, it was
possible for the OW data connector to crash.
2.3.0 OSPOW- Added support for OpenWorks R5000.10.3.x which can run on
94 either RH6 or RH7.
2.3.0 OSPOW- The OpenWorks native data model has be regenerated against
95 R5000.10.3.0 so it now has all the most recently added entities
and attributes.
2.3.0 OSPOW- The OW native data model has been changed and all DATE and
100 TIMESTAMP fields are now returned as TIMESTAMP objects
instead of strings.
2.3.0 OSPOW- Corrected a NullPointerException that occurred when querying for
102 EpiWell_WellPicks scoped to HorizonHeader.

Closed Issues | 19
Closed in
CR # Summary
Release
2.3.0 OSPOW- Corrected a problem when updating EpiInterpretation_Horizon
108 where the input DataSource value was not validated against the
list of valid interpreters the client has access to.
2.3.0 OSPOW- A WellZone tied to the UNKNOWN strat column in OpenWorks
109 now returns null for the StratColumn data key.
2.3.0 OSPOW- Improved performance retrieving the WellZone column from the
113 WellZoneParameter table.
2.3.0 OSPOW- Have added spatial data types, timestamp, and color attributes to
101 the native OW data model.
2.3.0 OSPOW- The OpenWorks project's default storage CRS identifier will be
117 used if any 2d lines have an invalid original CRS identifier (e.g.
null which means not populated). This was already being
performed for the EpiSeismic_LineGeometry2d and
EpiSeismic_PostStack2d tables but it was not being performed
for the PostStack2d accessor when the getLocation() method was
called.
2.3.0 OSPOW- When inserting into the OpenWorks gdiWellEntire_t native table,
121 the well_location_id is now required.
2.3.0 OSPOW- Corrected a NullPointerException that occurred when querying for
130 WellZones with a PrimaryKey$ constraint with 0 keys in the data
key array.
2.3.0 OSPOW- The OpenWorks EpiInterpretation_Interval table is now read/only
136
2.3.0 OSPOW- OpenWorks documentation suggests mapping "Hotine Oblique
140 Mercator - 1 point" to EPSG code 9815. However, the
OpenWorks database only provides 6 parameters for this
projection conversion method. According to Landmark support
case #2294116, their recommendation is to duplicate the
parameter "Azimuth Initial Line", which OpenSpirit has now done.
2.3.0 OSPOW- Added a new spatial data LineString attribute to the
144 gdiFaultSegment_t table called 'values$xyz' representing the XYZ
values of the fault segment.
2.3.0 OSPOW- CopyManager workflows that copy 2D Horizons, 3D Horizons, or
157 Grids from one OpenWorks project to another now use the
associated Feature StratColumn as a matching key when trying
to find the object in the target project.
2.3.0 OSPOW- Improved performance retrieving the TraceIndexXXX columns (eg
168 TraceIndexMD, TraceIndexTWT) by only computing the array
values if the column is requested.
2.2.0 33876 Added support for Stereographic projection conversion methods
based on a valid EPSG code.

20 | Closed Issues
Closed in
CR # Summary
Release
2.2.0 34491 Corrected a problem reading the x and y offsets from an
OpenWorks project whose project coordinate system is
geographic.
2.2.0 34505 Corrected a problem in the Data Source Config panel when
configuring an OpenWorks R5000.10 data source.
2.2.0 31811 The OpenWorks data connector can now create 2d lines and 3d
surveys if the OW project's storage CRS is lat/long.
2.2.0 33876 Added support for Stereographic projection conversion methods
based on a valid EPSG code.
2.2.0 34616 When inserting an OW non-seismic grid it is no longer identified
as a PrimaryZ property just because the DataUnit is time or depth
based. The OW non-seismic primary Z grid's PropertyType is
now consistent with the other vendor stores (e.g. either "Time" or
"Depth") instead of just returning whatever is in the gdiGrid_t's
attribute field. The PropertyAlias was previously implemented for
seismic horizons but the attribute was not mapped in the data
source capabilities. Now it shows up as a mapped attribute that is
insertable and updateable.
2.2.0 34715 The OpenWorks data connector now returns 4 coordinates,
instead of 2, for the EpiProject_Project's Extent spatial attribute to
conform to the expected behavior documented in the OpenSpirit
table model documentation.
2.2.0 35204 Fixed problems when the 2d/3d seismic datasets have "null"
values for the actual Z start and actual number of samples per
trace in the oracle database. If this occurs, the values are
retrieved from the external binary data files.
2.2.0 35259 The OpenWorks data connector server log contains more
diagnostics if the external SeisWorks binary data files (e.g. 2d/3d
seismic data sets and 3d seismic horizons) cannot be accessed.
2.2.0 35261 The OpenWorks data connector is now able to display and
update the 2d/3d seismic dataset associations for fault polylines
and 2d/3d seismic horizons.
2.2.0 35412 The OpenWorks data connector now returns the correct surface
age if the surface is associated to multiple strat columns. These
are viewable using the OSP DataSelector "Horizon Header" or
the "Strat Unit" tabs.
2.2.0 34941 The OpenWorks data connector now can update the
EpiInterpretation_Horizon Source, Classification, and
GeologicalAge attributes.
2.2.0 35157 Corrected a problem building an OpenSpirit coordinate system
object for the Beijing 1954 system. Previously, a local coordinate
system was returned.

Closed Issues | 21
Closed in
CR # Summary
Release
2.2.0 35158 Three new tables were added to the OpenWorks native data
model: district_dat, dir_dat, dir_dat_folder (see "New Features"
section).
2.2.0 35161 The OpenWorks data connector was modified so the 3d seismic
horizon binary files are now deleted from disk (e.g. *.hts) if
performing a 3d seismic horizon DELETE operation using
OpenSpirit (DELETE FROM
EpiInterpretation_HorizonGrid2dProperty WHERE
<whereClause>)
2.2.0 35524 Copy Manager workflows can now preserve the OpenWorks
2d/3d seismic datasets that are associated to fault polylines and
2d/3d seismic horizons if they are populated in the source project.
2.2.0 35534 Fixed a segmentation fault that could occur when running against
R5000.10 and updating all three well path arrays.

22 | Known Issues
Known Issues
The following are known issues at this time.
Issue # Summary/Workaround
OSPOW-200 When running OpenWorks R5000 on Windows and displaying data with
international characters in the native OpenWorks application as well in
OpenSpirit, special characters may be incorrectly displayed in both
applications.
WORKAROUND:
In order to read and display special characters from Oracle properly
make sure the registry key:
"HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_OraClient12H
ome1\NLS_LANG"
is set to the value: "AMERICAN_AMERICA.US7ASCII".
Please note that OpenWorks R5000 does not officially support
international characters, but OpenSpirit will correctly read and display
them.

Rell Capitals

Încărcat de

Informații document

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

Rell Capitals

Încărcat de

Drepturi de autor:

Formate disponibile

TIBCO OpenSpirit

Data Connector for

code font Code font identifies commands, code examples, filenames,

italic font Italic font is used in the following ways:

The note icon indicates information that is of special interest or

The warning icon indicates the potential for a damaging situation,

Connecting with TIBCO Resources

How to Join TIBCOmmunity

How to Access All TIBCO Documentation

How to Contact TIBCO Support

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

Deprecated and Removed Features

OpenSpirit Data Connector for OpenWorks Release Notes

Migration and Compatibility

Hotfix Runtime-v4.2.0-HF05 must be installed into the OpenSpirit Runtime 4.2.0

Certified Data Stores

OpenSpirit Data Connector for OpenWorks Release Notes

OpenWorks R5000.10.3 running on Linux RHEL Server release 5.4 or 6.7

Certified Operating Systems

Estimated Hardware Requirements

Estimated Disk Requirements

OpenSpirit Data Connector for OpenWorks Release Notes

Hotfix Runtime-v4.2.0-HF03 must be installed into the OpenSpirit Runtime 4.2.0

Certified Data Stores

Certified Operating Systems

OpenSpirit Data Connector for OpenWorks Release Notes

Estimated Hardware Requirements

Estimated Disk Requirements

OpenSpirit Data Connector for OpenWorks Release Notes

Certified Data Stores

Certified Operating Systems

Estimated Hardware Requirements

Estimated Disk Requirements

OpenSpirit Data Connector for OpenWorks Release Notes

Certified OpenWorks Data Stores

Certified Operating Systems

Estimated Hardware Requirements

Estimated Disk Requirements

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

OpenSpirit Data Connector for OpenWorks Release Notes

S-ar putea să vă placă și