Troubleshooting When Seismic Datasets Will Not Display
Article ID: KB0071229
Updated On:
| Products | Versions |
|---|---|
| TIBCO OpenSpirit Runtime | 4.3 |
Description
When working with seismic datasets or lines, it is always best to have a debug flag set to document as much data as possible into a data connector log file.
When OpenWorks R5000 seismic and/or interpretation data shows up in the OSP DataSelector but not in the OSP viewers use the native Landmark Consistency Check tool to confirm the visibility of the data.
The most common problem is a DM3DOP = 6 error written in the OW5000 server log, which means either OSP cannot find the seismic files (all file extents) or the Unix file permissions are incorrect and the files are not readable. If that is the case the native Landmark apps (e.g. SeisWorks) won't work either. If SeisWorks can see the files and OpenSpirit cannot it could mean an OW5000 data store configuration problem (e.g. an incorrect OW_CONF_DIR value).
The native Landmark application has a useful tool to verify the Oracle header information is in sync with the bulk files (3d volumes, 3d seismic horizons, 2d datasets).
When OpenWorks R5000 seismic and/or interpretation data shows up in the OSP DataSelector but not in the OSP viewers use the native Landmark Consistency Check tool to confirm the visibility of the data.
The most common problem is a DM3DOP = 6 error written in the OW5000 server log, which means either OSP cannot find the seismic files (all file extents) or the Unix file permissions are incorrect and the files are not readable. If that is the case the native Landmark apps (e.g. SeisWorks) won't work either. If SeisWorks can see the files and OpenSpirit cannot it could mean an OW5000 data store configuration problem (e.g. an incorrect OW_CONF_DIR value).
The native Landmark application has a useful tool to verify the Oracle header information is in sync with the bulk files (3d volumes, 3d seismic horizons, 2d datasets).
Issue/Introduction
This article explains what error to look for in the debug log files and explains which Landmark Utility to use to assist with correcting a seismic display issue. These guidelines are assuming the use of an OpenWorks data source.
Environment
Linux
Resolution
Check the debug log file to confirm whether the display is being affected by permission issues or lack of disk visibility. This issue will be noted, in the log file, by the DM3DOP error.
For OpenWorks R5000, If the seismic bulk datasets and/or interpretation data show up in the OpenSpirit DataSelector but not in the OSP 3D or Section viewers use the native Landmark Consistency Check tool.
This tool is used to verify that the oracle header information is in sync with the bulk files (3d volumes, 3d seismic horizons, 2d datasets).
To verify:
For OpenWorks R5000, If the seismic bulk datasets and/or interpretation data show up in the OpenSpirit DataSelector but not in the OSP 3D or Section viewers use the native Landmark Consistency Check tool.
This tool is used to verify that the oracle header information is in sync with the bulk files (3d volumes, 3d seismic horizons, 2d datasets).
To verify:
- From the OpenWorks Command Menu, bring up the Seismic Data Manager.
- Select the "Consistency Check" from the Tools menu. This will produce a report showing what bulk files are missing. If such files are missing, then the OSP Scan Utility will not be able to find them either.
- When performing this check, make sure that you use the same Unix host and userid as used to start the OW5000 data server. The host could affect disk visibility and the userid affects the file permissions. (this is the same Host and user specified in the OSP User Wizard)
- Another possibility is that something could be wrong with the district's dir.dat/owdir.dat files (e.g. might have invalid directories or directories that are not visible). Look for the following in the OW5000 debug log: Error creating dir for External Project File right after the "Newing up the osp_OpenWorks::SwDevkit object".
- Lastly, the OW_CONF_DIR contains the district.dat file. The district.dat file contains the directory where the dir.dat/owdir.dat files are located. The user needs to look in those files to make sure they have valid unix access to the data directories that point to where the external binary files are located.
Feedback
Yes
No
Powered by
