Download Seismic data not listing in selection list Problems can occur when

Seismic data not listing in selection list
Problems can occur when extremely large values are written to the seismic data attribute
fields in OpenWorks which then causes a numeric overflow. In many cases this occurs
when loading seismic data using PostStack and the Attr Min and Attr Max values are
populated. The symptoms include the seismic data not being listed in the seismic data
selection lists with in applications.
The problem is recognized in the error log of the product in which the problem occurs
when the following appears in the log:
Unable to read all instances of Seismic Data Set:
com.lgc.ow.infra.server.OWServerException: com.lgc.ow.gdi.GDIException:
ORA-01426:numeric overflow
Here is an example of the sql script to run. The OW project is DSD_NORWAY, so
substituted the OW project you want to query.
Before changing data using SQL, be sure that there is a good recent backup of the project.
Open a new xterm with the Landmark environment set.
From the OpenWorks Command Menu > System > Terminal Window
Type in the following at your prompt:
xtera{hbl3180R}% ow_prj_access <OW project name>
If the project name is DSD_NORWAY then use the command
ow_prj_access DSD_NORWAY
This should return the following:
--------------------------------------------------------------------------The project connection information is: DSD_NORWAY/N28090930@OWTERA10
--------------------------------------------------------------------------Copy and paste the project name/ID into the following:
xtera{hbl3180R}% sqlplus DSD_NORWAY/N28090930@OWTERA10
SQL*Plus: Release 10.2.0.5.0 - Production on Fri Jul 26 11:00:25 2013
Copyright (c) 1982, 2010, Oracle. All Rights Reserved.
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
Once logged into the project do the following:
SQL> spool my_sql.out
#NOTE this will capture the output and put in “my_sql.out” file
SQL> select seismic_data_set_id, max_orig_unclipped_amp from seismic_data_set;
SEISMIC_DATA_SET_ID MAX_ORIG_UNCLIPPED_AMP
------------------- ---------------------176
49.5485268
177
35.4258957
178
42.3244934
179
75.8059235
180
38.3567429
181
49.2760696
182
57.0732498
183
45.5383873
184
38.8003159
185
311.102386
186
148.359268
SEISMIC_DATA_SET_ID MAX_ORIG_UNCLIPPED_AMP
------------------- ---------------------187
142.253036
188
68.9988327
189
87.1383667
190
44.1511536
191
45.7018127
105
43330.2773
192
49.5485268
116
195.080582
144
127
193
35.4258957
194
3.4028E+38
#NOTE you can also substitute the following command for the above:
SQL> select seismic_data_set_id, max_orig_unclipped_amp from seismic_data_set order
by max_orig_unclipped_amp;
which will put the largest values at the bottom of the resulting list, but above any NULL
values.
SQL>spool off
SQL> quit
Display the “my_sql.out” file in a text editor and look for an amplitude vale that is
absurdly large, like 3.4028E+38 for example. Make note of the associated seismic data
set ID, 194 in this example.
After finding the data set with the high value, it can be removed:SQL> update SEISMIC_DATA_SET set max_orig_unclipped_amp = NULL where
SEISMIC_DATA_SET_ID = xxx;
(where xxx is the data set id from the previous query which has the abnormal amplitude
value. This would be 194 in the above example.)
SQL> commit;
to save the changes.