openworks software version...

5000.8.1.0 Release Notes Page 1 of 34 February 2012

OpenWorks® SoftwareVersion 5000.8.1.0

Release Notes

Contents

What’s In This Release ................................................................................................ 2

Welcome to the OpenWorks® Software ..................................................................... 3

System Requirements ................................................................................................. 5

Installation Instructions .............................................................................................. 5

Third Party Applications ............................................................................................. 6

International Trade Compliance ................................................................................. 7

Enhancements and New Functionality ...................................................................... 9

Fixed Issues ............................................................................................................... 12

Known Issues ............................................................................................................. 17

Compatibility with Discovery™ On OpenWorks® Software .................................. 27

Contacting Landmark Customer Support ............................................................... 31

Copyright and Trademark Information ..................................................................... 33

OpenWorks® Software


What’s In This ReleaseThe 5000.8.1.0 release of the OpenWorks® software provides new features and defect fixes. The highlights of this release are:

• The Oracle 11g database software (64-bit) is embedded in the installation program for the OpenWorks® database instance.

• The OpenWorks® database instance supports incremental backups and archive logs.

• New — Database Administration tool is a graphical interface to enable the Oracle user (database administrator) to administer the OpenWorks® database instance. The tool can run SQL scripts, supports database backup and recovery via Oracle’s Recovery Manager (RMAN), and supports repair functions via Oracle’s Data Recovery Advisor.

• Names of coordinate reference systems (CRSs) are sometimes changed after restoring projects or after transferring data between projects.

To go directly to more information on the new features and changes, other enhancements, fixed issues, and known issues for the OpenWorks® software, click on the links below:

Enhancements and New Functionality

Fixed Issues

Known Issues



Go To “What’s in this Release?”

Welcome to the OpenWorks® SoftwareThe OpenWorks® software version 5000.8.1.0 is a full release of the OpenWorks® software and its Import/Export utilities (the GeoDataLoad™ software). Newer utilities are documented in the online help, and older utilities are documented in the manuals (in PDF format). The online help has links to the manuals.

NOTICE: Changes to Oracle Licensing — Oracle Embedded Software License (ESL)

Due to new licensing requirements for the software of the Oracle database, the OpenWorks® software is moving to an embedded-use Oracle license (Embedded Software License, or ESL). Version 5000.8.1.0 of the OpenWorks® software is the first release to provide this functionality.

The Oracle ESL applies to any customer who licenses OpenWorks with Oracle (the OpenWorks software with the Oracle database software embedded), has an Oracle 11g installation, and does not have a separate contract with Oracle. Landmark will not provide an ESL solution with Oracle 10g.

As part of Oracle ESL compliance, customers who fit the above profile are no longer licensed to use Oracle tools directly, including SQL*Plus. Version 5000.8.1.0 of the OpenWorks software provides the following new tools to enable Oracle ESL compliance:

• The Oracle 11g database software is embedded in the installation program for the OpenWorks database instance. Installation no longer requires separate Oracle media.

• The OpenWorks database installer supports configuring your database to run in either ArchiveLog mode or NoArchiveLog mode. Archivelog mode supports hot backups, incremental backups, and point in time recovery. Nightly backups can be scheduled and users can configure backup retention policies.

• Database Query Tool provides a graphical user interface to perform simple database queries and to run pre-defined SQL scripts in order to troubleshoot data in a project.

• The new Database Administration tool provides a graphical user interface to run SQL scripts for troubleshooting purposes. With this tool, the Oracle user (database administrator) can:

• Run Landmark-supplied SQL scripts in order to perform system level functions.

• Configure and execute incremental backups and archive logs using Oracle Recovery Manager (RMAN).

• Repair a damaged database instance.




• Recover a full database instance.

• Clone a database instance.

• Upgrade an OpenWorks database instance from Oracle 10.2.0.x to Oracle 11.2.0.2.

NOTICE: Future Support for Operating Systems

Landmark regularly reviews our industry-leading software suite to verify that our product lines meet marketplace demands for implementation on the most appropriate and widely accepted technologies. Our goal is to focus our efforts where they will bring you the most value.

After careful consideration, and beginning with version 5000.10.x.x of the OpenWorks® software, Landmark will no longer release the OpenWorks® software on the following operating systems:

• Microsoft Windows® XP 32-bit, 64-bit

• Microsoft Windows® 2003 Server 32-bit, 64-bit

• Red Hat Enterprise Linux® 4.x 32-bit, 64-bit

• Red Hat Enterprise Linux® 5.x 32-bit only

The last versions of the OpenWorks® software tested on the above operating systems will be with the 5000.8.x.x product cycle.

We based this decision on limited customer demand for the OpenWorks® software on these operating systems as well as market trends indicating that most applications for the oil and gas industry will standardize on fewer operating systems. The costs to support multiple operating systems and platforms are large and reduce the velocity with which we can serve our customers by producing new releases and delivering functionality.

Going forward, the OpenWorks® software is committed to Red Hat Enterprise Linux® and Microsoft Windows® as the operating systems for our products. These operating systems not only offer excellent functionality, but also deliver major gains in price-performance.

Please be advised that this statement is formal notification as set forth in the terms and conditions of Landmark’s standard maintenance and support contract. We regret any inconvenience that this decision might cause, and we are prepared to work with you to minimize any potential disruptions within your operations.

Please contact your Account Executive with any concerns or if you desire any further information.




System RequirementsComplete system requirements for each platform are contained in the OpenWorks® Software Installation Procedures.

Installation Instructions

Refer to the OpenWorks® Software Installation Procedures for detailed installation information. The document is available in the Landmark Software Manager (LSM) from the Install Info button ( ) for the installation program.

