Académique Documents
Professionnel Documents
Culture Documents
http://www.rainlane.com/dispbbs.asp?BoardID=11&replyID=48712&id=16555&skin=0
Contents 目录
Overview 简介
What's in this Manual
Index 索引
• Tools for Troubleshooting. This section describes the OpenWorks utilities you can use to verify that
system processes are running. These tools can help you pinpoint the causes of problems.
• Troubleshooting Data-Related Problems. This chapter provides solutions to some problems you
might encounter accessing projects or data, as well as problems with importing or exporting data.
• Troubleshooting Seismic Display Problems. This chapter can help you with seismic display
problems, color bar problems, and problems displaying computed contours and well data.
• Troubleshooting Hardcopy Problems. This chapter contains solutions to problems with queuing and
printing hardcopy and plotfiles.
• Troubleshooting the Help System. Use this chapter when you are unable to access help files for an
application.
• Troubleshooting System Problems. This chapter describes the system processes used by Landmark
applications and provides tips for solving various problems with OpenWorks and SeisWorks.
• Troubleshooting ORACLE Problems. This chapter provides detailed steps you can take to correct
problems with your ORACLE database.
• Common Error Messages. This chapter contains the procedure for setting your system’s error level,
which determines the types of error message that will appear. This chapter also describes typical system
error messages.
• Requesting Technical Assistance. This chapter tells you how to use the TAR Tool to report problems
to Landmark support personnel.
• Checking Disk Space 检查磁盘空间. This section explains how to determine the amount of disk
space is available on your system.
• Last Resort 最后的办法. This section tells you how to reboot your system, which you should only
do if the steps described in the preceding steps have failed to resolve your problem.
• Where to Look for More Help 浏览其他章节,寻求更详细的帮助. This section describes the
remaining chapters of this manual, which contain more detailed troubleshooting procedures.
Methods for dealing with each of these problems are explained on the following pages.
Many problems can be remedied quickly using non-diagnostic strategies. Often you can resolve
problems by exiting the application you are using and then reopening the program. Try this approach if
the
windows are not opening properly, data appears to be inaccurate, faults are posted in the wrong place,
horizons are not properly posted, etc.
• If an application you are using becomes unresponsive, you might need to kill it. See “Killing
Processes” on page 8.
• Expand your Command Menu to show the status of vital processes. Start any processes that are not
running. See “Checking Essential System Processes” on page 5.
• Exit OpenWorks using the Exit command from the OpenWorks command menu, and restart
OpenWorks.
Restarting OpenWorks restarts all individual tasks. If restarting OpenWorks fails to correct the problem,
you can attempt to further diagnose the problem by working with the individual processes (tasks).
Note, however, that in general it is best not to attempt to restart individual applications and tasks.
To check the status of OpenWorks processes, click on the Landmark logo (命令菜单左上角的兰马徽
标 ), located on the left side of the OpenWorks Command Menu. The Runtime Status Box appears
under the command menu.
The most critical OpenWorks processes are listed, preceded by a check box(复选框). If a check box is
green, the corresponding process is running on your system or is available from a server. If the box is
red, the process has not been started on your system or is not available from a server.On CDE desktops,
a check displayed in a red or green check box indicates that OpenWorks has performed a verification on
the status of this resource.
To toggle the status box off, click on the Landmark logo again. To reinvoke the status box (after
pinpointing your problem and correcting it), double click on the Landmark logo. This toggles the status
box off and then back on.
Red and green check boxes can signify表示 different conditions on servers than on clients. The table on
the following page lists these differences.
LAM (License Green. Your system is able to check Green. Your system is able to check
Application Manager) out licenses via the specified license out licenses via the specified license
server. Red. Your system is not able server. Red. Your system is not able
to check out a license through the to check out a license through the
specified license server. The license specified license server. The license
server may be dead. Or, it may be server may be dead. Or, it may be
inaccessible. inaccessible.
System Resource Green. xsrm is running. Red. xsrm Green. xsrm is running. Red. xsrm
Monitor (xsrm) is not running. is not running.
Remote Services Green. RSvD is available on the Green. RSvD is available on the
Daemon (RSvD) ORACLE server. Red. RSvD is not ORACLE server. Red. RSvD is not
available on the ORACLE server. available on the ORACLE server.
Network Services Green. NetD is available on the Green. NetD is available on the
Daemon (NetD) ORACLE server. Red. NetD is not ORACLE server. Red. NetD is
available on the ORACLE server. not available on the ORACLE
server.
Starting Processes
If a process is not running, you can restart it by typing the following from the UNIX shell window:
This command tells the system to redirect the standard error stream to /dev/null. The ampersand (&) tells
the system to run this process in the background. This is done so the process will not lock up the window
from which it was started.
The process names are as follows:
Process Name Description Permissions
required
viewer FrameViewer
Killing Processes
When restarting some individual OpenWorks tasks, you sometimes must kill and restart
other tasks as well for OpenWorks to operate properly. The following chart shows the
tasks you must kill and restart if you restart certain tasks.
If you restart this: You must also kill and restart this:
mwm None
Before you attempt to kill individual processes, try to exit OpenWorks via the Command Menu. If you are
able to do this, use startow to restart OpenWorks from the Console Window.
Killing a Process
If you are unable to exit and restart OpenWorks, try to kill one or more processes. To stop a
process, use one of the commands described below.
stop_pd
• To kill or stop any other current processes, you must first find out the process ID number. To do
this type
A listing appears showing the process ID. To kill the process, type
kill -9 ####
• To kill multiple processes, type the process numbers separated by spaces. For example:
####, $$$$, %%%% are three different process numbers. If you attempt to kill a process that is not
running, this message appears
If an application hangs and you lose control of the mouse cursor, try killing the process from another
workstation on the system.
telnet <your_machine_name>
2. When prompted for a login, enter the login you normally use on your machine. The prompt should now
show your machine’s name.
ps -ef
exit
If you can’t kill the application, you may want to try restarting the X server.
On a Solaris System
ps -ef|grep mwm
ps -ef|grep .xinitrc.r5
2. To kill X, type
kill <PID#>
Do this for both processes found in step 1. This should return you to a white screen.
startserver
You may find you need to log out by typing exit, then login with your user name, and then use the
startserver command.
On an IBM System
ps -ef|grep X
2. To kill X, type
kill <PID#>
startserver
On a Silicon Graphics System
On an SGI system, log out and log back in to restart the X server.
3. When the login dialog box appears, select your login ID and click on Log In.
df -I (IBM)
All values are shown in blocks where a block equals 1024K bytes.
Checking disk space may provide you with information about where you have space problems.
Last Resort
If all troubleshooting efforts have failed, reboot your system.
If you cannot kill the application from another machine, you may want to shut down the system and then
reboot it. Shutting down the system is safer than performing a panic halt because it forces your file changes
to be written to disk and it closes the open files on your system, preventing them from becoming corrupted.
A message stating that the system is about to be shut down will be displayed on terminals of users that are
logged into your machine.
The message will also be posted on the terminals of systems that are mounted to your machine.
Moments after the message is posted, your system will be shut down.
If your system hangs and you cannot log into it remotely, you may have to abort and reboot. Aborting and
rebooting is a risky way to restart your system because it does not force your file changes to be written to
disk and it does not close the open files on your system. As a result, if you abort and reboot, you risk losing
changes and corrupting open files.
Before you abort, make sure that the system is truly dead. It is possible that you are experiencing a network
problem, which could cause delays in system activity. If this is the case, wait until the network server
responds.
On a Sun system
On an IBM system
Press the reset button. When rebooting is completed, restart OpenWorks and SeisWorks
Help System •inability to display help docu-ments “Troubleshooting the Help Sys-tem” on
for an application page 97
Three other chapters in this manual can be useful when you are attempting to solve system problems.
Chapter Description
“Tools for Troubleshooting” on page 17 Describes the OpenWorks utilities you can use to verify that
system processes are running. These tools can help you
pinpoint the causes of problems
“Common Error Messages” on page 131 Contains the procedure for setting your system’s level of
error message reporting and describes typical system error
messages.
“Requesting Technical Assistance” on page 145 Tells you how to use the TAR Tool to report problems to
Landmark support personnel.
• Environment Status Tool on page 18. Checks if the environment is correctly configured for OpenWorks
and the ORACLE system.
• Project Query on page 20. Uses SQL to query the current Oracle database on the size, location, and user
accessibility of a particular OpenWorks project.
Describes the LGC_DEBUG utility, which allows you to produce a report of files accessed by SeisWorks.
This report can help you determine causes of data access problems.
The Environment Status Tool assumes there are no RDBMS-related problems. For this reason, before you
invoke the Environment Status tool, you should confirm that Oracle is installed and functioning correctly.
To open the Environment Status tool from the OpenWorks Command Menu, click on Utilities à
Environment Status Tool. The following window appears.
The first thing that you should do when you have a problem displaying your wells is to determine whether
the Oracle database is properly installed and running. Next, you should consult the Environment Status
Tool to determine whether the OpenWorks environment is properly configured.
Select Status à System from the menu bar of the Environment Status Tool. The System Status Menu
appears.
1. In the OpenWorks Command Menu, click on Project àProject Admin. The Project Administration
dialog box appears.
2. In the Project Administration dialog box menu bar, select the project of interest and then click on Project
àQuery. You will receive a window similar to the one shown below.
Project Query has a number of read-only information fields that provide details about the size, space, and
accessibility of the Oracle project. Many of the entries in this dialog box refer to the project “tablespace.”
This is the disk space allotted to the project by Oracle.
Project Availability Project status. Currently, the only status available for this field is
ONLINE.
Project Default Table Extent The tablespace consists of one or more files. To store data for a
Parameters particular table within the tablespace, space is allocated in
blocks called a “extents.” When a table is created, it is
allocated an initial extent. As data is added, if the current extent
is used up, an additional extent is allocated.
A size may be specified for the initial extent and for the second
extent allocated (or the Next Extent). All subsequent extents
will be allocated in the size of the Next Extent. If a Percent
Increase has been specified, all subsequent extent allocations
will be a certain percent larger than the previous one.
Directories, names, and sizes of files that collectively make up
the “tablespace.” You use these names in SQL queries.
When you create an OpenWorks project, you are given the
Tablespace File option of making a small, medium, or large project. These
result in tablespace sizes of approximately the following sizes:
small = 60 MB
medium = 100 MB
large = 200 MB
You can add disk space to the existing tablespace using the
Project Administration: Modify option.
Free Space Available Space available for additional project data in the tablespace.
For more information on Oracle and Oracle troubleshooting, refer to “Troubleshooting Oracle Problems”
on page 71.
Activating/Deactivating LGC_DEBUG
To activate LGC_DEBUG, you set it and start SeisWorks from the same xterm window. The commands
differ slightly, depending on which type of shell you are using.
In a Bourne Shell
export LGC_DEBUG
unset LGC_DEBUG
In a C Shell
setenv LGC_DEBUG 1
unsetenv LGC_DEBUG
Using LGC_DEBUG
1. In an xterm, set LGC_DEBUG to 1, using the appropriate script for your system’s shell. (See above.)
s2d (SeisWorks/2D)
or
s3d (SeisWorks/3D)
3. When you encounter some problem in running SeisWorks, check the input/output report in the xterm
window. Perhaps the program is unable to open a needed file.
Example of Output(在此省略图示)
An example of the kind of output LGC_DEBUG produces when you start SeisWorks/3D is shown on the
following page. Note that the program searches all project directories for each file (/pa, /pb, /pc, etc.).
So you see many failed attempts to open the file before the program tries the right directory. This is normal.
The problem occurs when all attempts to open a particular file fail.
Beginning of LGC_DEBUG Output for a Successful SeisWorks/3D Session
• Data Troubleshooting Checklist on page 26. This section contains steps you can take to check for
problems in your OpenWorks or Oracle setup.
• Oracle Environment Variables on page 35. This section describes the environment variables that must
be set for Oracle to function properly.
• Troubleshooting Data Access on page 36. This section contains solutions for common data access
problems in OpenWorks and SeisWorks.
• Problems with Horizons in SeisWorks on page 47. This section discusses problems associated with
creating and manipulating horizons in SeisWorks
• Problems with Faults in SeisWorks on page 49. This section describes solutions for fault data problems
in SeisWorks.
• Problems Exporting Data from SeisWorks on page 51. This section discusses problems you might
have exporting SeisWorks data to Z-Map Plus.
• Checking the Continuity of SeisWorks/2D Data Files on page 52. This section contains the procedure
for using the contest2d utility to check the continuity of 2D master projects.
• Data Loading Problems on page 54. This section provides solutions to problems that can occur after
loading data into a project.
Verify that your seismic project is linked to an OpenWorks project. This association is recorded in the plist.
dat file, which typically is in $OWHOME/conf.
plist
You will receive a list of all available Seisworks projects and their corresponding OpenWorks projects. The
SeisWorks projects are listed in the left column. The OpenWorks projects are listed in the right column.
单位机器上的例子:
blade{owuser:/home/blade/owuser}% plist
blade{owuser:/home/blade/owuser}%
2. Confirm that an OpenWorks project is paired with your seismic project. If none is, use Seismic Project
Associate (available from the Seismic Project Manager’s Project menu) to associate an OpenWorks project
with the seismic project.
SeisWorks/2D users can find more information in the “Master Projects” and “Working Projects” chapters
of the SeisWorks/2D Project Management manual. SeisWorks/3D users should refer to the “3D Projects”
chapter of the SeisWorks/3D Project Management manual.
3. If an OpenWorks project is listed for your seismic project, your problem may be that Oracle does not
recognize you as a user for this project. In this case, perform the following steps:
• Use the Project Query option in the Project Administration utility to determine if you are set up as an
Oracle user for the project (see the OpenWorks Data Management manual for more information on Project
Administration).
If Project Administration does not work, you have a problem in your Oracle or OpenWorks setup. Proceed
to “All Users: Is Your OpenWorks Environment Properly Configured?” on page 27.
• If you are not a valid user, get the project manager to grant you user access.
• If you are a valid user, then the problem lies either with your OpenWorks environment or with the Oracle
setup. Proceed to “All Users: Is Your OpenWorks Environment Properly Configured?” below.
After verifying that you have user access to a valid OpenWorks project, you should look for errors in the
way OpenWorks is set up. Here are a few quick steps to check the OpenWorks configuration.
1. First, determine if the location of the OpenWorks runtime directory is properly defined by the
$OWHOME variable. To do this, type the following command:
lgc_getenv OWHOME
/home/OpenWorksblade{owuser:/home/blade/owuser}%
• Using vi or another editor, set the value in your initialization file ($HOME/.lgclogin or $HOME/.
lgcprofile).
• Log out.
• Log in.
• Start OpenWorks.
3. The OWSYSSID variable must also be set properly. To check this variable, type the following
command:
lgc_getenv OWSYSSID
The response should be the name of the Oracle instance where the OpenWorks system database is located.
By convention, the name of the Oracle instance is the node name preceded by ow. Example: for the node
nova, the OWSYSSID would be ownova.
4. If necessary, set OWSYSSID to a correct value either by using the Project Status tool or according to the
following steps.
owblade
blade{owuser:/home/blade/owuser}%
• Using vi or another editor, set the value in your Landmark configuration file ($OWHOME/conf/lgcenv.
cf).
• Log out.
• Log in.
• Start OpenWorks.
5. If NetD is not running, you will be able to access Oracle projects, but you will be unable to create,
modify, or delete projects using Project Administration or Project Create. RSvD allows OpenWorks
applications to access services on remote machines.
To check that the Network Services Daemon (NetD) and Remote Services Daemon (RSvD) are
functioning, perform the following steps:
• In the OpenWork Command Menu, click on the Landmark logo to invoke the Runtime Status Box.
• Look for a green check box next to Network Services Daemon and Remote Services Daemon, indicating
that the daemons are operating.
• If the check boxes are red, query whether the daemons are running. Use the following commands (Solaris,
SGI, and IBM):
checkRSvD
start_netd
This should also restart RSvD. RSvD can be initiated only by NetD.
实例:
blade{owuser:/home/blade/owuser}% checkRSvD
blade{owuser:/home/blade/owuser}% start_netd
blade{owuser:/home/blade/owuser}%
6. If, after performing all these checks, you still have trouble accessing the Oracle project, proceed to “All
Users: Can You Access Oracle?” below.
At this point you know that you have a valid OpenWorks project, but you cannot reach the Oracle database
from within SeisWorks. The next step is to query Oracle directly using SQL (structured query language 结
构化查询语言).
If this attempt fails, you will know that the problem lies in the Oracle setup.
1. First, check that the environment variable OWSYSSID is properly set. Type this command:
lgc_getenv OWSYSSID
The response should be the name of the Oracle instance where the OpenWorks system database is located.
By convention, the name of the Oracle instance is the node name preceded by ow. Example: for the node
nova, the OWSYSSID would be ownova.
2. If necessary, set OWSYSSID to a correct value either by using the Project Status tool or according to the
following steps.
• Using vi or another editor, set the value in your Landmark configuration file ($OWHOME/conf/lgcenv.
cf).
• Log out.
• Log in.
• Start OpenWorks.
3. If OWSYSSID is properly set, use its value to query the Oracle database. Type this command(输入蓝色
部分):
sqlplus owsys/owsys@<OWSYSSID>
You should get an SQL prompt, indicating that you are now in SQL and can view data in the database.(用
quit退出)
4. If your SQL query is not successful, you need to check whether your command reached the correct
sqlplus. Issue the following two commands:
which sqlplus
echo $ORACLE_HOME/bin/sqlplus
• The “which sqlplus” path should point to the same location as does the echo command. If it does not, the
system administrator may need to redefine your $PATH environment variable. Then repeat Step 3 and
continue from there.
• If the two paths are the same, you have a problem with your Oracle setup. Oracle may not be running, or
the SQL Net Listener may not be running. Proceed to Step 9.
5. If your SQL query is successful, but you are having trouble accessing the database under your own user
name, the problem may be that you are not established as a valid Oracle user. Perform the following steps:
cd $OWHOME/bin
su - oracle
• Invoke the Oracle Database User Management tool with the following command
orauser
The Oracle Database User Management tool should appear in the xterm.
6. Choose Option 4, Show Externally Identified Users of the Oracle Database. A list of valid Oracle
users appears.
7. If you are not in the list of Oracle users, press Return and then choose Option 1, Adding a user to the
Oracle Database. Follow the prompts to add yourself as an external user.
8. Now you must become a project user for the OpenWorks project of interest. Use Project Query in the
Project Administration utility to identify a project user with manager status, and get that user to grant you
access to the project.
9. To check the status of the Oracle environment, select System and then Database Sanity Checker from
the OpenWorks Command Menu.
10. From the menu bar of the Database Sanity Checker, select Option and then Oracle.
The Oracle Setup dialog box appears, with information about essential Oracle environment variables, files,
and processes.
11. Check that the environment variables are properly set. Use the following guidelines:
• ORACLE_HOME should be set to the top-level directory of your Oracle installation. (The default setting
is $OWHOME/oracle.)
Also, ORACLE_HOME must point to the actual Oracle directory, not to a link. To check this, go to
$OWHOME and issue an “ls -l” command; this listing will show if a link exists.
• ORACLE_SID should be set to the system ID for the database server your system will be accessing.
If either of these Oracle environment variables is not set correctly, set it using the following steps.
• Using vi or another editor, set the value in your initialization file
($HOME/.lgclogin or $HOME/.lgcprofile).
• Log out.
• Log in.
• Start OpenWorks.
12. In the Oracle Setup dialog box, check that the following Oracle processes are running.
• Recovery Process
• Process Monitor
• System Monitor
• Database Writer
• Log Writer
server.
If your machine is a client and you get Oracle from a remote server, the
Database Sanity Checker will show all Oracle processes as not running (as
indicated by a red radio button). This is normal.
To check the Oracle processes, you must invoke the Database Sanity
Checker from the server where Oracle resides. Perform the following steps:
$OWHOME/bin/xdbsanchk
13. If any of the five Oracle processes are not running, shut down Oracle and restart it. Use following
commands:
su - oracle
dbshut
dbstart
14. If the SQL*Net V2 Listener Process is not running, OpenWorks applications will not function. To start
the listener, use the following commands:
su - oracle
lsnrctl
start
quit
Both Oracle and OpenWorks can function without Archiver being activated.
15. If you cannot access the database with all essential processes running, the problem may be that your
machine is a client to an Oracle server, and the server is not listed in your tnsnames.ora file.
lgc_getenv OWSYSSID
实例:
blade{owuser:/home/oracle/OraHome1/network/admin}% ls
samples/ sqlnet.ora.bak
OWBLADE =
(DESCRIPTION =
(ADDRESS_LIST =
(CONNECT_DATA =
(SERVICE_NAME = owblade)
EXTPROC_CONNECTION_DATA.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
blade{owuser:/home/oracle/OraHome1/network/admin}%
• If no such entry exists, or if the existing entry is incorrect, see the OpenWorks System Administration
manual set for complete instructions on modifying the tnsnames.ora file.
• Oracle is running.
16. If you still cannot access the database, the problem may be an incorrect Oracle listener port. To check
this possibility, select Utilities and then Environment Status Tool from the OpenWorks Command Menu.
17. From the menu bar of the Environment Status Tool, select Status and then Oracle. The Oracle Status
Menu appears.
19. Check that this same value is recorded in the file /etc/services.
In this example, “1521” is the number of the Oracle Listener Port as posted in the Environment Status Tool.
20. If /etc/services does not have a “tnslsnr” entry, add one, or contact your system administrator for
assistance.
21. If the Oracle setup checks out and you still cannot access the database, contact your Landmark customer
support representative for assistance.
The following data access problems may occur in OpenWorks installations using Oracle. For more detailed
information on Oracle troubleshooting, see “Troubleshooting Oracle Problems” on page 71.
The data access environment variables must be set correctly. Use the Environment Status Tool to check
them. The OWSYSSID should be the name of the machine where the system database resides. If a variable
is not set correctly, then check the value of the OpenWorks environment variable OWSYSSID.
lgc_getenv OWSYSSID
If the node name is not the same as the node where OWSYS is found then you need to edit the file
$OWHOME/conf/lgcenv.cf and correct the OWSYSSID designation so that it has the letters ow followed
by the correct node name. For example, if the correct node name is nova:
OWSYSSID ownova
Check that OWSYS exists on the node specified by the OWSYSSID environment variable. Do this by
logging on to the node where OWSYS should exist and entering the following command:
sqlplus owsys/owsys
The system should make a connection. If it does not, be sure that Oracle is properly installed and running
(see the “Troubleshooting Oracle Problems” on page 71 chapter).
Also check that you have access from a remote node. To do this, log in to a remote node that should have
access to the node where owsys database exists.
sqlplus owsys/owsys@value_of_owsyssid
If this fails to connect, check that Oracle is running properly at each node. If that is the case and you are
still unable to connect, then you should check that the network privilege to connect between the two nodes
is properly set in Oracle.
Once you are in OWSYS you should check to see that the OpenWorks tables exist.
sqlplus owsys/owsys
First check that OWSYSSID is set properly. If it is set properly then the next step is to check that the tables
in OWSYS have the proper values.
There are three tables that should contain information describing a project: ow_sys_project,
ow_sys_min_max, and ow_sys_pal. The ow_sys_project and ow_sys_min_max tables should have one
entry for each project. The name for a project must be unique. The ow_sys_pal should have at least one
entry per project. This entry is the project manager with security level set to 3.
sqlplus owsys/owsys
If the project in question has been deleted from OpenWorks but still exists in Oracle, see also “A Project
Fails to Delete Completely” on page 41.
The Data Access System Cannot Find the Data Files 数据存取系统找不到数据文件
The data access system must have two data files located in the $OWHOME/dat/idb directory. These files
are sql.dat.oracle and xref.dat.
If these files are not found, the GDI initialization will fail and return an error on the command line:
$OWHOME/dat/idb/xref.dat
or
If the ERR_LEVEL environmental variable is set to 2 or less, then an error statement is produced:
or
Locate and move sql.dat and xref.dat into the $OWHOME/dat/idb directory to correct this problem. Make
certain that these files have read access permission. Check this with the command
ls -l $OWHOME/dat/idb
total 489
If three r’s do not exist in the second entry for each file, access may be denied to these files. To correct this
situation, on the command line enter
If relations exist between database verification tables, yet these relations are not specified, then the entire
access may fail. For example, if an attempt is made to read a casing instance without a formation name and
the vc_stratunitname has no “UNKNOWN” entry, then the access will fail.
The verification tables (VC 验证表) have an ID and a name as their basic components. There must be one
entry that has an ID of zero value and a default name of UNKNOWN, so that unspecified relations can
return this instance, allowing the entire access to succeed. For example, the vc_stratunitname table needs an
entry
strat_unit_name_id = 0
strat_unit_name = “UNKNOWN”
This allows successful access of a casing without having to specify the formation name.
If unexpected depth values are set, the depth preference may not be set. The default is the project depth
units and measured depth.
If no priority list is set and an api routine uses the priority list, then an error message will occur:
There are certain data types that check for ownership when a modification is being made. These are
• Calculated Lithology
• Horizon Parameters
• Pick
• Well List
• Zone
• Zone Attribute
• Zone Detail
If an update or deletion is attempted by a user who does not own the instance, then error messages occur if
the ERR_LEVEL is set at 0 or 1.
or
On rare occasions, a project you delete in OpenWorks may fail to completely delete from the Oracle
database, although the name no longer appears in any project list. In that event, you cannot use that project
name again with a project create or restore command.
In this circumstance, the following commands can be issued to manually delete all remnants of the project
from the database. This approach should be used only by the Oracle database administrator and only on any
rare occasion when a normal project delete has not succeeded.
1. Login as the oracle dba account owner (e. g., oracle) and use the Server Manager utility to access the
privileged Oracle user called internal:
login: su - oracle
password: <dba_password>
svrmgrl
connect internal
2. Now issue all commands needed to fully delete the project “PROJECTNAME” from the database (here,
indented lines represent wrapped lines):
alter session set current_schema=owsys;
project_name=’PROJECTNAME’;
project_name=’PROJECTNAME’;
project_name=’PROJECTNAME’;
project_name=’PROJECTNAME’;
project_name=’PROJECTNAME’;
project_name=’PROJECTNAME’;
project_name=’PROJECTNAME’;
3. You must also delete all tablespace related to the project. First, locate the proj.dbs file:
connect internal
4. Make note of the path to the project data file (i.e., the location of the proj.dbs file).
cascade constraints;
6. Finally, change to the directory where the proj.dbs file is located, and remove it.
cd <path_to_proj.dbs>
rm proj.dbs
When you move interpretations from 2DPlus or 3DPlus to SeisWorks, you could encounter problems when
trying to access the old data files.
If you press List in the Main Menu window and your project does not appear in the Project Selection dialog
box, perform the following steps:
plist
A list of all your SeisWorks projects and their associated OpenWorks and master projects will be displayed.
实例:
blade{owuser:/home/blade/owuser}% plist
------------ -------------------
blade{owuser:/home/blade/owuser}%
2. If the missing project is not listed, edit the plist.dat file. (This is the file from which the list of available
projects is generated.)
3. Check that the project directories exist and have open permissions.
• If the problem is permissions, use the following command to recursively give open permissions to each
directory and its subdirectories. You must have superuser status when you issue this command:
• If the project directories are missing, reload them from a backup tape.
4. Check that the project definition file (.ps2 in SeisWorks/2D or .pds in SeisWorks/3D) is in the project
sys directory and has open permissions.
In 2DPlus every data file you created was owned by lgc and had a user ID of 200 and a group ID of 10.
Now, in SeisWorks/2D you have the latitude to establish different user and group IDs.
If SeisWorks users are using different accounts besides lgc with different user and group IDs, they may run
into permission problems when they try to access old 2DPlus files. Simply change the permissions to grant
open access as described in “Changing the
In 3DPlus, every data file you created was owned by lgc and had a user ID of 200 and a group ID of 10.
Now, in SeisWorks/3D you have the option of establishing different user and group IDs.
If you are using different accounts besides lgc with different user and group IDs, you may run into
permission problems when you try to access old 3DPlus files. Simply change the permissions to grant open
access. For instructions on checking and changing permissions, see “Changing the Permission Mode of a
File” below.
Permissions are assigned to both directories and files. The permission mode of a directory determines
whether users can read or write to the files in the directory. The permission mode of a file determines
whether users can read, write to, or execute the process specified by that particular file.
Users belong to three different categories: (1) the owner of the file, (2) the group to which the owner
belongs, and (3) all others. If you are denied permission to read or write to the files in a directory, or to
read, write to, or execute a particular file, chances are that you must change a permission mode. You can
change the permissions assigned to a
particular directory or file only if you are the owner of the directory or file, or you have superuser status.
Examining the Currently Assigned Permissions 检查当前指定的权限
To view the current permission mode of a file, cd to the directory containing the file and use the ls -
lag command to display information about the files in the directory. You will receive a display that
resembles the following screen.
实例:
blade{owuser:/home/blade/owuser}% ll
blade{owuser:/home/blade/owuser}%
Column 1(红) indicates whether the file is a directory, a file, or a link. A dash (–) indicates that the file is a
file. A “d” indicates that the file is a directory. An “l” indicates a link to a file or directory.
Columns 2 through 4(蓝) indicate the permissions for the user. Columns 5 through 7(绿) indicate the
permissions for the group to which the user belongs. And Columns 8 through 10(粉) indicate the
permissions for all other users.
To determine what permissions are currently assigned to the different user types, use the following table.
x Allows the prospective user to execute the file. This option only applies to files
that are executables.
- Denies access of the particular type indicated by the respective column. That is, if
a dash (–) appears in a read column, the read permission is denied. If it appears in a
write column, the write permission is denied. If it appears in an execute column,
the execute permission is denied.
The variables that can be used in this command are described in the table below.
Variable Description
<user type> Specifies which of the user types is to be affected by the permission
change. Valid codes for user types: u is the owner, g is the group, and
o is all others.
<permission code> Specifies the type of permission to be granted or denied. Valid codes:
r applies to read privileges, w applies to write privileges, x applies to
execute privileges.
If you are the owner of a directory or file, you can grant read, write, and execute permissions to all user
types by using the following command
This method uses the octal number 777 to assign permissions. The octal number method of assigning
permissions is described in the online “man pages” for chmod (which you can view by typing man chmod
at a system prompt).
To change the permissions within a particular directory and apply the changes to all subdirectories and their
files, you can use the following “recursive” chmod command.
If you receive an error message notifying you that you cannot make another horizon:
• Check for duplicate horizon data (.hzd) files. If you find duplicates, delete them.(删除重复的层位文
件)
• Check that the horizon catalog (.hrz_cat) exists. If it does not, create one with the crtcat utility.
• Check whether you have exceeded the limitation of 4096 horizons currently in the working project. If you
have, you must use an existing horizon plane, since the 4096 horizon limit is arbitrary and irreversible.
Eliminating existing horizons will not enable you to add additional horizons. Instead, find a horizon that
you no longer need. Display the horizon in the Map View and use the Areal Delete option to delete the
interpreted data that is currently correlated with the horizon. Use the Attributes option in the
SeisWorks/2D
First, check to see if the horizons are still in the master project but simply not appearing in your working
project. Select Horizons à Global Manager à Global Add to Project. If the horizons you need are
listed, select them for your working project. If the horizons of interest are not listed in the Global Add to
Project dialog box, check to see if both horizon header(层位头) (.hzh) and horizon data(层位数据) (.hzd)
files are contained in the master project. If the data files are present but the header file is missing, simply
“creating” the horizon once again within SeisWorks may solve the problem. But if the data files are
missing, you will have to reinterpret the horizon or load it from a backup tape.
(例如,在master目录下:
T8h______________________________________.hzh_glb
t8h_______________________________________.hzh_glb
HE-2000-119H______________T8h____________.hzd_glb
HE-2000-119H______________t8h_____________.hzd_glb )
Check the dir.dat file to make sure that all the master project filesystems are in directories with the “global”
designation. If these filesystems have somehow been moved to directories that are not global, you cannot
access the files you need to display and work with horizons.
(例子:
blade{owuser:/home/OpenWorks/conf}% more dir.dat
#/home1/OWPROJ global
/home4/OWPROJ global
blade{owuser:/home/OpenWorks/conf}% )
If dir.dat is not properly specified or your global area is not properly defined for the project, the horizons
will be marked as deleted in the horizon catalog (.hrz_cat). Correct the problem with dir.dat or the global
area, and then simply use the Global Manager to restore your horizons to the working project.
SeisWorks/3D
If you find some of your horizons missing, try rebuilding the horizon index file (.hrz) using the HrzUtil
utility. See the HrzUtil chapter of the Seismic Project Utilities manual for detailed procedures.
1. Exit SeisWorks/3D.
HrzUtil
3. When the HrzUtil dialog window appears, select the 3D radio button and click on List. From the popup
Project Selection dialog box, highlight your project and click OK.
A list of horizon names, ordered by horizon number, appears in the Horizon List selection box.
5. When the index has been rebuilt, the horizon list is refreshed.
You can have a total of five active horizons for all currently open Map or Perspective Views. Your horizon
selections apply to all currently open Map Views, Horizon Image Maps, and Perspective Views.
For example, suppose you select bluemax as the first display horizon in the Contents dialog box for Map
View 1. Then you select greenmin as the first display horizon in the Contents dialog box for Map View 2.
Your last selection will be applied to all the currently open views. If you redraw Map View 1, greenmin—
not bluemax—will be displayed there.
To avoid this problem, use the second horizon display field when you choose the horizon for your second
Map View, the third horizon display field when you choose the horizon for your third Map View, and so on.
Only faults that have been selected for display are listed in the Correlate dialog box. If a fault you want is
not there, close the dialog box. From the Map View or Seismic View menu bar, select Faults à
Select, and choose that fault for display. Then reopen the Correlate dialog box.
When you are correlating with fault heaves in Map View, you must click on the fault segment within that
heave. The fault heave, which represents the gap in the horizon, may be wider than the fault segment in
areal view. So when you click within the heave you may not actually be on the segment, as illustrated
below.(图略)
Fault as interpreted in Seismic View. Note that gap in horizon is wider than the area covered by the fault segment as drawn.
Fault as shown in Map View. Note that the width of the heave exceeds the width (areal extent) of the fault segment. When you
correlate, you must click on the segment.
If you click within the heave and get a beep, move closer to one side of the heave symbol and click again.
In a Map View, the Identify Faults option works only for faults that have been triangulated. Any change to
a fault segment or fault plane makes the existing triangulation of that plane obsolete.
If the triangulation is out of date when you try to identify faults, a message prompts you to retriangulate or
exit the identify faults mode.
To retriangulate, click on OK. The program retriangulates the fault plane and continues the search to
identify faults.
This message will also appear if only one fault segment has been assigned to the fault plane. To avoid
receiving the message, digitize another fault segment and apply it to the fault plane.
To avoid this irregularity, keep all segments for a given plane approximately the same length. (That is, digitize the full extent of the fault segment on
every section you interpret.)
Export to Z-MAP Plus creates temporary sorting files (tmp.*) in the project sys directory during an export
job. Your horizon may exceed the available capacity.
• Export the horizon dataset using the Computed Contours and Fault Polygons option on the Export to Z-
MAP Plus dialog box.
For a quick check of your 2D master project, use the contest2d utility.
This utility tests for continuity of 2D line data, horizon data, and seismic data.
It checks to see if
• each line has a a valid trace range(每条测线拥有有效道范围). That is, it checks that the minimum trace
is not 0, that the minimum trace number is smaller than the maximum trace number, and that the minimum
and maximum trace numbers are not the same.
• each line has the required navigational files(每条测线拥有所需的导航文件). These are the .st_glb file
that defines the shotpoint-to-trace relationship(炮道关系) and the .xy_glb file that contains shotpoint real-
world locations(炮点实际位置).
• every horizon data file (.hrd_glb) has the same trace range as defined in corresponding the line header file
(.lh_glb)(测线头文件).
As contest2d runs, it outputs to the screen a list of each line examined and the trace range of that line. The
utility also generates two files:
• a log file that lists every file examined, its file size, and its full path
• an error file that lists any discrepancies encountered during the check.
The log file is useful in compiling a database of the lines in your master project and in keeping track of the
size of your master project.
The error file may help you identify and resolve problems encountered in displaying seismic or horizon
data.
See the contest2d chapter of the Seismic Project Utilities manual for detailed procedures.
1. Set the environment variable LGC_MASTER to the master project you wish to examine by entering the
appropriate commands at the prompt:
export LGC_MASTER
contest2d <openworks project name> <contest log file > < error file >
Use whatever names you like for the log and error files. If you want to write them to a directory other than
the current directory, include the full path.
3. Examine the output on the screen, which will show you each line checked and its trace range.
4. Examine the log file and error file.
• Load a position log with more stations (depths) recorded along the well path.
• Load a directional survey (it will calculate TVD values using the radius of curvature method as the
default).
This message does not necessarily indicate a problem. When dealing with multiple occurrences of a field,
null occurrences can exist after the last data value. The loader cannot write a record with a required field set
to null, so it drops that record. Check the error log file to verify.
Try exiting and restarting SeisWorks. If that does not correct the problem, try one or more of the following:
• Make sure that the active OpenWorks project matches the SeisWorks definition.
The Well Status is not recognized by SeisWorks. Edit the status using the OpenWorks Well Data Manager.
You are missing one or both of the following: a Time/Depth Table, a Position Log.
3) Wells-Select-Synthetics. Also make sure that the synthetic exists over the time range displayed. Often,
synthetics have a time reference other
• Problems with Seismic Display on page 58. Contains solutions for common problems encountered while
displaying seismic data.
• Problems with Colors on page 59. Describes steps you can take to solve problems related to the allocation
of color for seismic displays.
• Other Display Problems in SeisWorks on page 60. Discusses solutions for problems with displaying
computed contours or wells in map displays.
No Seismic 无地震剖面显示
SeisWorks/2D
Did you select a vertical seismic (.2v2) file? Check the Seismic Parameters dialog box, and select a .2v2
file. (是否选上了 .2v2 文件)
SeisWorks/3D
If no seismic is displayed at all, you may need to select a vertical, bricked, or compressed seismic (.3dv, .
bri, .cmp) file. Check the Seismic Parameters dialog box, and select a seismic file. (是否选上了 .3dv, .
bri, .cmp 文件)
If you are trying to display a 16-bit or 32-bit file, and you have not scaled the file to 8 bits, you will receive
“snow” or stripes on the display.(显示16或32位文件时,没有按8位模式来显示)
See “Scaling and Clipping Seismic Data” in the chapter “Preparing Seismic Views” of the SeisWorks/3D
Data Display manual for information on how to scale seismic data.
Gaps or white spots may indicate problems in the way the data was acquired or processed. Another
possibility is that the data was not loaded correctly. If the problem is extensive, you may have to reload the
data. Check with your system administrator or data loader. Also, refer to the 2D Project Management, 3D
Project Management, 2D Batch Control Monitor, and 3D Batch Control Monitor manuals.
When you start SeisWorks, you are asked to indicate whether you want single or dual color bars on each
screen. If you get a message saying dual color bars cannot be allocated, you probably do not have enough
colors available. Remember other applications are also tapping the color resources.
In such a case, you can either run SeisWorks with a single color bar, or you can kill some other applications
and then try to start SeisWorks in the dual color bar mode.
If you display a horizon or mapping file in the Map View, and nothing appears, display the Color Control
dialog box of the screen where the problem is occurring.
The problem may be that the Mode option is set to Manual and the data is outside the range of the color
bar. If this is the case, set the Mode option to Local and redisplay the horizon or mapping file in the Map
View in question.
Color map files (.clm files) are automatically copied to the project sys directory when you create a working
project. Select FileàOpen in the Color Control dialog box to see whether you have color map files. If
none are listed in the resulting dialog box, someone has deleted them or moved them out of the system. To
restore them, copy the .clm files from $SEISUTILSHOME/dat to your project sys directory.
(例如单位上的机器:
.clm 默认存放位置在:/home/OpenWorks/SeisUtils/dat
2D工区的存放位置(包括自定义的颜色文件):/home/OWPROJ/hjq072d)
If the color bar is not picking up the minimum and maximum values properly, recompute extremes for the
horizon. In a Map View or Horizon Image Map, select Horizons à Computations àCompute
Extremes. Then set the color bar to the Local mode and redraw the Map View.
Be sure that in specifying the areal extent for the Compute Extremes computation, you select Entire
Survey. If Compute Extremes is run for a limited map area, the color bar will reset to the minimum and
maximum values computed for that small area only.
This section contains troubleshooting techniques for computed contours and well data in map displays.
The quality and accuracy of computed contours depends on the contouring parameters you have set. If you are
dissatisfied with their appearance, adjust the contour parameters and rerun the contouring job.
Contours appear inside the fault • Use the Edit Polygons option to delete the points inside
polygons. 等值线在断层多边形 the polygons.
内部
• If the contours are gridded, check the parameters you
set in Map It. If you selected Do not use polygons,
recalculate the gridding surface using the Use existing
faults option.
• Check the following in the Computed Contours
No annotation appears on Parameters dialog box (ContoursàParameters
Computed):
the contours. 等值线上无标注
• Computed Contour Annotation is turned on.
Frequently problems encountered while displaying wells are related to your parameter settings or your time-
depth tables. Use the following table to check that you have set the well display parameters properly for the type
of data you want to view.
Too many wells are posted. • Reset the Criterion Distance option in the
Seismic Well Parameters dialog box to a smaller
value.
• Troubleshooting System Problems on page 68(排查系统问题). This section contains solutions to a few
common Landmark system problems.
To check if OpenWorks processes are running, use the ps command with the -l option. For example:
ps -efl
(IBM, Solaris, or SGI)
To check on Oracle processes, use the su command to switch to the Oracle user account, then use the ps
command. For example:
su - oracle
ps -l
(IBM, Solaris, or SGI)
(例子:
blade{owuser:/home/blade/owuser}% su - oracle
blade% ps -l
blade% pwd
/home/oracle
blade% )
To check on a specific process, use the grep option with the name of the process or a fragment of the process
name. For example:
(单位机器上的例子:
The Pointing Dispatcher (pd) is started automatically through the Pointing Dispatcher Executor (PdEx)
daemon when Dynamic PD is turned on, which is the OpenWorks default setting. The Pointing Dispatcher
should be stopped only if you have a “dual environment”running multiple releases of OpenWorks
simultaneously. If you need to
run the stop_pd script, refer to “Configuring the Pointing Dispatcher”in the manual OpenWorks System
Administration: Managing the
System.
If you stop Oracle and do not reboot, you must restart Oracle before continuing to use OpenWorks. To restart
Oracle:
1. Use the su command to switch to the Oracle user account. For example:
su - oracle
dbstart
lsnrctl start
Oracle keeps the most recent database changes in a cache. The contents of this cache may be lost if you reboot
the system without stopping Oracle. Consequently, you should always stop Oracle first before rebooting the
system. To stop Oracle:
1. Use the su command to switch to the Oracle user account. For example:
su - oracle
dbshut
3. Stop the Listener process by entering the following command:
lsnrctl stop
Both dbshut and lsnrctl work only if the letter Y appears at the end of the
configuration setting in the file /etc/oratab. If these processes do not work, you can
control the database server from inside the Server Manager utility using the
appropriate commands. See the Oracle Server Manager User’s Guide for more
details.
su - root
$OWHOME/lam/bin/startlmgrd
This should only be run on the machine which is the LAM manager.
su - root
setenv OWHOME
OpenWorks_home_directory
$OWHOME/lam/bin/stoplmgrd
This should only be run on the machine which is the LAM manager.
When you start OpenWorks in a non-CDE environment using the startserver command, the following
processes are started: X, mwm, xsrm, viewer (FrameViewer), and launcher. When you start OpenWorks using
the startow command in an X window, the following
Some system files were modified during the OpenWorks installation. If there are problems, check to make sure
that the correct modifications are present in the system files. The script $OWHOME/bin/rc.ow is the shell script
that starts most required processes when the workstation boots. The script rc.ow is called at boot time by the
system file /etc/inittab (IBM) or /etc/rc2.d (SGI and Solaris). The rc.ow start-up call
Appropriate messages are displayed at the end of the boot stream if these files are set up properly. For example:
NOTE: $OWHOME is an environment variable defined in rc.ow. This variable is also defined in .lgcprofile or .
lgclogin, where it should be the same as in rc.ow.
Troubleshooting X 排查X
1. Echo the value of the environmental variable $OPENWINHOME. This specifies where X has been loaded
(echo $OPENWINHOME).
2. Verify that files exist in that directory. Compare the file listing with a machine that is operating correctly.
Solution: If there are missing files, the best solution is to reload the OpenWindows software from the
OpenWorks release media. Refer to the “Installing OpenWindows” booklet.
Check to see that all entries in the $HOME/.xinitrc file are valid.
Problems Starting SeisWorks SeisWorks起动问题
Below are solutions to some problems you might encounter in starting SeisWorks.
清理SeisWorks地震工区系统目录下无用文件的方法
Several files are created in the /tmp directory as you run SeisWorks. If these files become corrupted and are not
deleted when you reboot, you may have problems when you next attempt to open SeisWorks. To fix this
problem, look for the files in /tmp, delete them, exit SeisWorks, and then start SeisWorks again. You can safely
delete any of the following files. 当运行SeisWorks时,在/tmp目录下会生成一些文件。如果这些文件损坏
了并在重起机器时没被删掉,那么在打开SeisWorks可能会出现问题。为解决该问题,找到/tmp目录
里的这些文件并将其删除,退出SeisWorks,然后再重起SeisWorks。
.dirdat
.fs.lst
.plist.tmp
swild.ctr
upd.prj
During an interpretative session, SeisWorks creates certain temporary files and writes them to the project sys
directory. Under normal circumstances, these files are cleared when you exit SeisWorks. If they are not deleted,
you may find your sys directory becoming full. To remedy the situation, you can remove any of the following
file types. 在解释过程中,SeisWorks会生成一定类型的临时文件并将其写进地震工区系统目录中。在
正常情况下,当退出SeisWorks时这些文件会自动清除。如果没有清除,你会发现系统目录变得越来
越大(满了)。
我在单位机器上用以下设置(在用户下以root身份用vi建个文本文件dk,加进如下内容保存,然后chmod
555 dk。执行dk即可清除/tmp目录和地震工区目录下无用的文件。用同样的方法,也可把个人的Z-Map作图
目录加进来,删除诸如 .lck, .LCK, tmp.*, core 文件。如果能编个角本程序当每次退出SeisWorks时能自动运行
并清理垃圾文件,将是一个高效的方法。):
rm /tmp/*.dirdat
rm /tmp/*.fs.lst
rm /tmp/*.plist.tmp
rm /tmp/swild.ctr
rm /tmp/upd.prj
rm /tmp/*zycor.log
rm /home/OWPROJ/hjq2d/v834d2bc2*
rm /home/OWPROJ/hjq2d/v834d2bc2*.w3s
rm /home/OWPROJ/hjq2d/hzbf*.w*
rm /home/OWPROJ/hjq2d/tmp.*
rm /home/OWPROJ/hjq2d/core
rm /home4/OWPROJ/hjq072d/v834d2bc2*
rm /home4/OWPROJ/hjq072d/v834d2bc2*.w3s
rm /home4/OWPROJ/hjq072d/hzbf*.w*
rm /home4/OWPROJ/hjq072d/tmp.*
rm /home4/OWPROJ/hjq072d/core
If you install Oracle using the Landmark Oracle install procedure, the procedure automatically configures
Oracle to run with OpenWorks. However, if your site already has Oracle installed, or you are going to install
Oracle directly from Oracle-supplied media, you must verify that your installation meets Landmark
specifications.
• Before Using These Procedures on page 72. This section describes important information you should have
before troubleshooting Oracle.
• Documenting and Reading Error Messages on page 73. This section discusses the importance of recording
Oracle messages for use in troubleshooting.
• OpenWorks Requirements for Oracle on page 73. This section describes the settings and parameter values
required by OpenWorks for Oracle installations.
• The Environment Status Tool and Oracle on page 77. This section discusses the error messages that could
appear when using the Environment Status Tool to examine Oracle status.
• Using Server Manager to Query the Oracle Database on page 80. This section discusses the error messages
that could appear when using the Environment Status Tool to examine Oracle status.
• Using Server Manager to Query the Oracle Database on page 80. This section contains the procedure for
using Server Manager, a tool provided by Oracle for querying the database.
• Oracle in a Networked Environment on page 82. This section discusses important factors to consider when
troubleshooting Oracle in a networked environment.
• Troubleshooting Oracle Problems on page 85. This sections describes steps you can take to troubleshoot
common problems with Oracle.
The instructions in this chapter assume that OpenWorks has been installed successfully. Before reading the
chapter, you should be familiar with the following environmental variables.
Refer to the OpenWorks System Administration manual set for a description of these terms as well as for a
complete description of the OpenWorks environment.
In addition, you should be familiar with the OW_ADMINISTRATOR role that provides additional security for
OpenWorks projects. For a complete description of this role and the OpenWorks 2003 security model, see the
OpenWorks Project Management manual.
Error messages prefixed by ORA come from the Oracle database directly or through the application system.
You have a simple facility available that can help identify the type of error. Enter the oerr command with the
message number, as follows. For example, if the
The complete message is displayed below the command line for reference. This rarely provides a complete
answer or solution but can provide quick hints to solving the problem. If you need more help, you can check
your Oracle documentation for documented error messages, or call for help. If you call, be prepared to explain
the events leading up to the problem. You may also want to check your log file to find any previous errors that
may have led to your current problems.
If you install Oracle using the procedures described in the OpenWorks Installation Procedures document,
including using the pre-Oracle process, all the parameter settings described in this section should already have
been configured to interact with Landmark applications.
If Landmark media is not the source of your Oracle database, please follow the recommendations in this section.
Resource Recommended
maxinstances 1
maxlogfiles 40
maxdatafiles 254
maxlogmembers 5
Default datafile sizes provided by Oracle are inadequate for Landmark applications. The required datafile sizes
are as follows:
a. Oracle appends the ORACLE_SID to the filename. In the example, the ORACLE_SID is owminnie, where minnie is the server
name.
For safety purposes Landmark strongly recommends mirroring Oracle Log files on separate disks. However, not
having mirrored Log files will not affect the functioning of the Landmark applications.
The sizes shown above for system and rollback tablespaces may be insufficient if your site experiences any of the
following conditions:
System Tablespace
Each OpenWorks project will take from 3 to 5 Megabytes of space in the system tablespace.
Rollback Tablespace
You may find that you wish to increase the size of your rollback tablespace if you encounter problems in doing
the following:
• Doing project backups while users are working in the very large projects.
• Doing backups for projects that have a very large number of wells (30,000 or more).
Oracle sets a default block size of 2 Kilobytes. Set the parameter in the instance configuration file config.ora to
the following.
db_block_size = 8192
Oracle Parameters
Landmark applications have a few requirements about values of certain Oracle parameters. The following lines
must appear in the instance initialization file, commonly known as the init{ORACLE__SID}.ora file.
The db_files and max_enabled_roles parameters can have the given values or larger values.
compatible=8.1.7.1
os_authent_prefix=""
remote_os_authent=true
#NLS_DATE_******="YYYY-MM-DD HH24:MI:SS"
db_files=254
max_enabled_roles=48
shared_pool_size=9000000
db_block_buffers=3200
The following lines are recommended for performance reasons (the job_queue items are required for
OpenExplorer Advanced Project Management):
pre_page_sga = true
ccf_io_size = 131072
sort_area_size = 524288
#small_table_threshold = 20
open_cursors = 400
log_buffer = 1048576
max_dump_file_size=10240
dml_locks=500
job_queue_processes=2
job_queue_interval=60
After making the changes described above, you must shut down the database and restart it for the changes to
take effect. After the Oracle instance has been restarted, please ensure that the OpenWorks-supplied database
setup script is run by the Oracle DBA user. This script creates the tablespaces and Oracle users required by the
OpenWorks database,
The listener process must be to running before the setup script is run.
To start the listener process, as the Unix Oracle DBA user, type:
lsnrctl start
To run the database setup script, as Unix Oracle DBA user, type:
$OWHOME/install/owdbsetup
Please have your site DBA run the Oracle supplied script utlmontr.sql as the Oracle user SYS.
错误信息显示窗口上显示为:
ii) the current user is added as a valid Oracle user to the database
There are three possibilities, summarized in the message box and listed below.
• The Oracle instance is not running on the machine where the Environment Status Tool is being invoked.
This can typically happen in a client-server environment where the user is running the Environment Status Tool
on the Oracle client. The tool needs to run on the Oracle server.
• The Unix user running this tool is not a known user to the Oracle instance that is being queried. (The one
that is defined by the ORACLE_SID environment variable.)
OpenWorks provides a script that simplifies this process. To run the script login to the Oracle DBA account on
the machine where Oracle is running, and type:
$OWHOME/bin/orauser
Proceed to add the current Unix user as an externally identified Oracle user. Selecting all the defaults provided
by the script will do the necessary steps.
This process is typically done when a Unix user is created by the lgcuser script provided by OpenWorks to add a
new user or update an existing user.
• The instance configuration file, typically called $ORACLE_HOME/dbs/config.ora should be readable by all.
Some Oracle installations make this file read protected. The Environment Status Tool requires this file to be
readable by the Unix user running the tool.
If the Oracle database can not find your OpenWorks project directories, the following message appears.
错误信息显示窗口上显示为:
Please ask your DBA to run the script $OWHOME/bin/dboradir and add project
locations.
OK
OpenWorks requires project locations to be known to the Oracle database. Project locations are directories
where the OpenWorks software will create database files associated with OpenWorks projects.
These locations are added when the script dboradir is run. If Oracle has been installed using the Landmark-
supplied owinstall format, this will automatically be done for you. Otherwise the Landmark-supplied script
owdbsetup needs to be run on the machine where the Oracle database is installed by the Unix Oracle DBA user.
If no project directory locations are specified, the default location of $ORACLE_HOME/dbs is
assumed.
Could not find the Oracle Database Log Files 找不到Oracle Database Log文件
If the Oracle role MONITORER has not been created, the following message appears.
错误信息显示窗口上显示为:
ii) grant role MONITORER to the current user running the Status Tool.
OK
For the Environment Status Tool to correctly diagnose the Oracle configuration, the user running the tool
should have the Role MONITORER granted. Once again if the installation is a standard Landmark installation,
this is already done for you. If this is not a standard Landmark installation, the role MONITORER first needs to
be created for this particular Oracle installation.
Please have your Site DBA run the Oracle-supplied script utlmontr.sql as the Oracle user SYS. Once that is done
have the DBA assign the role to the Unix user running the Environment Status Tool. The utlmontr.sql script is
found in the $ORACLE_HOME/rdbms/admin directory.
• owsys
• owsysp
• lmsys
The users’ owsys and owsysp have tablespaces owsys and owsysp associated with them. Use the following
procedures to check whether the users and tablespaces exist and are set up correctly.
Login as the Unix Oracle DBA user, then type the following:
svrmgrl
connect internal
The next query verifies the existence of the tablespaces OWSYS and OWSYSP. Type this command:
This query lists all the tablespaces known to the current Oracle instance, the status of these tablespaces, and the
data files associated with each tablespace. Your screen listing should be similar to the following output:
------------------------------------------------------
7 rows selected.
The preceding list shows that the tablespaces OWSYS and OWSYSP exist and are available. It also verifies that
the data file associated with the tablespace physically exists on the system. If you find that the OWSYS and
OWSYSP tablespaces do not exist, run the OpenWorks script owdbsetup as the Unix Oracle DBA user.
If the tablespaces OWSYS and OWSYSP exist but their status is OFFLINE or INVALID, please have the site
DBA make them AVAILABLE or call your Landmark representative for assistance.
exit;
In addition to the basic roles described here, the OW_ADMINISTRATOR role that
provides additional security for OpenWorks projects. For a complete description of
this role and the OpenWorks 2003 security model, see the OpenWorks Project
Management manual, OpenWorks Security Model chapter.
以下是单位机器上的操作实例:
blade{owuser:/home/blade/owuser}% su – oracle 回车
Sun Microsystems Inc. SunOS 5.8 Generic Patch October 2001
blade% svrmgrl 回车
JH USERS TEMP
20 rows selected.
12 rows selected.
SVRMGR> exit 回车
• peer-to-peer configuration(对等网配置). This means that two or more Oracle instances, on separate or
same machines, each having stand-alone capabilities, are set up to communicate with each other.
NFS mounting Oracle binaries from an NFS server, and accessing an instance on a remote machine through
SQL*Net. An Oracle instance is not present on the client machine.
This section provides a brief description of the most common pitfalls and problems encountered in a networked
environment.
Troubleshooting client server, and exploring SQL*Net in detail is beyond the scope of this manual. Please refer
to the SQL*Net manual for further information.
The files listener.ora and tnsnames.ora are important for a networked Oracle environment. These files can be
found in the directory:
The listener process is a daemon process that runs on a machine which wants to accept connections over the
network from remote machines.
There is just one listener process running on a machine, even if there are multiple Oracle instances on the
machine.
The listener process has a configuration file associated with it. The configuration file, called the listener.ora file,
has information about all the instances on the local machine that are willing to accept networked connections,
and are willing to be serviced by the listener process. The following is a sample listener.ora file.
LISTENER=
(ADDRESS_LIST=
(ADDRESS=
(PROTOCOL=tcp)
(PORT=1521)
(HOST=minnie)
(ADDRESS=
(PROTOCOL=IPC)
(KEY=owminnie)
SID_LIST_LISTENER=
(SID_DESC=
(SID_NAME=owminnie)
(ORACLE_HOME=/export/home4/test/oracle)
The sample file services one instance, owminnie, on the host machine minnie. It accepts TCP and IPC
connections for the instance. The listener process listens on the reserved port number 1521 for incoming TCP
connections. The ORACLE_HOME variable associated with the instance owminnie is /export/home4/test/
oracle.
The installation process creates a listener.ora file for the instance you have installed.
单位机器上的listener.ora:
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS_LIST =
(DESCRIPTION =
(PROTOCOL_STACK =
(PRESENTATION = GIOP)
(SESSION = RAW)
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /home/oracle/OraHome1)
(PROGRAM = extproc)
(SID_DESC =
(GLOBAL_DBNAME = owblade)
(ORACLE_HOME = /home/oracle/OraHome1)
(SID_NAME = owblade)
blade{owuser:/home/oracle/OraHome1/network/admin}%
The tnsnames.ora file is a list of all the instances on the network that are available to the current instance,
including itself. The remote instances still reserve the right to restrict the current instance from connecting. A
sample tnsnames.ora file is as follows:
owminnie=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=minnie)
(PORT=1521)
(CONNECT_DATA=
(SID=owminnie)
owrocky=
(DESCRIPTION=
(ADDRESS=
(PROTOCOL=tcp)
(HOST=rocky)
(PORT=1521)
(CONNECT_DATA=
(SID=owrocky)
单位机器上的实例:
blade{owuser:/home/oracle/OraHome1/network/admin}% m tnsnames.ora
OWBLADE =
(DESCRIPTION =
(ADDRESS_LIST =
(CONNECT_DATA =
(SERVICE_NAME = owblade)
EXTPROC_CONNECTION_DATA.COM =
(DESCRIPTION =
(ADDRESS_LIST =
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
blade{owuser:/home/oracle/OraHome1/network/admin}%
With this tnsnames.ora the instance can connect to the instance owminnie, on the host minnie via the TCP
protocol. It can also connect to the instance owrocky on the host rocky via the TCP protocol. It is assumed that
the listener process is running on both those hosts and it listens on port 1521.
The tnsnames.ora file that is shipped with Oracle must be edited to work properly in an OpenWorks
environment. For example, formatting issues and the use of lower case letters in the file must be corrected so
that OpenWorks daemons will run.
Edit $ORACLE_HOME/network/admin/tnsnames.ora and make sure that the following words are all upper
case(保证为大写字母):
CONNECT_DATA, SID
$OWHOME/bin/owlistsids $ORACLE_HOME/network/admin/tnsnames.ora
Two values should be returned; the first is the ORACLE_SID, and the second is the host name. For example,
Owminnie minnie
单位机器上的的例子:
blade{owuser:/home/oracle/OraHome1/network/admin}% $OWHOME/bin/
owlistsids $ORACLE_HOME/network/admin/tnsnames.ora 回车
blade{owuser:/home/oracle/OraHome1/network/admin}%
If you suspect a problem with the Oracle database, you should check to make sure all processes are running.
Oracle has six essential database processes that must be running before you can access a database.
Process Name Purpose
Database Writer ora_dbwr_<SID> Performs all writes from the database cache in
memory to the database files on disk. Writes only
把内存中的数据库缓 occur when more data needs to be read into the
存写成磁盘数据库文 SGA and there is too little free space in the
件 database buffers.
Log Writer ora_lgwr_<SID> Performs all writes from the redo log buffers in
memory to the log files on disk. As transactions
把内存中的redo log commit, this process writes redo log entries into
写成磁盘log文件 an on-line redo log file.
These processes are started when the workstation is booted and should remain running until the workstation is
halted. Use the following command to verify that Oracle processes are running:
This command should display the following entries. (If you are running a client-only workstation, there are no
Oracle processes running on your workstation. Be sure Oracle is running on your server.)
If some of the processes are not running, restart the Oracle database server. To restart Oracle, exit from all
application programs and execute the following commands:
su - oracle
dbstart
lsnrctl start
If an error occurs during startup, it is displayed on the screen and logged in the file $ORACLE_HOME/rdbms/
log/alert_sid.log. If necessary, refer to the Oracle documentation for more detailed descriptions of log files and
error messages. The error message should indicate which processes did not start.
单位机器上的实例(该log文件会变得越来越大,可以人为将其减小):
blade{owuser:/home/oracle/OraHome1/rdbms/log}% ls
blade{owuser:/home/oracle/OraHome1/rdbms/log}%
Unable to Connect to a Local Database 连不上本地数据库
Connecting to a local database requires that the Oracle processes are running (refer to the section “Database
Processes May Not Be Running” on page 85 for more information) and that you have authorization to access
the database. The utility program orauser lets
you provide user access to Oracle. For more details see the Manging the System manual and the OpenWorks
installation procedures.
Connecting to a remote database requires that the Oracle processes are running on the local and the remote
workstation and that you have permission to access the remote database. For information on database processes,
see “Database Processes May Not Be Running” on page 85.
For more details see the Manging the System manual and the OpenWorks installation procedures.
The Oracle command dbshut is used to halt all Oracle processes before rebooting the workstation. You must
exit from all application programs before running this command. The dbshut command will not shutdown the
database if applications are still connected.(执行dbshut之前,要关闭OpenWorks应用程序)
In many cases the shutdown normal and even the shutdown immediate commands will hang up the system. At
this point you have two options.
• Identify the processes connected to the system that are causing the hangup.
Identifying the current processes will have to be done through Server Manager, since no further standard
connection can occur during a shutdown. Breaking the process can work, but usually this results in the need for
a shutdown abort shortly after. The key is to make sure all connections are cleared before shutdown. If you do
not have that luxury, a shutdown immediate is worth trying. As a last resort, the abort command may be
unavoidable.
You may want to review the $ORACLE_HOME/rdbms/log/alter*.log files and any *_PID.trc files to see if
information has been written recently. Background processes can die or fail and the database writes these results
to the log and trace files. If these trace files do not provide immediate clues, a shutdown abort must be
performed. You have the
option of calling for support prior to shutting down, but it depends on your immediate needs.
Once the shutdown abort completes, immediately try to restart the system before doing any maintenance work,
unless you know it is absolutely necessary. If maintenance was scheduled, you can start with more confidence
after a clean shutdown.
Usually, you only have to start the database if you have been forced to shut down or if the system requires
maintenance. This introduces a wide variety of problems of different severity. Once again the key is reviewing
the trace and log files to see if anything out of the ordinary has occurred during the last shutdown or during
system maintenance.(查看log文件,以确定问题出在何处)
implies that the files listed in the control file cannot be accessed by the database during startup. If you do not
have the list of all files located within the database, you should start Server Manager using svrmgrl and issue the
connect internal command. Then spool the results from querying v$datafile and v$logfile with the database
startup mount command completed. These internal tables give you a full listing of the files used by the control
file (except for the control files themselves, which are listed in the config.ora file).
A file may have been moved, renamed, or deleted during standard operation or during shutdown. Most of these
cases can be corrected, but the file in question must be identified. Make sure that all of these files exist. If they do
not, you must carefully evaluate what has happened to the file in question. This is critical to your ability to
recover your current database without being trapped into recovering from the last week’s backup.
If any of the files were moved during the operation of the database, you have an even chance to recover the
current system without corruption.
If they were moved while the database was being shutdown, recovery is almost certain.
There are two key factors to recovering your database in these cases.
• Has the system been changed since the file was moved?
If the first case applies, this problem is beyond the scope of the current troubleshooting procedures, but can be
handled using Oracle techniques documented in the Oracle8 Server Administrator’s Guide.
If the second case applies, consider your situation carefully before proceeding:
1. Try to copy the most recent version of the datafile to the location required.
2. If the startup fails again, decide if the data is required to continue all other operations. Unfortunately if it is the
****** or RBS tablespace data files, you must return to your cold backup. If any other datafile is in question you
can simply drop the datafile before
3. If you choose to drop the object before the database starts up, you are committing to the current database and
leaving all data and work associated with that file behind. Once the database is running, you can then re-create
the file if needed. The statements
required to perform this operation are clearly documented in the Understanding Oracle Guide.
Typically, unless the environment has very tight security, a user will drop a table or remove all the rows from it.
In many cases this situation is unrecoverable. However, if the object was from the project tablespace, you can
recover the tablespace objects and data using the recover project function in the application. An export file is the
only
While running an application, your process may pause, hang or fail with or without error messages. In most
cases, the failure of your process has resulted from a connection failure mentioned above.
However some other process limits may have caused the problem. You may see error messages such as:
tablespace ‘name’
These types of errors all stem from the resource availability within the Oracle database. In most cases where
resources are concerned, the user’s process will fail and the error message will be returned.
At this stage, you must assume that if you try the same process the same results will occur. Document the error
and then try the same process if the event was not very time-consuming. If you receive a consistent result you
should report the object in question to technical support for specific instructions on correcting the resources to
allow completion of the transaction.
There are many reasons these errors can occur but the checklist below is the quickest path to determining the
problem. With each item in the list there is a brief description of the tasks required to complete the checklist. If
you need more detail please refer to the Open Works System Administration Guide.
• Check your environment variables(检查环境变量). Oracle software and your access to it depend heavily
on the variables ORACLE_SID, ORACLE_HOME, and LD_LIBRARY_PATH to locate the software and
libraries required for Oracle products and applications. There are others for your particular application but
without these properly set, you cannot use the database.
• Check for database activity(检查数据库活动性). Log on using the Oracle account and use the following
command to check for background processes.
You can confirm by logging into SQL*Plus directly using the following command:
sqlplus system/password
If the database is not running, review the log files in $ORACLE_HOME/rdbms/log/alter*.log to determine if
there were any problems with the database. Restart the system using the following commands to initialize the
Oracle background processes.
svrmgrl
connect internal
startup
• Check for network processes(检查网络进程). Log on to your workstation as oracle and verify that the
Listener process for SQL*Net is active.
This is an Oracle background process that connects users to the database. You can use the following command
to confirm the process is active.
lsnrctl stat
You can also confirm by connecting directly to the database. For example:
sqlplus system/password@ownova
If the network listener is not active, use the following command to activate the process.
lsnrctl start
• Check Oracle privileges for the user account(检查用户的Oracle权限). Each user account must have
sufficient privileges to connect to and access the database. To confirm this, use the following command:
sqlplus system/password
then review the information in the DBA_ROLE_PRIVS table to determine that the user has connect and
resource privileges. If not you can alter the user by entering the following SQL command:
To insure that you see relevant error messages, keep both the console window and the main menu of the
application you are using open and visible as you work.
• Setting the Error Level on page 94(设置错误级别). This section describes the OpenWorks error
reporting system, which you can use to determine the causes of system problems.
• Using the OpenWorks Error Logger on page 99(使用错误信息日志). This section contains the
procedure for setting the error level using the OpenWorks Error Logger utility.
1 Warnings.
The default setting is Error Level 3. Error Level 0 may provide too much information to be helpful.
For example, if you are having problems with SeisWorks/3D, you might lower the error level within an xterm
window, start SeisWorks/ 3D from that window, and repeat the sequence of steps that caused the problem in
your original session. This time, more detailed diagnostic information will be posted in the xterm window.
lgc_getenv ERR_LEVEL
For most diagnostic purposes, an error level of 2 provides sufficient information. The required commands are
slightly different if you are working in a Bourne shell or a C shell. The following examples show changing the
error level to diagnose SeisWorks problems.
In a Bourne Shell
ERR_LEVEL=2
export ERR_LEVEL
or
In a C Shell
setenv ERR_LEVEL 2
or
If you wish to change the error level setting for all applications, you must edit the file
containing the ERR_LEVEL variable. See WHERE for instructions.
How you start the application influences where error messages are posted.
When you start Landmark applications from the OpenWorks Command Menu, error messages are written to
the “run” directory. Typically run resides in your home directory.
Each application has its own “.err” file in the run directory. To see the error messages for SeisWorks, perform
the following steps:
cd
cd run
or
3. To display and continually update the error file as you work, type
or
This method records the error messages to a file you specify with the “script” command, as follows:
export ERR_LEVEL
or
script <myerrorfile>
3. Start your application in the same xterm using its executable name.
You can find these names in the launcher.dat or swlauncher.dat file, for instance. Each executable command
appears in the column after the application’s name; use only the first word. For example:
or
more <myerrorfile>
As the application runs, any errors display in the xterm and a copy is sent to the file. In addition, you can type
annotations of your workflow in the xterm, and this is also saved. When you finish running the application, exit
from the application menu. Then, in the xterm window type “exit” to exit from the script file.
Bourne Shell:
or
C Shell:
or
more <filename>
2. Select the OpenWorks utility or application from the list on the left.
3. Click on the radio button for the Error Level you wish to use while running this application.
4. In the field labeled Error Log File, enter the full pathname of the file where you want the error messages
placed.
Error levels are same for the Error Logger and the keyboard.
The error levels used by the OpenWorks Error Logger are identical to those you
enter from the keyboard. 错误记录器上设置的错误级别与从键盘上设置的
级别是一致的。
Solution: Check that the Oracle server is running. If it is not, restart the server by logging into the Oracle server
and issuing the following commands:
dbshut
dbstart
Cause: Your system is a client that is not mounted to the Oracle server.
echo $OWSYSSID
This variable identifies the host ID of the server where Oracle database is installed. Note that, by Landmark
convention, the OWSYSSID specification often includes an “ow” prefix. For example, if OWSYSSID is
specified as “owjazzman,” the actual host ID is “jazzman.”
Use the df command to determine whether your system is mounted to the Oracle server.
echo $OWSYSSID
If this variable is not set to the host ID of the system where Oracle is installed, use vi to edit the appropriate file.
Prefix the two letters “ow” to the hostname. Then exit from X, log out, and log back in.
echo $ORACLE_HOME
in an xterm window or by checking the Environment Status Tool.
实例:
/home/oracle/OraHome1
blade{owuser:/home/blade/owuser}%
If this variable is not set to the directory where the Oracle database has been installed, use vi to edit the
appropriate Unix initialization file. Then exit from X, log out, and log back in.
Cause: You cannot reach the Oracle server because of a network problem.
Solution: Check with your system administrator to see if you have a network problem.
Solution: Check the System Configuration panel of the Environment Status Tool to see if ORACLE_SID is set
to the proper instance ID. (See “Tools for Troubleshooting” on page 17.)
Cause: You are trying to use the Database Sanity Checker to query the database instance configuration file from
a client.
Solution: The database instance configuration file can not be queried from a client. If you want to check the
setup of the Oracle server, you must do so from the server itself.
Solution: Check the System Configuration panel of the Environment Status Tool to see if the ORACLE_SID is
set to the proper Oracle server ID. If it is not, reset it in the appropriate Unix configuration file. (See “Tools for
Troubleshooting” on page 17.)
Cause: Your database instance configuration file does not have read permission. (Relevant only if your system is
an Oracle server.)
Solution: Generally, the database instance configuration file is called $ORACLE_HOME/dbs/config.ora. This
file should be readable by all. If the file does not currently have read permission, have your Oracle database
administrator change it so that it does.
Solution: Ensure that your seismic project is associated with an OpenWorks project.
You receive a list of all currently available SeisWorks projects and their corresponding OpenWorks projects.
3. If plist does not show a project associated with your seismic project, use the Seismic Project Associate utility
(available from the Seismic Project Manager’s Project menu) to associate an OpenWorks project with your
seismic project.
SeisWorks/2D users can find more information in the “Master Projects” and “Working Projects” chapters
of the SeisWorks/2D Project Management manual. SeisWorks/3D users should refer to the “3D Projects”
chapter of SeisWorks/3D Project Management.
echo $OWSYSSID
If this variable is not set to the host ID of the system where Oracle is installed, use vi to edit the appropriate file.
Prefix the two letters “ow” to the hostname. Then exit from X, log out, and log back in.
Solution: Have a user with MANAGE authority and the OW_ADMINISTRATOR role grant confer the same
authority and role to your account.
Cause: The working project has been modified without updating the seismic map (.sm) files工作工区已更新,
但未更新地震图(.sm)文件.
1. Exit SeisWorks.
update2d <projectname>
3. Reopen SeisWorks.
(注:该错误常见到。以后可按此法解决之。)
Cause: The application cannot open the project definition file (.ps2) for some reason.
Solution: Check permissions on the project definition file (.ps2), and change them to read-write if necessary.
(实例:
Cause: The application cannot find your project sys directory, and the project definition file (.ps2) resides there.
Solution: Check that dir.dat has been defined correctly. The location of this file is defined by $OW_PMPATH,
which is usually set to the directory $OWHOME/conf. However, if your system is running as a client or has
been modified at your site, dir.dat may be in $OW_DDF.
Solution: Check permissions on the project definition file (.pds). Change them to read-write if necessary.
Cause: The application cannot find your project sys directory, and the project definition file (.pds) resides there.
Solution: Check that dir.dat has been defined correctly. This file usually resides in the $OW_PMPATH which is
often $OWHOME/conf. However, if your system is running as a client or has been customized, dir.dat may be
defined by $OW_DDF.
Solution: Check that the environmental variable SEIS_DPATH is set. See VARIABLES for information on
variables.
Solution: Select the project first, then open a new or existing session.
Cause: Someone has deleted the selected project from your system.
Solution: Restore the project using the SeisWorks Backup/Restore utility, or copy the project directories from
another system onto yours.(这是典型的工区恢复方法)
Cause: The project as defined by master grid does not encompass the location or extent of your horizons.
Solution: Delete the horizon index file (.hrz)(层位索引文件) and recreate it using the HrzUtil utility. If this
does not solve the problem, call Landmark Customer Support.
Cause: In trying to correlate faults, you selected a fault plane name without first selecting a fault segment or
heave.
Solution: Select a fault segment or heave, then select the fault plane you want to assign it to.
Cause: The SEIS_DPATH environmental variable has not been properly set.
Give the absolute path for OWHOME. (Generally, lgcenv.cf is located in $OWHOME/conf.) (例:在
$OWHOME/conf 中,设置:SEIS_DPATH /home/OpenWorks/SeisUtils/dat )
Cause: This often happens when you add a disk and create a directory with root permissions.
Solution: To give all users full access to all project directories, perform the following steps:
su
The above instructions assume, of course, that all your project directories begin with the letter p (/pa, /pb, /pc,
etc.).
If this is not the case, use the appropriate combination of letters and wildcards to include all the project
directories when you change the permissions.