The Installation Procedures manual has information about:

• Creating an installation of the OpenWorks® software and its database instance.

• Upgrading a previous version of the OpenWorks® software, possibly upgrading the Oracle software (depending on whether a new version of the Oracle software is supported by the new version of the OpenWorks software), and possibly upgrading (or extending) existing projects.

If the OpenWorks® Data Model has changed in the new version of the OpenWorks® software, the projects in an existing database instance must be upgraded (or extended) before the projects can be managed or used in the new version of the OpenWorks software, or before they can be used by other applications that support the new version of the OpenWorks software. The information about upgrading projects is in the “Upgrade the OpenWorks® Software” chapter of the Installation Procedures manual.




Third Party ApplicationsHalliburton 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:

$OWHOME/docs/third_party.pdf Linux

%OWHOME%\docs\third_party.pdf Windows




International Trade ComplianceThis application is manufactured or designed using U.S. origin technology and is therefore subject to the export control laws of the United States. Any use or further disposition of such items is subject to U.S. law. Exports from the United States and any re-export thereafter may require a formal export license authorization from the government. If there are doubts about the requirements of the applicable law, it is recommended that the buyer obtain qualified legal advice. These items cannot be used in the design, production, use, or storage of chemical, biological, or nuclear weapons, or missiles of any kind.

The ECCN’s provided in Release Notes represent Halliburton’s opinion of the correct classification for the product today (based on the original software and/or original hardware). Classifications are subject to change. If you have any questions or need assistance, please contact us at:

[email protected]

Under the U.S. Export Administration Regulations (EAR), the U.S. Government assigns your organization or client, as exporter/importer of record, responsibility for determining the correct authorization for the item at the time of export/import. Restrictions may apply to shipments based on the products, the customer, or the country of destination, and an export license may be required by the Department of Commerce prior to shipment. The U.S. Bureau of Industry and Security provides a web site to assist you with determining the need for a license and with information regarding where to obtain help. The URL is:

http://www.bis.doc.gov

Definitions

CCATS (Commodity Classification Automated Tracking System) — the tracking number assigned by the U.S. Bureau of Industry and Security (BIS) to products formally reviewed and classified by the government. The CCATS provides information concerning export/re-export authorizations, available exceptions, and conditions.

ECCN (Export Control Classification Number) — The ECCN is an alpha-numeric code, e.g., 3A001, that describes a particular item or type of item, and shows the controls placed on that item. The CCL (Commerce Control List) is divided into ten broad categories, and each category is

mailto:[email protected]://www.bis.doc.gov




further subdivided into five product groups. The CCL is available on the EAR web site (http://www.access.gpo.gov/bis/ear/ear_data.html#ccl).

The ECCN Number, License Type, and the CCATS Numbers for this product are included in the table below.

Product/Component/Version 5000

ECCN Number License CCATS Number

OpenWorks® Software 5D002C.1 ENC G054746

GeoDataLoad™ Software 5D002 ENC G049393

http://www.access.gpo.gov/bis/ear/ear_data.html#ccl




Enhancements and New FunctionalityThis section describes the changes in the OpenWorks® software.


• The Oracle 11g database software (64-bit) is embedded in the installation program for the OpenWorks® database instance.

For installations of the OpenWorks® database server using Oracle 10g, 32-bit or 64-bit, or using Oracle 11g, 32-bit, you need to do the following:

• Acquire the Oracle software separately.

• To install the OpenWorks® database instance, use the installation program for version 5000.8.0.0.

• To install the OpenWorks® software, use the installation program for version 5000.8.1.0.

• The OpenWorks® database instance supports incremental backups and archive logs.

These backups and logs allow you to perform a point-in-time recovery of a database instance.

• New — Database Administration tool: A graphical interface to enable the Oracle user (database administrator) to administer the OpenWorks® database instance. The tool can do the following:

• Runs SQL Scripts: Runs predefined scripts to perform common database administration tasks, such as start the database, stop the database, delete a database instance, and check the status of the listener.

• Supports Oracle’s Recovery Manager (RMAN): Hides the details of using RMAN. When an OpenWorks® database instance is created, you can set the schedule for incremental backups and for the backup of archive logs, and you can determine how long the backups and logs are retained.

• Repairs a Damaged Database Instance: Uses Oracle’s Data Recovery Advisor.

• Recovery of a Full Database Instance: Uses Oracle backup files to recover the database instance to the same or another machine. The recovered database instance can be from its latest state or from a point-in-time.




• Clone a Database Instance: Clones a database instance to another instance on the same machine in order to duplicate the original database instance. The cloned database can be from its latest state or from a point-in-time.

• Upgrades an OpenWorks Database Instance.

• Names of coordinate reference systems (CRSs) for the original data are sometimes changed when restoring projects or when transferring data between projects. This behavior has existed in previous versions of the OpenWorks software. The behavior is the following:

• The CRS in the backup file or source project is compared to the CRSs in the database instance. The names and parameters of the CRSs are compared. A new CRS is created, if

— the name of the backup or source CRS does not exist in the database instance. The name of the new CRS in the database instance is the same as the CRS in the backup file or source project.

— the same CRS name exists in the database instance, but the parameters of the CRSs are not the same. Since the name of the CRS must be unique in the database instance, the new CRS in the database instance is given a name similar to the following.

When restored:

OriginalCRSName_n

where OriginalCRSName is the name of the CRS in the backup, and where n is an integer.

When transferred with Project Data Transfer:

OriginalCRSName_pdt

• Defects fixed.

• Changes were made in the following components of the OpenWorks® software:

Change Color Scheme General Units Converter Project Administration

Change Oracle User Password

Interpretation Data Manager

Project Status

Checkshot Data Manager (Linux Only)

Interpretation ID Manager Project Upgrade




GeodataLoad™ Software

• Updated SEG Y Data Loader.

• Defects fixed.

• Changes were made in the following components of the GeoDataLoad™ software:

Curve Dictionary Launcher Script for OpenWorks® Java Applications

Seismic Data Manager

Data Domain Manager Lease List Manager Seismic List Manager

Database Administration Tool — New

Lithologic Symbol Editor SeisWorks® Development Kit (for seismic data access)

Database Query Tool Map Projection Editor Special Units Editor

DecisionSpace Infrastructure

Mapping Overlay Manager (Linux Only)

Surface/Fault Data Manager

Deviation Data Manager (Linux Only)

Measurement System Manager

Well Curve Viewer

Error Logger Modify Database Users Well Data Manager

Extend2Dline Utility OpenWorks® Development Kit™

Well List Manager

Field List Manager OWSW (OpenWorks® and SeisWorks®) Data Access

Well Symbol Editor

ASCII Loader Project Data Transfer

Curve Loader Raster Log Import

Data Export Wizard SEG Y Data Loader

Data Import Wizard Stimulation Data Loader

GGX ASCII 4 Export Well Data Export




Fixed IssuesThis section lists the most important issues and enhancements in the OpenWorks® and the GeoDataLoad™ software.


Configuration, Installation, and Generally

Defect ID Summary

• 875471 Installation: Bash mode: Syntax error setting up environment variable for .lgcprofile.

• 877992 Installation: ASCII Loader > serious performance degradation when loading large files.

• 853030 Installation: OpenWorks® applications on Windows, LAM environment variable FLEXLM_NO_CKOUT_INSTALL_LIC.

Data Management

Defect ID Summary

• 874445 Interpretation Data Manager: Create pick name in vc pick surf name.

• 874365 Mapping Overlay Manager: AutoCad 10 and 12 DXF files fail to convert to ZGF > Error reading file > Error creating layer.

• 856877 Seismic Data Manager: Pack and Go duplicating data.

• 872718 Seismic Data Manager: Create new seismic volume version with interpreter access.

• 875008 Seismic Data Manager: Unable to importing 3D seismic and horizons using Pack and Go.

• 877546 Seismic Data Manager: Constraint violation XAK2SEISMIC_DATA_SET when using Pack and Go between two projects of the same name.




• 879992 Seismic Data Manager: Mismatch between 2D navigation data in OpenWorks® database and 2D data exported via Export Wizard.

• 829947 Well Data Manager: Well Data Manager issue with Look for option.

• 874175 Well Data Manager: Directional Survey. Adding tie point information and saving reverts X/Y offset values to 0.00 (zero).

• 874697 Well Data Manager: With well location, saving a Platform Code that does not match the Platform Slot No --- Error: 27760082 Cannot create a new PlatformSlot through WellLocation.

• 879945 Well Data Manager: Log Image Registered Log Section --- TIF File Path is incorrect when using SHARED_LOG_IMAGES.

• 832458 The Hide all columns and Freeze all columns icons do not exist in Column Management dialog.

Data Model

Defect ID Summary

• 877041 Data Model: Interpretation project views incorrect for EM_STRUCTURAL_MODEL; cannot share models between interpretation projects with different CRS.

Database

Defect ID Summary

• 837474 Database: Enforce project upgrade and expose intermediate release information.

• 868940 Database: EXECUTE ALL TYPE Oracle system privilege is granted to PUBLIC considered an insecure practice.

• 875068 Database: PetroWorks® software, version 5000.0.1.0: Changed petrophysical parameter reverts to original value on save.




Documentation

Defect ID Summary

• 875937 Online Help: Help prjdel script error.

OpenWorks® Development Kit

Defect ID Summary

• 876826 OpenWorks® Development Kit: Using gdiReadSet with clause when we should be using gdiReadSubset in horizon minimum and maximum computations.

• 876832 OpenWorks® Development Kit: Some statements from vector subsystem not using bind variable.

• 877358 OpenWorks® Development Kit: Not using bind variables in horizon intersection computation.

• 871225 OpenWorks® Development Kit: Add units management to tolerance value for determining whether a 3D survey requires tiled transforms.

• 872967 OpenWorks® Development Kit: NANs returned as XY location of shotpoint from hsfLine.shotpointToXY.

• 878325 OpenWorks® Development Kit: hsf3dSeismicDataSet::writeXYTrace permitted index values beyond the seismic volume range.

• 871472 OpenWorks® Development Kit: Need to use bind variables in vecReadVector.

Project Management

Defect ID Summary

• 872760 Project Administration: Restore and upgrade should not copy ZGFs to all Interpretation projects.

• 873999 Project Administration: Modify > Options > Edit to remove data throws blank error message and fails.




• 874021 Project Administration: Restore removes private IDs membership if that user happens to be the same user that restores the project.

• 877995 Project Administration (Upgrade): Modify nc_upgrade_3d to check for existing horizon_data row with same geom_set_id and file name before inserting new row.

• 879143 Project Administration: Non-Default 2D storage areas are not backed up, but the files are not restored.

• 879587 Project Administration: Petrophysical_parm_value rows with well_id=0 are missing in upgraded version 5000 project.

• 880544 Project Administration (Upgrade): Seismic data sets upgrade to have larger z_npts_actual than z_npts.

GeoDataLoad™ Software

ASCII Loader

Defect ID Summary

• 874959 ASCII Loader: Serious performance degradation when loading large files.

Curve Loader

Defect ID Summary

• 845650 Curve Loader: Crashes when loading many position logs.

• 877392 Curve Loader: Error loading multiple synthetic data in version 5000.

Data Import Wizard

Defect ID Summary

• 873033 Data Import Wizard: Incorrect shotpoint/trace ratio when loading 2D shotpoint/trace file.




• 873034 Data Import Wizard: Navigation data disappears when loading 2D shotpoint/trace file.

• 875052 Data Import Wizard: Z-MAP™ grid format file from Trinity ZetaWare crashes Data Import Wizard.

Project Data Transfer

Defect ID Summary

• 870777 Project Data Transfer: Private interpretation ID gets new Owner added or assigned, and previous Owner is changed to Manage access.

• 870779 Project Data Transfer: Private interpretation ID with one user ID is changed to a new user ID if another user ID makes the transfer, and original user ID is dropped.

• 870780 Project Data Transfer: Incorrect message when transferring interpretation ID --- Multiple users for data source XXXX already exist in target; Skipping data source transfer.

• 875712 Project Data Transfer: No user associated with an interpretation ID in the source causes PDT transfer user to become owner in target.

• 876387 Project Data Transfer: 3D survey to a specific seismic storage area, not all path of dir.dat.

• 877514 Project Data Transfer: Process History transfer can sometimes turn public interpretation ID to private.

SEG Y Data Loader

Defect ID Summary

• 880733 SEG Y Data Loader: Fails when loading 3D data set.

Well Data Export

Defect ID Summary

• 878012 Well Data Export: owxAll formats fail to export all well perforation data.




Known IssuesThis section lists the important issues that exist in the OpenWorks® and GeoDataLoad™ software.


Configuration, Installation, and Generally

Defect ID Summary

• 862083 Compatibility: Network IP protocol: IPv6 and OpenWorks® applications.

• 873538 Listing of color map files (.clm) only from one specific file system.

• 875485 After choosing a project within the session form in the Well Seismic Fusion™ software version 5000.8, requests two OpenWorks® licenses.

Data Management

Defect ID Summary

• 880124 Curve Dictionary: Cannot copy selected curve group with same name for another interpreter.

• 864456 Data Domain Manager: OpenWorks® software, version 5000.0.3.0, Well Location Ground Elevation denormalized error or WAD?

• 877301 Interpretation Data Manager: Seismic Data Manager crash with numeric overflow - on seismic_data_set.max_orig_unclipped_amp.

• 862444 PowerView® Basemap: PD Send Polygon AOI from Project Basemap is corrupted.

• 847150 Seismic Data Manager: Deleting 2D seismic from.

• 862659 Seismic Data Manager: Data Catalog Tool needs to validate data sets before putting them in list to catalog.

• 866686 Seismic Data Manager: Catalog Data Tool should list seismic file name for another survey, even though same file name exist for other survey.




• 874218 Seismic Data Manager: Seismic File Storage, the storage File Name and File Location does not display the full path.

• 875398 Seismic Data Manager: Limits not documented, possible to paste in negative Line and Trace values.

• 877457 Seismic Data Manager: Allowing survey assignment for a horizon to change to different survey.

• 877931 Seismic Data Manager: Pack and Go: Copy files to export directory is ignored when doing import.

• 878707 Seismic Data Manager: Seismic File Storage date sorting.

• 879557 Seismic Data Manager: Edit 2D lines and save returned ORA-01422 UPD_SEIS_2D_LINE trigger error.

• 879578 Seismic Data Manager: 3D survey navigation - Project Coordinates are changing by clicking MB1.

• 879756 Seismic Data Manager: User with Interpret access to OpenWorks® project is able to edit/save 3D grid navigation.

• 880848 Seismic Data Manager: nc_upgrade_3d and catalog tool produced different attributes for seismic data set.

• 876229 Well Curve Viewer: Does not refresh curve changes done in the LogEdit™ software.

• 878391 Well Curve Viewer: Should handle multi-valued log curves as with stimulation DTS (Distributed Temperature Sensing) data.

• 803957 Well Data Manager: Cannot delete directional survey without first deleting the pos.

• 863005 Well Data Manager: Position log absolute values are incorrect after updating Well Location surface values.

• 867202 Well Data Manager: Surface Lat/Lon values are not cartographically converted when the PDB & IP have different datums

• 868792 Well Data Manager: Project Administration, well does not show up in interpretation project defined by Area of interest.




• 878388 Well Data Manager: Needs to be updated to handle multi-valued log curves.

This issue is apparent when stimulation DTS (Distributed Temperature Sensing) data is loaded for a well. The stimulation DTS data contains readings of time and depth measurements and a number of temperature values for each reading. The stimulation DTS data is stored in the Log Curve table associated with a well.

For stimulation DTS data, the time measurement is considered the primary measurement, and the depth (or distance) measurement is considered the secondary measurement. When stimulation DTS data is loaded into the Log Curve table for a well, the time measurements in units of seconds are loaded into the Top Depth and Base Depth columns. These columns allow time values, but the heading in Well Data Manager nominally displays the unit in a distance unit (such as feet or meters). The fields containing the data have the correct values in seconds. The depth measurements from the stimulation DTS data, which are in distance units, are stored in the Second Dimension columns of the Log Curve table.

The table below explains the stimulation DTS data stored in the Log Curve table.

Also, Well Data Manager handles single-value log curves. The DTS data has multi-value log curves.

When you click the Browse button (…) in the Log Values column of the Log Curve table, a dialog box displays with depth measurements (as in elapsed acquisition time) in seconds and a link to the temperature values as recorded in the original stimulation DTS data. The link to the multiple temperature values does not function correctly.

Log Curve Columns Meaning for Stimulation DTS Data

Top Depth — nominally in depth units

start time in seconds

Base Depth — nominally in depth units

end time in seconds

Depth Increment increment in seconds

Storage Depth Mode mode is seismic or elapsed acquisition time

Depth Mode mode is seismic or elapsed acquisition time

Columns in the Dialog Box Meaning for Stimulation DTS Data

Depth (s) — in time units in time units

Sample Values (degF) A link to the sample values. These values are in temperature units.




• 881323 Well Data Manager: Well Status History > Symbol field never updates.

• 857324 Well Symbol Editor: Information on SymbolCategories.xml.

Database

Defect ID Summary

• 869297 Database: Saving horizon in Calculator can update many horizon attribute header rows (Update Date and Update User ID fields).

Database Administration

Defect ID Summary

• 880885 Database Administration Tool: The upgrade workflow always sets the memory target and memory max target to 1024 regardless of what a user inputs in the parameter panel.

• 882608 Database Administration Tool: Changing the flash recovery area on an existing database should be moving the old files to the new file location.

• 883085 Database Administration Tool: The owdb_drop_database script in the tool does not remove the hc_SID file located in the ORACLE_HOME/database directory.

Workaround: The Oracle user or root can remove the file manually.

• 884028 Database Administration Tool: A database clone can be attempted with the same name as an existing SID. The clone process completes successfully, but fails in the post-configuration, producing RMAN errors. The failure triggers cleanup steps which remove multiple database files for the existing database instance with the same name. The cleanup of these files leaves the existing (source) database instance broken.

Documentation

Defect ID Summary

• 882924 Documentation: Uninstall procedures in Installation Guide need updating.




Installation

Defect ID Summary

• 868735 Installation: Need statement in documentation about US7ASCII being the supported and recommended Oracle database character set.

• 874566 Installation (Database): Uninstall removes flash recovery area on Linux but not Windows.

• 881890 Installation (Database): Embedded database installer allows memory_max_size less than 1024 MB.

• 883514 Installation (Database): In Windows, the entry ORACLR_CONNECTION_DATA is added to tnsnames.ora upon an embedded database creation.

• 883735 Installation (Database): During a database installation, the percent of memory defined for SGA for the database can exceed the amount of total SGA on the machine. When this happens, the schemas creation step of the database installation fails and causes the database configuration scripts to fail. These failures are not seen as errors in the installation or the log, and the database appears to be successfully created. However, because of the failures, the schemas and the memory parameters are not correct and the database will not function properly.

Workaround: Set the proper memory parameter values for the database with the Database Parameters dialog (Database > Configuration) in the Database Administration tool. Then, rerun the database installation, only selecting the install schemas option to rebuild the schemas correctly.

• 884530 Installation (Database): When installing more than one database instance on a machine the database installer moves the templates, owdbsetup, and scripts directories for the existing database instance. For the templates and scripts directories, this behavior causes no problems. However, the owdbsetup directory contains scripts that are specific to a database instance, and they are necessary for the execution of nightly hot and cold backups.

When an existing database instance has hot or cold backups scheduled, and if another database is created from the database installer, the hot or cold backups for the existing database instance will stop running. A database administrator can only know the backups are stopped by manually checking the log files or the flash recovery area.

Workarounds: Method 1: Use the Database Administration tool and its Database Backup Configuration Parameters dialog (Database > Configuration) to configure




the backups for the database instance. This method starts with the default backup configuration values.

Or

Method 2: Manually merge the files.

Interpretation ID Manager

Defect ID Summary

• 866635 Interpretation ID Manager: Delete fails when ID associated to a Stratigraphic Column.

• 872648 Interpretation ID Manager: Do not require interpretation ID to be set when launching Interpretation ID Manager.

• 878222 Interpretation ID Manager: Error updating interpretation ID from Public to Private.

Map Project Editor

Defect ID Summary

• 817852 Map Projection Editor: Add functions to support Krovak coordinate system in the OpenWorks® software

• 827141 Map Projection Editor: There should be both a Hotine Oblique Mercator and an Oblique Mercator projection type.

• 879429 Map Projection Editor: OpenWorks® software, version 5000.8 in Windows 7, does not work anymore -Xcrsedit.exe has stopped working error.

• 879900 Map Projection Editor: Mercator projection parameters need renaming for clarification.




OpenWorks® Development Kit

Defect ID Summary

• 876831 OpenWorks® Development Kit: gdiReadSubsetWithClause should support bind variables.

• 870291 OpenWorks® Development Kit: OUOM attributes read as null for OUOM behavior GDI_AUTOFILL_IF_NOT_SET.

Project Administration

Defect ID Summary

• 820497 Project Administration: Apply Seismic Constraints ORA-01403 ORA-06512 errors.

• 861575 Project Administration: Owbackup-all script not working for seismic file.

• 868182 Project Administration: OpenWorks® software, version 5000.0.3.5, owbackup-all dependant on X-Server.

• 869632 Project Administration: Delete project will create new empty OW_PROJ_DATA project folder.

• 871941 Project Administration: Version 5000.0.2.8, project database restores but interpretation project restore/create fails.

• 873249 Project Administration: Unable to extract a seismic backup file over 4 GB with Winzip.

• 875721 Project Administration: OwBatchUpgrade failed with error- Input error: File is a directory.

• 876518 Project Administration (Upgrade): Project Restore does not cancel import cleanly and does not preserve the import logs.

• 876811 Project Administration (Upgrade): Missing coordinates system definition for polygon sets and other data types after upgrading project from R2003 to version 5000.0.3.6.

• 876964 Project Administration: Backup project database and restore issue.




• 878517 Project Administration: Interpretation project refresh fails with unique constraint error.

• 879364 Project Administration: Project Backup fails for specific project with Super User.

• 880422 Project Administration: Project refresh failed when one 3D survey included marked restricted.

GeoDataLoad™ Software

ASCII Loader

Defect ID Summary

• 857127 ASCII Well Loader: For Well Header data lists well location ID as a required foreign key.

• 881565 ASCII Well Loader: Second update messes up well location and well header associations.

• 854477 ASCII Well Loader: LAS file scan and load truncates UWI from 26 to 24 characters.

Curve Loader

Defect ID Summary

• 873857 Curve Loader: Upgrade, utilize the service names.

• 877916 Curve Loader: Crashes when trying to load log curves as processed/composite after deleting pseudo-logging references in Curve Dictionary.

Data Import Wizard

Defect ID Summary

• 872765 Data Import Wizard: Throws DSR and NullPointerException on import of fault data in Z-MAP™ format.




• 876314 Data Import Wizard: ASCII reader does not correctly read data from some overlapping sections.

• 880041 Data Import Wizard: Error with loading Fault Polygon.

• 881389 Data Import Wizard: Wizard format to match 2003 Fie legacy format.

Raster Log Import Wizard

Defect ID Summary

• 879923 Raster Log Import: Clarify the documentation on owdir.dat configuration for SHARED_LOG_IMAGES.

• 880139 Raster Log Import: DRA/TIF data file fails with ‘missing tif file’ message.

Project Data Transfer

Defect ID Summary

• 835676 Project Data Transfer: Version 5000.0.1.2, horizon data not on every 2D line after Horizon Catalog update due to mismatched line definitions from two source projects.

• 865425 Project Data Transfer: Log Curve with NULL data source (Interp) fails to transfer.

• 870886 Project Data Transfer: Transferring wavelets from between projects.

• 873263 Project Data Transfer: Transfer of unassigned segments deletes all existing unassigned fault segments.

• 879385 Project Data Transfer: Error with Release Notes on Windows. Error opening this document. This file cannot be found.

• 881396 Project Data Transfer: Fails to transfer Surface Profiles to geographic project.

• 881445 Project Data Transfer: Transferring velocity models but no info in the DepthTeam™ software.

• 881869 Project Data Transfer: Document that Velocity Models can only be transferred between projects with the same CRS.




SEG Y Data Loader

Defect ID Summary

• 876638 SEG Y Data Loader: Loading 3D SEG Y takes 18 hours as opposed to 1 hour 46 minutes in the PostStack™ software.

Well Data Export

Defect ID Summary

• 854285 Well Data Export: Get error when exporting curves for multiple wells in binary formats.

• 844067 Well Data Export: The messages of the parent well and well location were not exported when only export a sidetrack well via Well Data Export.




Compatibility with Discovery™ On OpenWorks® SoftwareThe GeoGraphix Discovery™ on OpenWorks® (DOW) software directly links a Discovery™ application to the data in an OpenWorks® project, and provides a shared project environment for interpretation applications. Landmark has delivered the OpenWorks and DOW software for Release 5000. Landmark and GeoGraphix will continue to provide updates and enhancements to these products. When planning your uptake of Release 5000 and verifying your workflow, you should consider version compatibility between the OpenWorks software and the GeoGraphix Discovery on OpenWorks software.

In the Compatibility Table section below, the table indicates the level of compatibility of previous releases and of upcoming scheduled and planned releases. This table will be updated as new releases are planned. The objective is to provide closely coupled compatible versions of the software to allow you to more easily take up current releases.

GeoGraphix performs full release testing for those combinations indicated as Release in the table, but may not exercise full release testing on other version combinations. For these interactive releases, GeoGraphix performs compatibility testing between the OpenWorks and DOW software (indicated as Compatibility in the table). See the table below for the level of testing for each version combination. Although GeoGraphix does not anticipate any integration issue, it is recommended that customers also verify compatibility in their own environment.

Landmark (the OpenWorks software) and GeoGraphix (the DOW software) support the versions listed as Release in the table. However, while GeoGraphix has completed compatibility testing, GeoGraphix Support may not be able to fully support the versions listed as Compatibility in the table. When requesting support for a Compatibility environment, GeoGraphix Support works on a best effort basis to troubleshoot any issues, and if an issue needs additional attention, GeoGraphix Support reports such issues to the Research & Development group of Landmark or GeoGraphix, both. Landmark and GeoGraphix Support cannot guarantee any resolution service levels associated with issues from a Compatibility environment.

Combinations which have not been tested, either in the full release or in a compatibility environment, are listed as Untested. Combinations of versions not listed are Not Compatible and will not operate together, or the version was not released at the time this document was published.

The most current version of this information, and an overview of suggested compatibility test paths, is available as Solution Documents 170465, 176387, and 182177.




Compatibility Table

Bold in the Release Version columns indicates a major version change in the software.

DOWRelease VersionLicense Version

OpenWorksRelease Version

Verification Testing

July, 2011 5000.0.2.55000.02

5000.8.0.0 Untested

March, 2011 5000.0.2.55000.02

5000.0.3.5 Release

March, 2011 5000.0.2.55000.02

5000.0.3.2 Untested

February, 2011 5000.0.2.55000.02

5000.0.3.1 Untested

December, 2010 5000.0.2.55000.02

5000.0.3.0 Compatibility

June, 2011 5000.0.2.55000.02

5000.0.2.12 Untested

April, 2011 5000.0.2.55000.02


January, 2011 5000.0.2.55000.02


November, 2010 5000.0.2.55000.02

5000.0.2.9 Untested

November, 2010 5000.0.2.55000.02

5000.0.2.8 Untested

May, 2010 5000.0.2.55000.02

5000.0.2.5 Untested

July, 2011 5000.0.2.15000.02

5000.8.0.0 Untested

March, 2011 5000.0.2.15000.02

5000.0.3.2 Untested

February, 2011 5000.0.2.15000.02

5000.0.3.1 Untested

June, 2011 5000.0.2.15000.02


April, 2011 5000.0.2.15000.02





January, 2011 5000.0.2.15000.02


November, 2010 5000.0.2.15000.02

5000.0.2.9 Untested

November, 2010 5000.0.2.15000.02

5000.0.2.8 Untested

August, 2010 5000.0.2.15000.02

5000.0.2.7 Release

May, 2010 5000.0.2.15000.02

5000.0.2.5 Untested

July, 2011 5000.0.2.05000.02

5000.8.0.0 Untested

March, 2011 5000.0.2.05000.02

5000.0.3.2 Untested

February, 2011 5000.0.2.05000.02

5000.0.3.1 Untested

June, 2011 5000.0.2.05000.02


April, 2011 5000.0.2.05000.02


January, 2011 5000.0.2.05000.02


November, 2010 5000.0.2.05000.02

5000.0.2.9 Untested

November, 2010 5000.0.2.05000.02

5000.0.2.8 Untested

August, 2010 5000.0.2.05000.02

5000.0.2.7 Release

May, 2010 5000.0.2.05000.02

5000.0.2.5 Untested







July, 2011 5000.0.1.15000.01

5000.8.0.0 Untested

June, 2011 5000.0.1.15000.01


April, 2011 5000.0.1.15000.01


January, 2011 5000.0.1.15000.01


May, 2010 5000.0.1.15000.01

5000.0.2.5 Untested

March, 2010 5000.0.1.15000.01

5000.0.2.2 Release

September, 2008 5000.0.1.15000.01

5000.0.0.3 Release







Contacting Landmark Customer Support

Landmark software operates Technical Assistance Centers (TACs) in Australia, the United Kingdom, and the United States. Additional support is also provided through regional support offices around the world.

• Support Via Web Portal

• Technical Assistance Centers

• Regional Offices

Support Via Web Portal

Support information is always available on the Landmark Customer Support internet page. You can also submit a support request directly to Landmark Customer Support though the Landmark Customer Support Portal:

http://css.lgc.com/InfoCenter/index?page=home

To request support in the Landmark Customer Support Portal:

1. In the PIN and Password text boxes in the Please Sign In area, enter your registered personal identification number and password.

2. Click the Sign In button.

3. In the Case & Defect Information area, click the Create A New Case link.

4. In the Create Case area, fill in the necessary information. Provide details about your technical concern, including any error messages, the workflow steps where the problem occurred, and attachments of screen shots that display the problem. To help understand the concern, you can also attach other files too, such as example data files.

5. Click the Submit button. A support analyst in the nearest Technical Assistance Center will respond to your request.

http://css.lgc.com/InfoCenter/index?page=home




Technical Assistance Centers

Regional Offices

For contact information for regional offices, see the Contact Support page located at:

http://css.lgc.com/InfoCenter/index?page=contact&section=contact

If problems cannot be resolved at the regional level, an escalation team is called to resolve your incidents quickly.

Asia, Pacific8:00 am - 5:00 pm Local Time Monday-Friday, excluding holidays

61-8-9481-4488 (Perth, Australia) Toll Free 1-800-448-488Fax: 61-8-9481-1580Email: [email protected]

Europe, Africa, Middle East8:00 am - 5:30 pm Local TimeMonday - Friday, excluding holidays

44-1372-868686 (Leatherhead, UK) Fax: 44-1224-723260 (Aberdeen, UK)Fax: 44-1372-868601 (Leatherhead, UK)Email: [email protected]

Latin America (Spanish, Portuguese, English)7:00 am - 5:00 pm Local Time

713-839-3405 (Houston, TX, USA)Fax: 713-839-3646Email: [email protected]

North America7:30 am - 5:30 pm Central Standard TimeMonday - Friday, excluding holidays

713-839-2200 (Houston, TX, USA)Toll Free 1-877-435-7542(1-877-HELP-LGC)Fax: 713-839-2168Email: [email protected]

mailto:[email protected]:[email protected]:[email protected]:[email protected]://css.lgc.com/InfoCenter/index?page=contact&section=contact




Copyright and Trademark Information

© 2012 HalliburtonAll Rights Reserved

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:

Halliburton | Landmark Software & Services2107 CityWest Blvd, Building 2, Houston, Texas 77042-3051, USA

P.O. Box 42806, Houston, Texas 77242, USAPhone:713-839-2000, FAX: 713-839-2015Internet: www.halliburton.com/landmark

Trademarks3D Drill View, 3D Drill View KM, 3D Surveillance, 3DFS, 3DView, Active Field Surveillance, Active Reservoir Surveillance, Adaptive Mesh Refining, ADC, Advanced Data Transfer, Analysis Model Layering, ARIES, ARIES DecisionSuite, Asset Data Mining, Asset Decision Solutions, Asset Development Center, Asset Development Centre, Asset Journal, Asset Performance, AssetConnect, AssetConnect Enterprise, AssetConnect Enterprise Express, AssetConnect Expert, AssetDirector, AssetJournal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, AssetOptimizer, AssetPlanner, AssetPredictor, AssetSolver, AssetSolver Online, AssetView, AssetView 2D, AssetView 3D, BLITZPAK, CartoSnap, CasingLife, CasingSeat, CDS Connect, Channel Trim, COMPASS, Contract Generation, Corporate Data Archiver, Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot, Decision Management System, DecisionSpace, DecisionSpace 3D Drill View, DecisionSpace 3D Drill View KM, DecisionSpace AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace Atomic Meshing, DecisionSpace Desktop, DecisionSpace Nexus, DecisionSpace Reservoir, DecisionSuite, Deeper Knowledge. Broader Understanding., Depth Team, Depth Team Explorer, Depth Team Express, Depth Team Extreme, Depth Team Interpreter, DepthTeam, DepthTeam Explorer, DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery 3D, Discovery Asset, Discovery Framebuilder, Discovery PowerStation, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth-Model, Drillworks, Drillworks ConnectML, Drillworks Predict, DSS, Dynamic Frameworks to Fill, Dynamic Reservoir Management, Dynamic Surveillance System, EDM, EDM AutoSync, EDT, eLandmark, Engineer’s Data Model, Engineer’s Desktop, Engineer’s Link, ESP, Event Similarity Prediction, ezFault, ezModel, ezSurface, ezTracker, ezTracker2D, FastTrack, Field Scenario Planner, FieldPlan, For Production, FrameBuilder, Frameworks to Fill, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, Geometric Kernel, GeoProbe, GeoProbe GF DataServer, GeoSmith, GES, GES97, GESXplorer, GMAplus, GMI Imager, Grid3D, GRIDGENR, H. Clean, Handheld Field Operator, HHFO, High Science Simplified, Horizon Generation, I2 Enterprise, iDIMS, Infrastructure, Iso Core, IsoMap, iWellFile, KnowledgeSource, Landmark (as a service), Landmark (as software), Landmark Decision Center, Landmark Logo and Design, Landscape, Large Model, Lattix, LeaseMap, LithoTect, LogEdit, LogM, LogPrep, MagicDesk, Make Great Decisions, MathPack, MDS Connect, MicroTopology, MIMIC, MIMIC+, Model Builder, NETool, Nexus (as a service), Nexus (as software), Nexus View, Object MP, OpenBooks, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire, OpenWire Client, OpenWire Server, OpenWorks, OpenWorks Development Kit, OpenWorks Production, OpenWorks Well File, PAL, Parallel-VIP, Parametric Modeling, Permedia, 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, Power Interpretation, PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, PowerModel, PowerView, PrecisionTarget, Presgraf, PressWorks, PRIZM, Production, Production Asset Manager, 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+, Quiklog, 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, Reservoir Framework Builder, RESev, ResMap, 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, SmartFlow, smartSECTION, smartSTRAT, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel, StrataSim, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SurfNet, SynTool, System Start for Servers, SystemStart, SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team Workspace, TERAS, T-Grid, The Engineer’s DeskTop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, TracPlanner Xpress, Trend Form Gridding, Trimmed Grid, Turbo Synthetics, Unconventional Essentials, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, vSpace, vSpace Blueprint, vSpace Onsite, WavX, Web Editor, Well H. Clean, Well Seismic Fusion, Wellbase, Wellbore Planner, Wellbore Planner Connect, WELLCAT, WellCost, WellDirect, WELLPLAN, WellSolver, WellXchange, WOW, Xsection, You’re in Control. Experience the difference, ZAP!, ZetaAnalytics, and Z-MAP Plus are trademarks, registered trademarks, or service marks of Halliburton.

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

NoteThe information contained in this document is subject to change without notice and should not be construed as a commitment by Halliburton. Halliburton 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 Products

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

$OWHOME/docs/third_party.pdf Linux

%OWHOME%\docs\third_party.pdf Windows

Disclaimer

The programs and documentation may provide links to external web sites and access to content, products, and services from third parties. Halliburton is not responsible for the availability of, or any content provided on, third party web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Halliburton is not responsible for: (a) the quality of third party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Halliburton is not responsible for any loss or damage of any sort that you may incur from dealing with any third party.

OpenWorks® Software Version 5000.8.1.0 Release NotesWhat’s In This ReleaseWelcome to the OpenWorks® SoftwareNOTICE: Changes to Oracle Licensing — Oracle Embedded Software License (ESL)NOTICE: Future Support for Operating Systems

System RequirementsInstallation InstructionsThird Party ApplicationsInternational Trade ComplianceDefinitions

Enhancements and New FunctionalityOpenWorks® SoftwareGeodataLoad™ Software

Fixed IssuesOpenWorks® SoftwareConfiguration, Installation, and GenerallyDefect ID Summary

Data ManagementDefect ID Summary

Data ModelDefect ID Summary

DatabaseDefect ID Summary

DocumentationDefect ID Summary

OpenWorks® Development KitDefect ID Summary

Project ManagementDefect ID Summary

GeoDataLoad™ SoftwareASCII LoaderDefect ID Summary

Curve LoaderDefect ID Summary

Data Import WizardDefect ID Summary

Project Data TransferDefect ID Summary

SEG Y Data LoaderDefect ID Summary

Well Data ExportDefect ID Summary

Known IssuesOpenWorks® SoftwareConfiguration, Installation, and GenerallyDefect ID Summary

Data ManagementDefect ID Summary

DatabaseDefect ID Summary

Database AdministrationDefect ID Summary

DocumentationDefect ID Summary

InstallationDefect ID Summary

Interpretation ID ManagerDefect ID Summary

Map Project EditorDefect ID Summary

OpenWorks® Development KitDefect ID Summary

Project AdministrationDefect ID Summary

GeoDataLoad™ SoftwareASCII LoaderDefect ID Summary

Curve LoaderDefect ID Summary

Data Import WizardDefect ID Summary

Raster Log Import WizardDefect ID Summary

Project Data TransferDefect ID Summary

SEG Y Data LoaderDefect ID Summary

Well Data ExportDefect ID Summary

Compatibility with Discovery™ On OpenWorks® SoftwareCompatibility Table

Contacting Landmark Customer SupportSupport Via Web PortalTechnical Assistance CentersRegional Offices

Copyright and Trademark InformationThird Party ProductsDisclaimer