山定子 注释
OpenWorks Software ®
Installation Procedures
© 2008 Landmark Graphics Corporation
Trademark Notice
3D Drill View, 3D Drill View KM, 3DFS, 3D Surveillance, 3DView, Active Field Surveillance, Active Reservoir Surveillance, ADC,
Advanced Data Transfer, ARIES, ARIES DecisionSuite, AssetConnect, Asset Decision Solution, Asset Development Center, Asset
Journal, AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, Asset
Performance, AssetPlanner, AssetSolver, AssetSolver Online, AssetView, BLITZPAK, CasingSeat, COMPASS, Corporate Data Archiver,
Corporate Data Store, Data Analyzer, DataManager, DataStar, DBPlot, DecisionSpace, DecisionsSpace 3D Drill View KM, DecisionSpace
AssetLink, DecisionSpace AssetPlanner, DecisionSpace AssetSolver, DecisionSpace AssetView 2D, DecisionSpace AssetView 3D,
DecisionSpace Atomic Meshing, DecisionSpace Decision Management Systems(DMS), DecisionSpace for Production, DecisionSpace
Nexus, DecisionSpace PowerGrid, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir, DecisionSpace
TracPlanner, DecisionSpace Well Seismic Fusion, DecisionSpace WellSolver, DecisionSuite, DepthTeam, DepthTeam Explorer,
DepthTeam Express, DepthTeam Extreme, DepthTeam Interpreter, Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS,
Discovery, Discovery Asset, Discovery PowerStation, DMS, Drillability Suite, Drilling Desktop, DrillModel, Drill-to-the-Earth Model,
DSS, Dynamic Reservoir Management, Dynamic Surveillance System, EarthCube, EDM, EDT, eLandmark, Engineer’s Data Model,
Engincoeer's Desktop, Engineer’s Link, ESP, Event Similarity Prediction, Executive Assistant, ezFault, ezSurface, ezTracker, FastTrack,
FG+, FieldPlan, Field Scenario Planner, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix Exploration System, GeoLink,
GeoProbe, GeoProbe GF DataServer, GES, GESXplorer, GMAplus, GMI Imager, GRIDGENR, Handheld Field Operator, HHFO, I2
Enterprise, iDIMS, IsoMap, iWellFile, Landmark, Landmark Decision Center, Landmark & Design, Landmark Logo and Design,
Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Magic Earth, MagicDesk, Make Great Decisions, MathPack,
MIMIC, MIMIC+, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks, Open Explorer, OpenJournal, OpenSGM, OpenVision,
OpenWells, OpenWire, OpenWorks, OpenWorks Development Kit, OpenWorks Well File, OpenWorks Production, PAL, Parallel-VIP,
PetroBank, PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding
Plus, Pointing Dispatcher, PostStack, PostStack ESP, PostStack Family, PowerCalculator, PowerExplorer, PowerExplorer Connect,
PowerGrid, PowerHub, Power Interpretation, PowerJournal, PowerModel, PowerView, PrecisionTarget, Presgraf, PRIZM, Production
Asset Manager, PROFILE, Project Administrator, ProMAGIC, ProMAGIC Connect, ProMAGIC Server, ProMAX, ProMAX 2D,
ProMAX 3D, ProMAX 3DPSDM, ProMAX 4D, ProMAX Family, ProMAX MVA, ProMAX VSP, pSTAx, Query Builder, Quick, Quick+,
QUICKDIF, QuickWell, QuickWell+, QUIKDIG, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom,
Real Time Asset Management Center, Real Time Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real
Time Surveillance, Real-Time View, Reference Data Manager, RESev, ResMap, RightTime, RTOC, SCAN, SeisCube, SeisMap,
SeisModel, SeisSpace, SeisVision, SeisWell, SeisWorks, SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks
PowerJournal, SeisWorks PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect,
SimConvert, SimDataStudio,SimResults, SimResults+, SimResults+3D, SIVA, SIVA+, smartSECTION, Spatializer, SpecDecomp,
StrataAmp, StrataMap, StrataModel, StrataSim, StratWorks, StrataWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf &
Connect, SynTool, SystemStart, SystemStart for Clients, SystemStart for Servers, SystemStart for Storage, Tanks & Tubes, TDQ, Team
Workspace, TERAS, The Engineer’s Desktop, Total Drilling Performance, TOW/cs, TOW/cs Revenue Interface, TracPlanner, Trend Form
Gridding, Turbo Synthetics, VESPA, VESPA+, VIP, VIP-COMP, VIP-CORE, VIPDataStudio, VIP-DUAL, VIP-ENCORE, VIP-
EXECUTIVE, VIP-Local Grid Refinement, VIP-THERM, WavX, Web Editor, Wellbase, Wellbore Planner, Wellbore Planner Connect,
WELLCAT, WELLPLAN, Well Seismic Fusion, WellSolver, WellXchange, WOW, Xsection, You're in Control. Experience the difference,
ZAP!, and Z-MAP Plus are trademarks, registered trademarks or service marks of Landmark Graphics Corporation.
All other trademarks, service marks and product or service names are the trademarks or names of their respective owners.
Note
The information contained in this document is subject to change without notice and should not be construed as a commitment by Landmark Graphics
Corporation. Landmark Graphics Corporation assumes no responsibility for any error that may appear in this manual. Some states or jurisdictions
do not allow disclaimer of expressed or implied warranties in certain transactions; therefore, this statement may not apply to you.
Third Party Code
Landmark acknowledges that certain third party code has been bundled with, or embedded in, Landmark’s software. The licensors of this
third party code, and the terms and conditions of their respective licenses, may be found at the following location:
%OWHOME%\docs\third_party.pdf Windows
Landmark OpenWorks® Software Installation Procedures
Contents
Contents
Introduction
Licensing ........................................................................................................................................ 5
Quick Start
Oracle Installation
OpenWorks Installation
Post-Installation
Overview ...................................................................................................................................... 93
Linux & Solaris Servers and Clients: Run owsetup Script .............................................. 95
Windows ...................................................................................................................................... 99
Windows Servers and Clients: Oracle Wallet and Multiple Users .................................. 99
GeoDataLoad Installation
Check Software Packages (RPMs) on Linux 32-bit Servers and Clients ...................... 129
Set Shell Limits for the Oracle User on Linux 32-bit Servers ....................................... 131
Check Software Packages (RPMs) on Linux 64-bit Servers and Clients ...................... 134
Set Shell Limits for the Oracle User on Linux 64-bit Servers ....................................... 137
Appendix: Troubleshooting
Linux: Opening Acrobat Files in the Nautilus File Manager ........................................ 156
Linux: Running Acrobat Reader from the Gnome Panel .............................................. 157
Changing a Process Resource Limit with ulimit (or limit) .............................. 160
Introduction
引 言
This guide will help you install and configure the serer and client of Oracle 10g version 10.2.0.3.0
and OpenWorks on the following operating systems:
Use the instructions in “Quick Start” on page 7 to install on all of these platforms.
All Landmark Release 5000.0.0 applications require the OpenWorks 5000.0.0 version of the data
model. The basic steps to move data from previous releases of OpenWorks to Release 5000.0.0
are:
• If necessary, back up the projects with the backup function of the OpenWorks R2003.x
Project Administration utility.
• Install Oracle 10g and the Oracle patches required for the operating system.
• Restore 2003.x projects with the restore function of the Project Administration utility.
• Upgrade projects to the Release 5000.0.0 database schema with the upgrade function of
the Project Administration utility.
An upgrade in-place method is not available in OpenWorks 5000.0.0; however, “Appendix: Full
Oracle Instance Upgrade” on page 109 contains a procedure for moving your data to a new Oracle
instance.
Use the Upgrade function of Project Administration to upgrade a project database of any version
since OpenWorks R1998 to the current version of the OW_SYS schema in the OpenWorks
database. A project may need to be upgraded after the project has been restored from a backup or
after OpenWorks (and its database schema) have been upgraded. For example, after a project is
restored, you may see a version number after the project name, indicating that the project must be
upgraded before its data can be accessed.
The upgrade procedures available for a project depend upon whether the project database also
contains SeisWorks data. If the project database contains no SeisWorks data, the only procedure
the Upgrade function will perform is upgrading the project database itself. However, if it contains
SeisWorks data, and depending on the available SeisWorks data, the Upgrade function can
migrate 2D Master project and 3D project data, upgrade 2D Working project data, and create
interpretation projects from each SeisWorks project contained in the SeisWorks data.
For general information about OpenWorks projects, refer to the OpenWorks Project Management
manual (owpm_management.pdf). For detailed procedures to manage, create, modify, back up,
restore, and upgrade projects, refer to the Project Management topics in the OpenWorks Online
Help ($OWHOME/docs/onlinehelp.htm).
Choosing the installation option “Create a district.dat from TNSNAMES.ora” when installing
OpenWorks will allow you to run OpenWorks and proceed with new projects with no additional
Linux (64 bit) Red Hat Enterprise Linux 5.0 X86_64 512 Mb 1 Gb
a. Operating System
Red Hat Linux: The Release 5000.0.0 supported platform is the X86_64 architecture, but OpenWorks
5000.0.0 is also built in the 32-bit format.
Solaris: The Release 5000.0.0 supported platform is the SPARC64 architecture, but OpenWorks 5000.0.0
is also built in the 32-bit format.
b. Processor
IA32 = Intel Pentium IV, Xeon
X86_64 = Intel Xeon EM64T, AMD Opteron, Athlon 64, Athlon 64FX
c. Swap: If the machine will be an Oracle 10g server, the swap space must be at least three times that of the
machine's memory.
The default small size for a project in OpenWorks 5000.0.0 is 300 Mb.
Software Specifications 软件
• Oracle Database 10g Enterprise Edition; i.e., Oracle 10.2.0.1 and the Oracle 10.2.0.3 patch
• PDF Reader: Adobe Reader 7.x
• Web browser: Mozilla Firefox 1.7 on Linux or Solaris, Mozilla Firefox 1.7 or
Internet Explorer 6.0.x or higher on Windows
Windows:
Licensing 许可
The Landmark Application Manager (LAM) is the license system used to control access to
Landmark applications. LAM is based on Macrovision's FLEXnet Publisher. A new LAM version
is required for the 5000.0.0 release. You cannot have both Release 2003 and Release 5000.0.0
license files running on the same server.
LAM is delivered as a separate application and is not included in the OpenWorks application.
You must obtain new licenses for all Release 5000.0.0 products. To relicense, customers must
contact their local Landmark representative.
For instructions on how to install LAM and to obtain licenses, refer to the LAM Guide—Linux,
Solaris, and Windows (LAM.pdf) for complete details.
第三方应用程序许可协议
Third Party Applications License Agreements
Landmark uses various third party applications in its software. Information about third party
applications is available for all products. The Release Notes will detail the third party information
or define where the information is located. In addition, Landmark has included with most
applications a file titled Third_Party.pdf which includes attribution and license information for all
third party products used by Landmark. Third party information can be found at the following
locations:
The help capability of Landmark Graphics applications assumes an installation of a web browser
and Acrobat Reader.
Some of the documentation for OpenWorks is in Portable Document Format (PDF) and is
viewable in Adobe Reader version four or greater. The documentation for OpenWorks 5000.0.0 is
created for and tested with Adobe Acrobat Reader 7.x on all of the operating systems where
OpenWorks installs.
Landmark does not provide the installation program for Adobe Reader. However, you can
download the reader free of charge from Adobe’s web site. Adobe Reader is freely available on
Adobe’s web site (www.adobe.com).
To use the index created for the OpenWorks documentation, you should download a Full version
or a version with Search.
Simply download the reader from Adobe’s web site. No configuration is necessary.
The Adobe installation program asks you to accept a default installation location or enter the path
where the Acrobat Reader will install the Acrobat files. Landmark recommends that you accept
the default location for the Acrobat Reader files. This path is used by the OpenWorks help system
to find Acrobat Reader.
If you install Acrobat Reader in another location, edit the startAcrobat script in
$OWHOME/bin, or make a link to acroread (the Acrobat Reader executable) in /usr/
bin .
Quick Start
快速入门
Use the steps in this chapter to install Oracle, OpenWorks, and GeoDataLoad with minimal
installation effort.
Installation Checklist: All Platforms lists the steps to be performed on each platform according
to its function as a server or client.
Oracle Installation: The following platform-specific procedures describe creating an Oracle user
and checking kernel settings, installing Oracle 10.2.0.1 and the 10.2.0.3 patch as well as installing
a new OpenWorks 5000.0.0 database or installing the OpenWorks 5000.0.0 schema on an existing
database.
Post-Installation (all platforms, servers and clients) describes setting up your .lgclogin, OS users,
database users, and configuring districts.
GeoDataLoad Installation (all platforms, servers and clients) describes the installation of the
GeoDataload application.
Servers Clients
Linux Linux Solaris Win Win Linux Linux Solaris Win
Step
64 32 64 64 32 64 32 64 32
10. Install OpenWorks 5000.0.0 Y Y Y Y Y
Database Schemas on an Existing
Oracle Database.
Oracle Installation
安装Oracle
8. Install OpenWorks 5000.0.0 Database (Perform these steps to create a new Oracle database
for OpenWorks.)
Landmark recommends using the Pre-Oracle Installer to set up your environment for Oracle and
to create the Oracle user that is used to install Oracle and the OpenWorks database.
The Pre-Oracle Installer also prompts you to modify the kernel parameters if the machine is an
Oracle server.
1. Log on as root.
3. Double-click setup.exe.
4. Click Next.
5. Enter the directory where you want to install the Oracle files.
6. Click Next.
7. Verify that all settings are correct. If necessary, click Previous to correct settings.
8. Click Install.
9. Press Enter.
10. When prompted, enter the Oracle user name. “ora10g” is used throughout this document.
11. When prompted, enter the home directory for the Oracle user. “<drive>/ora10g/OraHome1” is
used throughout this document.
The script creates the Oracle user and updates the kernel.
Change the release file so the Oracle Universal Installer can install the Oracle Software
successfully.
/tmp/database/runInstaller
7. Click Next.
9. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
13. Accept the inventory directory and group name defaults or make appropriate changes.
If any of the tests fail, you must correct the problem(s) before proceeding with the installation.
a. If the test for kernel parameters fails, Configure Kernel Parameters on Linux 32-bit
Servers and rerun the Prerequisite Checks by clicking Back and Next.
b. If the test for swap space fails, exit the installer, perform the steps in Check Swap
Space on Linux 32-bit Servers and run the installer again.
The Execute Configuration scripts window opens, instructing you to execute two scripts,
orainstRoot.sh and root.sh.
20. Click OK in the Execute Configuration scripts window only after successfully executing the
orainstRoot.sh and root.sh scripts.
/tmp/Disk1/runInstaller
6. Click Next.
8. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
9. Click Next.
10. Click Install and wait for the Oracle Software Patch installation to complete.
The Execute Configuration scripts window opens, instructing you to execute one script,
root.sh.
12. Click OK in the Execute Configuration scripts window only after successfully executing the
root.sh script.
You will get error messages that it is not possible to alter the permissions on certain files in
$ORACLE_HOME. These errors can be ignored. The ownership of these files was changed to
root when you ran the root.sh configuration script earlier in the installation procedure.
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
/tmp/Linux/Disk1/InstData/VM/setup.bin
6. Click Next.
7. Enter the directory where you want to install the OpenWorks Database files. “<drive>/ora10g/
Landmark/OpenWorksDatabase” is used throughout this document.
8. Click Next.
11. Enter the directory where you installed the Oracle Database software and patch. “<drive>/
ora10g/OraHome1” is used throughout this document.
12. Enter the appropriate Oracle Sid using a maximum of eight alphanumeric characters; for
example, owskip. Do not use any special characters. Do not use a number at the beginning of
the Sid name.
14. Optional. Perform this step if you will use the database within a particular domain and want
the domain name to be part of the database name.
• To use a domain name as part of the database name, enter the domain name in the
DB_DOMAIN field. The domain name can be any ASCII characters, separated by
periods. For example, to make the owskip database in the domain “lgc.com”, enter
lgc.com in the DB_DOMAIN field.
• If you choose not to use a domain name as part of the database name, leave this field
blank.
16. Accept the default or enter the directory where you want to install the first set of database
files. “<drive>/ora10g/OraHome1/oradata/<Sid>/” is used throughout this document.
18. Set the System and SysAux tablespace sizes. The defaults are 1024MB and 256 MB,
respectively.
20. Accept the default or enter the directory where you want to install the second set of database
files.
21. Set the Undo Tablespace size. The default is 1024 MB.
24. Accept the default or enter the directory where you want to install the third set of database
files.
25. Set the Temp Tablespace size. The default is 512 MB.
28. Accept the default or enter the directory where you want to create OpenWorks schemas
database files.
30. Enter the directory where you want to create project database files.
33. Verify that all settings are correct. If necessary, click Previous to correct settings.
35. Click OK in the Database Configuration Assistant window after the database is successfully
created.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of drop user
statements, IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts,
v$compatibility table or view does not exist, and imp7uec table or view does not exist.
The Shutdown and Startup instance and Listener Output screen opens.
The default passwords for the database users “system” and “sys” are “system” and “sys”
respectively. Change these default passwords after the installation.
如果在Linux或Solaris
4. Set the display, if you are running remotely: 上通过Windows远程安
装,则需要Exceed
setenv DISPLAY <hostname>:0.0 2007。Exceed 2008将无
法工作。
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
/tmp/Linux/Disk1/InstData/VM/setup.bin
6. Click Next.
7. Enter the directory where you want to install the OpenWorks Database files. “<drive>/ora10g/
Landmark/OpenWorksDatabase” is used throughout this document.
8. Click Next.
11. Enter the Oracle Home directory where you installed the Oracle Database software. “<drive>/
ora10g/OraHome1” is used throughout this document.
12. Enter the appropriate Oracle Sid using a maximum of eight alphanumeric characters. Do not
use any special characters.
• If you used the domain name as part of the database name when you created the
database, include the domain in the Oracle Sid field.
• If you did not use a domain name then the Oracle Sid Alias is the same value as Oracle
Sid.
16. Select the directory where you want to create the OpenWorks schema database files.
18. Select the directory where you want to create project database files.
21. Verify that all settings are correct. If necessary, click Previous to correct settings.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements, IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts,
v$compatibility table or view does not exist, and imp7uec table or view does not exist.
You are instructed to set the initialization parameter “recyclebin” (which keeps the deleted
objects in a bin) to “off.”
27. Check the initialization parameter using the following SQL commands:
sqlplus <dba_user>/<dba_password>@sid
SQL>exit
Landmark recommends using the Pre-Oracle Installer to set up your environment for Oracle and
to create the Oracle user that is used to install the Oracle client software.
1. Log on as root.
3. Double-click setup.exe.
4. Click Next.
5. Enter the directory where you want to install the Oracle files.
6. Click Next.
7. Verify that all settings are correct. If necessary, click Previous to correct settings.
8. Click Install.
9. Press Enter.
10. When prompted, enter the home directory for the Oracle user. “<drive>/ora10g/OraHome1” is
used throughout this document.
Change the release file so the Oracle Universal Installer can install the Oracle Software
successfully.
/tmp/client/runInstaller
7. Click Next.
9. Click Next.
12. Accept the default name for the installation or type a new name.
13. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
Note: If any of the tests fail, cancel the install, set the recommended value of the parameter
mentioned on the host, and run the installer again.
The Execute Configuration scripts window opens, instructing you to execute two scripts,
orainstRoot.sh and root.sh.
23. Click OK in the Execute Configuration scripts window only after successfully executing the
orainstRoot.sh and root.sh scripts.
3. Log on as the Oracle user (e.g. ora10g) if you are not currently logged as the Oracle user.
/tmp/Disk1/runInstaller
6. Click Next.
8. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file.
9. Click Next.
10. Click Install and wait for the Oracle Software Patch installation to complete.
You will get error messages that it is not possible to alter the permissions on certain files in
$ORACLE_HOME. These errors can be ignored. The ownership of these files was changed to
root when you ran the root.sh configuration script earlier in the installation procedure.
c. Set Shell Limits for the Oracle User on Linux 64-bit Servers
8. Install OpenWorks 5000.0.0 Database (Perform these steps if you are creating a new Oracle
database for OpenWorks.)
Landmark recommends using the Pre-Oracle Installer to set up your environment for Oracle and
to create the Oracle user that is used to install Oracle and the OpenWorks database.
The Pre-Oracle Installer also prompts you to modify the kernel parameters if the machine is an
Oracle server.
1. Log on as root.
3. Double-click setup.exe.
4. Click Next.
5. Enter the directory where you want to install the Oracle files.
6. Click Next.
7. Verify that all settings are correct. If necessary, click Previous to correct settings.
8. Click Install.
9. Press Enter.
10. When prompted, enter the Oracle user name. “ora10g” is used throughout this document.
11. When prompted, enter the home directory for the Oracle user. “<drive>/ora10g/OraHome1” is
used throughout this document.
The script creates the Oracle user and updates the kernel.
However, you must change the release file so the Oracle Universal Installer can install the Oracle
Software successfully.
/tmp/database/runInstaller
7. Click Next.
9. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
13. Accept the inventory directory and group name defaults or make appropriate changes.
If any of the tests fail, you must correct the problem(s) before proceeding with the installation.
• Configure Kernel Parameters on Linux 64-bit Servers and run the Prerequisite
Checks by clicking Back then Next.
• If the test for swap space fails, exit the installer, perform the steps in Check Swap
Space on Linux 64-bit Servers to create the recommended value of swap space on
the host, and run the installer again.
如果交换空间不足,需按要求创建Swap Space。
16. Click Next.
The Execute Configuration scripts window opens, instructing you to execute two scripts,
orainstRoot.sh and root.sh.
b. Log on as root.
20. Click OK in the Execute Configuration scripts window only after successfully executing the
orainstRoot.sh and root.sh scripts.
/tmp/Disk1/runInstaller.
6. Click Next.
8. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
9. Click Next.
10. Click Install and wait for the Oracle Software Patch installation to complete.
The Execute Configuration scripts window opens, instructing you to execute one script,
root.sh.
12. Click OK in the Execute Configuration scripts window only after successfully executing the
root.sh script.
You will get error messages that it is not possible to alter the permissions on certain files in
$ORACLE_HOME. These errors can be ignored. The ownership of these files was changed to
root when you ran the root.sh configuration script earlier in the installation procedure.
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
/tmp/Linux/Disk1/InstData/VM/setup.bin
6. Click Next.
7. Enter the directory where you want to install the OpenWorks Database files. “<drive>/ora10g/
Landmark/OpenWorksDatabase” is used throughout this document.
8. Click Next.
11. Enter the directory where you installed the Oracle Database software and patch. “<drive>/
ora10g/OraHome1” is used throughout this document.
12. Enter the appropriate Oracle Sid using a maximum of eight alphanumeric characters. Do not
use any special characters.
14. Optional. Perform this step if you will use the database within a particular domain and want
the domain name to be part of the database name.
• Enter the domain name in the DB_DOMAIN field. The domain name can be any
ASCII characters, separated by periods. For example, to make the owskip database in
the domain “lgc.com,” enter lgc.com in the DB_DOMAIN field.
• If you choose not to use a domain name as part of the database name, leave this field
blank.
16. Accept the default or enter the directory where you want to install the first set of database
files. “<drive>/ora10g/OraHome1/oradata/<Sid>/” is used throughout this document.
18. Set the System and SysAux tablespace sizes. The defaults are 1024MB and 256 MB,
respectively.
20. Accept the default or enter the directory where you want to install the second set of database
files.
21. Set the Undo Tablespace size. The default is 1024 MB.
24. Accept the default or enter the directory where you want to install the third set of database
files.
25. Set the Temp Tablespace size. The default is 512 MB.
28. Enter the directory where you want to create OpenWorks schemas database files.
30. Enter the directory where you want to create project database files.
33. Verify that all settings are correct. If necessary, click Previous to correct settings.
35. Click OK in the Database Configuration Assistant window after the database is successfully
created.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements, IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts,
v$compatibility table or view does not exist, and imp7uec table or view does not exist.
The Shutdown and Startup instance and Listener Output screen opens.
The default passwords for the database users “system” and “sys” are “system” and “sys”
respectively. Change these default passwords after the installation.
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
5. On Linux 64-bit and Solaris 64-bit, verify that Oracle lib32 is in the LD_LIBRARY_PATH:
/tmp/Linux/Disk1/InstData/VM/setup.bin
7. Click Next.
8. Enter the directory where you want to install the OpenWorks Database files. “<drive>/ora10g/
Landmark/OpenWorksDatabase” is used throughout this document.
9. Click Next.
12. Enter the directory where you installed the Oracle Database software and patch. “<drive>/
ora10g/OraHome1” is used throughout this document.
13. Enter the appropriate Oracle Sid using a maximum of eight alphanumeric characters. Do not
use any special characters.
• If you used the domain name as part of the database name when you created the
database, include the domain in the Oracle Sid field.
• If you did not use a domain name, the Oracle Sid Alias is the same value as Oracle Sid.
15. Enter the password for the system user. The default is “system.”
17. Select the directory where you want to create the OpenWorks schema database files.
19. Select the directory where you want to create project database files.
22. Verify that all settings are correct. If necessary, click Previous to correct settings.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements, IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts,
v$compatibility table or view does not exist, and imp7uec table or view does not exist.
You are instructed to set the initialization parameter “recyclebin” that keeps the deleted
objects in a bin.
28. Check the initialization parameter using the following SQL commands:
sqlplus <dba_user>/<dba_password>@sid
SQL>exit
What’s Next?
Landmark recommends using the Pre-Oracle Installer to set up your environment for Oracle and
to create the Oracle user that is used to install the Oracle client software.
1. Log on as root.
3. Double-click setup.exe.
4. Click Next.
5. Enter the directory where you want to install the Oracle files.
6. Click Next.
7. Verify that all settings are correct. If necessary, click Previous to correct settings.
8. Click Install.
9. Press Enter.
10. When prompted, enter the Oracle user name. “ora10g” is used throughout this document.
11. When prompted, enter the home directory for the Oracle user. “<drive>/ora10g/OraHome1” is
used throughout this document.
Modify the Linux 64-bit Release File 修改Linux 64-bit Release File
However, you must change the release file so the Oracle Universal Installer can install the Oracle
Software successfully.
/tmp/database/runInstaller
7. Click Next.
9. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
13. Accept the inventory directory and group name defaults or make appropriate changes.
Note: If any of the tests fail, you must exit, set the recommended value of the parameter
mentioned on the host, and run the installer again.
The Execute Configuration scripts window opens, instructing you to execute two scripts,
orainstRoot.sh and root.sh.
25. Click OK in the Execute Configuration scripts window only after successfully executing
orainstRoot.sh and root.sh scripts.
2. Extract the zip file in to a temporary directory using the unzip command:
3. Log on as the Oracle user, e.g., ora10g, if you are not currently logged as Oracle user.
/tmp/Disk1/runInstaller
6. Click Next.
8. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
9. Click Next.
You will get error messages that it is not possible to alter the permissions on certain files in
$ORACLE_HOME. These errors can be ignored. The ownership of these files was changed to
root when you ran the root.sh configuration script earlier in the installation procedure.
What’s Next?
6. Install OpenWorks 5000.0.0 Database (Perform these steps to create a new Oracle database
for OpenWorks.)
Landmark recommends using the Pre-Oracle Installer to set up your environment for Oracle and
to create the Oracle user that is used to install Oracle and the OpenWorks database.
The Pre-Oracle Installer also prompts you to modify the kernel parameters if the machine is an
Oracle server.
1. Log on as root.
3. Double-click setup.exe.
4. Click Next.
5. Enter the directory where you want to install the Oracle files.
6. Click Next.
7. Verify that all settings are correct. If necessary, click Previous to correct settings.
8. Click Install.
9. Press Enter.
10. When prompted, enter the Oracle user name. “ora10g” is used throughout this document.
11. When prompted, enter the home directory for the Oracle user. “<drive>/ora10g/OraHome1” is
used throughout this document.
The script creates the Oracle user and updates the kernel.
3. Extract the zip file in to /tmp/database using the gunzip and cpio commands:
gunzip /tmp/database/10gr2_db_sol.cpio.gz
/tmp/database/runInstaller
7. Click Next.
9. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
13. Accept the inventory directory and group name defaults or make appropriate changes.
Note: If any of the tests fail, cancel the install, set the recommended value of the parameter
mentioned on the host, and run the installer again.
• Set the kernel parameters as required and run the Prerequisite Checks by clicking Back
then Next.
• If the test for swap space fails, exit the installer, perform the steps in Check Swap
Space on Solaris 10 Servers and run the installer again.
The Execute Configuration scripts window opens, instructing you to execute two scripts,
orainstRoot.sh and root.sh.
22. Click OK in the Execute Configuration scripts window only after successfully executing the
orainstRoot.sh and root.sh scripts.
/tmp/Disk1/runInstaller.
6. Click Next.
8. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file. “<drive>/ora10g/OraHome1” is used throughout this document.
9. Click Next.
10. Click Install and wait for the Oracle Software Patch installation to complete.
The Execute Configuration scripts window opens, instructing you to execute one script,
root.sh.
12. Click OK in the Execute Configuration scripts window only after successfully executing the
root.sh script.
You will get error messages that it is not possible to alter the permissions on certain files in
$ORACLE_HOME. These errors can be ignored. The ownership of these files was changed to
root when you ran the root.sh configuration script earlier in the installation procedure.
2. Get the OpenWorks 5000.0.0 Database zip file and extract it in to the temporary directory.
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
/tmp/Solaris/Disk1/InstData/VM/setup.bin
5. Click Next.
6. Enter the directory where you want to install the OpenWorks Database files. “<drive>/ora10g/
Landmark/OpenWorksDatabase” is used throughout this document.
7. Click Next.
9. Click Next.
10. Enter the directory where you installed the Oracle Database software and patch. “<drive>/
ora10g/OraHome1” is used throughout this document.
11. Enter the appropriate Oracle Sid using a maximum of eight alphanumeric characters. Do not
use any special characters.
13. Optional. Perform this step to use the database within a particular domain and have the
domain name be part of the database name. Enter the domain of your choice or leave it blank.
15. Accept the default or enter the directory where you want to install the first set of database
files. “<drive>/ora10g/OraHome1/oradata/<Sid>/” is used throughout this document.
17. Set the System and SysAux tablespace sizes. The defaults are 1024MB and 256 MB,
respectively.
19. Accept the default or enter the directory where you want to install the second set of database
files.
20. Set the Undo Tablespace size. The default is 1024 MB.
23. Accept the default or enter the directory where you want to install the third set of database
files.
24. Set the Temp Tablespace size. The default is 512 MB.
27. Enter the directory where you want to create OpenWorks schemas database files.
29. Enter the directory where you want to create project database files.
32. Verify that all settings are correct. If necessary, click Previous to correct settings.
34. Click OK in the Database Configuration Assistant window after the database is successfully
created.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements, IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts, etc.
However, TNS- errors are installation failure indicators.
The default passwords for database user “system” and “sys” are “system” and “sys”
respectively. Change these default passwords after the installation.
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
3. On Linux 64-bit and Solaris 64-bit, verify that Oracle lib32 is in the LD_LIBRARY_PATH:
5. Extract the zip file in the temporary directory using the unzip command.
/tmp/Solaris/Disk1/InstData/VM/setup.bin
7. Click Next.
8. Enter the directory where you want to install the OpenWorks Database files. “<drive>/ora10g/
Landmark/OpenWorksDatabase” is used throughout this document.
9. Click Next.
12. Enter the directory where you installed the Oracle Database software and patch. “<drive>/
ora10g/OraHome1” is used throughout this document.
13. Enter the appropriate Oracle Sid using a maximum of eight alphanumeric characters. Do not
use any special characters.
• If you used a domain name as part of the database name when you created the
database, enter sid.domain.com.
• If you did not use a domain name the Oracle Sid Alias is the same value as Oracle Sid.
16. Enter the password for the Oracle system user. The default is “system.”
18. Enter the directory where you want to create the OpenWorks schema database files.
20. Enter the directory where you want to create project database files.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements and IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts, etc.
You are instructed to set the initialization parameter “recyclebin” (which keeps the deleted
objects in a bin) to “off.”
28. Check the initialization parameter using the following SQL commands:
sqlplus <dba_user>/<dba_password>@sid
SQL>exit
What’s Next?
Landmark recommends using the Pre-Oracle Installer to set up your environment for Oracle and
to create the Oracle user that is used to install the Oracle client software.
1. Log on as root.
3. Double-click setup.exe.
4. Click Next.
5. Enter the directory where you want to install the Oracle files.
6. Click Next.
7. Verify that all settings are correct. If necessary, click Previous to correct settings.
8. Click Install.
9. Press Enter.
10. When prompted, enter the Oracle user name. “ora10g” is used throughout this document.
11. When prompted, enter the home directory for the Oracle user. “<drive>/ora10g/OraHome1” is
used throughout this document.
3. Extract the zip file in to /tmp/client using the gunzip and cpio commands:
gunzip /tmp/client/10gr2_client_sol.cpio.gz
/tmp/client/runInstaller
7. Click Next.
9. Click Next.
12. Accept the default name for the installation or type a new name.
13. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file.
• If the kernel parameters check fails, set the kernel parameters as required and run the
Prerequisite Checks by Clicking on Back and Next.
• If any of the other tests fail, cancel the install, set the recommended value of the
parameter mentioned on the host, and run the installer again.
The Execute Configuration scripts window opens, instructing you to execute two scripts,
orainstRoot.sh and root.sh.
24. Click OK in the Execute Configuration scripts window only after successfully executing the
orainstRoot.sh and root.sh scripts.
/tmp/Disk1/runInstaller.
6. Click Next.
8. Verify that the default Oracle Home Location is the same as the ORACLE_HOME value in
the ora10g .login file.
9. Click Next.
10. Click Install and wait for the Oracle Software Patch installation to complete.
You will get error messages that it is not possible to alter the permissions on certain files in
$ORACLE_HOME. These errors can be ignored. The ownership of these files was changed to
root when you ran the root.sh configuration script earlier in the installation procedure.
What’s Next?
5. Install OpenWorks 5000.0.0 Database (Perform these steps to create a new Oracle database
for OpenWorks.)
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\10201_database_win32\database\setup.exe
5. Click Next.
7. Accept the default path for the Oracle Home Location or select a new location. The default
path is C:\oracle\product\10.2.0\db_1.
• If any of the tests fail, cancel the install, set the recommended value of the parameter
mentioned on the host, and run the installer again.
• If you get the Checking Network Configuration requirements warning, cancel the
install, follow the Prerequisites for Installing Oracle on DHCP Computers, and run
the installer again.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\p5337014_10203_WINNT\Disk1\setup.exe
5. Click Next.
6. Verify that the default name for the installation is the same as the name used when the
software was installed.
7. Verify that the default path is the same as the location used when the software was installed.
8. Click Next.
9. Click Install and wait for the Oracle Software Patch installation to complete.
11. When prompted “Do you really want to exit?” click OK.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\oracle\product\10.2.0f\db_1\users\ora10g
C:\temp\owdb5000\Disk1\InstData\VM\install.exe
7. Click Next.
8. Enter the directory where you want to install the OpenWorks Database files.
9. Click Next.
12. Verify that the default Oracle Home directory is where you installed Oracle.
13. Accept the machine name as the default Oracle Sid or enter an Oracle Sid using a maximum
of eight alphanumeric characters. Do not use any special characters.
15. Accept the default directory or enter the directory where you want to install the first set of
database files.
17. Accept the default System size of 1024 MB and the default SysAux tablespace size of 256
MB.
19. Accept the default directory or enter the directory where you want to install the second set of
database files.
20. Accept the default Undo Tablespace size of 1024 MB and the default Redo Logs size of 16
MB.
22. Accept the default directory or enter the directory where you want to install the third set of
database files.
23. Accept the default Temp size of 512 MB and the default Users Tablespaces size of 5 MB.
25. Accept the default directory or enter the directory where you want to create OpenWorks
schemas database files.
27. Accept the default directory or enter the directory where you want to create OpenWorks
schemas database files. If desired, enter additional directories for project database files.
29. Verify that all settings are correct. If necessary, click Previous to correct settings.
This step takes about 20 minutes. The Oracle instance is created and started, database files and
data dictionary views are created, and the Oracle JVM and Enterprise Manager Repositry are
created.
31. Click OK in the Database Configuration Assistant window after the database is successfully
created.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements, IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts,
v$compatibility table or view does not exist, and imp7uec table or view does not exist.
The default passwords for the database users “system,” “sys,” “sysman,” and “dbsnmp” are
“system,” “sys,” “sysman,” and “dbsnmp” respectively. Change these default passwords after
the installation.
36. Accept the default Yes to shutdown and startup the instance and listener and click Next.
The Shutdown and Startup instance and Listener Output screen opens.
37. Verify that the commands completed successfully, then click Next.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\oracle\product\10.2.0\db_1\users\ora10g
C:\temp\owdb5000\Disk1\InstData\VM\install.exe
7. Click Next.
8. Enter the directory where you want to install the OpenWorks Database files.
9. Click Next.
12. Verify that the default Oracle Home directory is where you installed Oracle.
13. Accept the machine name as the default Oracle Sid or enter an Oracle Sid using a maximum
of eight alphanumeric characters. Do not use any special characters.
17. Select the directory where you want to create OpenWorks schema database files.
19. Select the directory where you want to create project database files.
22. Verify that all settings are correct. If necessary, click Previous to correct settings.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of drop user
statements and IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts.
You are instructed to set the initialization parameter “recyclebin” (which keeps the deleted
objects in a bin) to “off.”
28. Check the initialization parameter using the following SQL commands:
sqlplus <dba_user>/<dba_password>@sid
What’s Next?
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\10201_client_win32\client\setup.exe
5. Click Next.
6. Select Administrator.
7. Click Next.
8. Accept the default name of the installation, oraClient10g_home1, or enter a new name.
• If any of the tests fail, cancel the install, set the recommended value of the parameter
mentioned on the host, and run the installer again.
• If you get the Checking Network Configuration requirements warning, cancel the
install, follow the Prerequisites for Installing Oracle on DHCP Computers, and run
the installer again.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\p5337014_10203_WINNT\Disk1\setup.exe
5. Click Next.
6. Change the default name for the installation to the name used when the Oracle 32-bit client
was installed; i.e., OraClient10g_home1.
7. Change the default path to the same location used the Oracle 32-bit client was installed; i.e.,
<drive>:\oracle\product\10.2.0\client_1.
8. Click Next.
9. Click Install and wait for the Oracle Software Patch installation to complete.
What’s Next?
7. Install OpenWorks 5000.0.0 Database (Perform these steps to create a new Oracle database
for OpenWorks.)
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\10201_win64_x64_database\database\setup.exe
5. Click Next.
7. Accept the default path for the Oracle Home Location or select a new location. The default
path is:
<drive>:\oracle\product\10.2.0\db_1.
If you receive a Checking Network Configuration requirements warning, cancel the install,
follow the Prerequisites for Installing Oracle on DHCP Computers, and run the installer
again.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\ p5337014_10203_MSWIN-x86-64\Disk1\setup.exe
5. Click Next.
6. Change the default name for the installation to the same name used when the software was
installed; i.e., OraDb10g_home1.
7. Change the default path to the same location used when the software was installed; i.e.,
<drive>:\oracle\product\10.2.0\db_1. The patch is applied in this path.
8. Click Next.
9. Click Install and wait for the Oracle Software Patch installation to complete.
The Configuration Assistants screen opens briefly, then the End of Installation screen opens.
Install Oracle Client Software 32 bit (10.2.0.1.0) 安装Oracle Client Software 32 bit
(10.2.0.1.0)
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\10201_client_win32\client\setup.exe
5. Click Next.
6. Select Administrator.
7. Click Next.
8. Accept the default name of the installation, oraClient10g_home1, or enter a new name.
• If any of the tests fail, cancel the install, set the recommended value of the parameter
mentioned on the host, and run the installer again.
• If you get the Checking Network Configuration requirements warning, cancel the
install, follow the Prerequisites for Installing Oracle on DHCP Computers, and run
the installer again.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\Temp\p5337014_10203_WINNT\Disk1\setup.exe
5. Click Next.
6. Change the default name for the installation to the name used when the Oracle 32-bit client
was installed; i.e., OraClient10g_home1.
7. Change the default path to the same location used when the Oracle 32-bit client was installed;
i.e., <drive>:\oracle\product\10.2.0\client_1. The patch is applied in this path.
8. Click Next.
9. Click Install and wait for the Oracle Software Patch installation to complete.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\oracle\product\10.2.0\db_1\users\ora10g
C:\temp\owdb5000\Disk1\InstData\VM\install.exe
7. Click Next.
8. Enter the directory where you want to install the OpenWorks Database files. The default path
is C:\Landmark\OpenWorks.
9. Click Next.
12. Verify that the default Oracle Home directory is where you installed Oracle 64-bit; i.e.,
<drive>:\oracle\product\10.2.0\db_1.
13. Accept the machine name as the default Oracle Sid or enter an Oracle Sid using a maximum
of eight alphanumeric characters. Do not use any special characters.
15. Accept the default directory or enter the directory where you want to install the first set of
database files.
17. Accept the default System size of 1024 MB and the default SysAux tablespace size of 256
MB.
19. Accept the default directory or enter the directory where you want to install the second set of
database files.
20. Accept the default Undo Tablespace size of 1024 MB and the default Redo Logs size of 16
MB.
22. Accept the default directory or enter the directory where you want to install the third set of
database files.
23. Accept the default Temp size of 512 MB and the default Users Tablespaces size of 5 MB.
25. Accept the default directory or enter the directory where you want to create OpenWorks
schemas database files.
27. Accept the default directory or enter the directory where you want to create project database
files.
30. Verify that all settings are correct. If necessary, click Previous to correct settings.
31. Click Install when all settings are correct. The Oracle Wallet and a number of other settings
are configured.
This step takes about 20 minutes. The Oracle instance is created and started, database files and
data dictionary views are created, and the Oracle JVM and Enterprise Manager Repositry are
created.
32. Click OK in the Database Configuration Assistant window after the database is successfully
created.
The default passwords for the database users “system,” “sys,” “sysman,” and “dbsnmp” are
“system,” “sys,” “sysman,” and “dbsnmp” respectively. Change these default passwords after
the installation.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements and IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts.
37. Accept the default Yes to shutdown and startup the instance and listener and click Next.
The Shutdown and Startup instance and Listener Output screen opens.
38. Verify that the commands completed successfully, then click Next.
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
C:\oracle\product\10.2.0\db_1\users\ora10g
c:\temp\owdb5000\Disk1\InstData\VM\install.exe
7. Click Next.
8. Enter the directory where you want to install the OpenWorks Database files.
9. Click Next.
12. Verify that the default Oracle Home directory is where you installed Oracle 64-bit.
13. Accept the machine name as the default Oracle Sid or enter an Oracle Sid using a maximum
of eight alphanumeric characters. Do not use any special characters.
17. Accept the default directory or enter the directory where you want to create OpenWorks
schema database files,
19. Accept the default directory or enter the directory where you want to create project database
files.
22. Verify that all settings are correct. If necessary, click Previous to correct settings.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
statements and IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts.
You are instructed to set the initialization parameter “recyclebin” (which keeps the deleted
objects) to “off.”
28. Check the initialization parameter using the following SQL commands:
sqlplus <dba_user>/<dba_password>@sid
SQL>exit
Install Windows 2003 SP2 32-bit Client 安装Windows 2003 SP2 32-bit Client
Because there is no Windows 64-bit Client version of Oracle, you must install the Windows XP/
2003 SP2 32-bit Client.
What’s Next?
OpenWorks Installation
安装OpenWorks
Use the steps in this section to install OpenWorks.
1. On Linux or Solaris, simply remove the $OWHOME directory and its contents.
2. If you install remotely on Linux or Solaris from Windows verify that Exceed 2007 is installed
on the Windows computer. Exceed 2008 will not work.
1. Verify that Exceed 2007 is installed by checking the version using the “About” box on Exceed
or checking the “About” option in an Exceed window. If you have an old version of Exceed
installed, uninstall it, reboot, and install Exceed 2007 before continuing.
5. Set the OW_HOME_DIR variable for the user who will install OpenWorks:
Important: The user who installs OpenWorks must have administrator privileges.
a. Log on as the user with administrator privileges who will install OpenWorks. Do not
log on as Administrator.
e. When the Environment Variables window opens, click New in the User variables pane.
• Type the path where OpenWorks will be installed in the Variable value text box;
for example, C:\Landmark\OpenWorks.
• Click OK.
在Windows上安装时考虑多用户情况
Each user who will run OpenWorks on this system must set the
OW_HOME_DIR User variable and create their own folder under
Openworks\users for their Oracle wallet. See the post-installation section
Windows Servers and Clients: Oracle Wallet and Multiple
Users.
1. Log on as a user with administrator privileges who will install OpenWorks and who has set the
OW_HOME_DIR User variable.
• Do not install if the OW_HOME_DIR User variable has not been set.
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
5. Click Next.
7. Click Next.
9. Click Next.
• After installation, you can change where flat files are stored. Edit the owdir.dat file in
the system directory.
13. Accept the default directory or enter the directory where you installed Oracle (see the Oracle
Software Installation section).
14. Enter the appropriate Oracle Sid using a maximum of eight alphanumeric characters. Do not
use any special characters.
仅适用Windows64位系统
Windows 64-bit only. The Get Oracle 32bit Client Information screen opens.
16. Enter the directory where the Oracle 32bit client was installed; i.e.,
<drive>:\oracle\product\10.2.0\client_1
17. Enter the Oracle Sid using a maximum of eight alphanumeric characters. Do not use any
special characters.
所有平台
All platforms. The District.dat screen opens.
• If you select “Create an empty district.dat,” the district.dat file must be configured
before any OpenWorks application is launched. See the OpenWorks Post-Installation
Configuration section for more information.
21. Click Yes to install the Microsoft Visual C++ 2005 SP1 Redistributable Package.
25. Verify that all settings are correct. If necessary, click Previous to correct settings.
Windows only. The Microsoft Visual C++ 2005 SP1 Redistributable Package License Agreement
window opens.
Linux 64-bit only. If the installer cannot find the libg2c library, the Missing library window
opens. You will install the library after the OpenWorks installation.
Linux only. The RedHat 5 specific screen opens, instructing you to run the root.sh script after the
OpenWorks installation.
What’s Next?
Post-Installation
安装Oracle和OpenWorks之后
Overview 简介
Perform the configuration steps in this section after installing Oracle and OpenWorks. See the
OpenWorks Project Administration manual and online help for more detailed information.
• Linux Only
• All Platforms
• Windows
• District Configuration
Linux Only
Perform this procedure if the OpenWorks installer could not find the libg2c library and the
Missing library window opened at the end of the OpenWorks installation.
You can download the rpm from the RedHat web site, http://rhn.redhat.com, or contact RedHat
customer support.
Perform this procedure if instructed to do so via a RedHat 5 specific screen at the end of the
OpenWorks installation.
sh $OWHOME/bin/root.sh
#!/bin/sh
# This script needs to be executed as root
to change the security context
# This file was auto-generated
chcon -c -v -R -u system_u -r object_r -t lib_t /d01/ow_nc/ow_nc/lib/
chcon -c -v -R -u system_u -r object_r -t lib_t /d01/ow_nc/ow_nc/lib64/
chcon -t texrel_shlib_t /d01/ow_nc/ow_nc/lib/*
chcon -t texrel_shlib_t /d01/ow_nc/ow_nc/lib64/*
# For oracle:
#chcon -c -v -R -u system_u -r object_r -t lib_t /d01/ora10g/OraHome1//lib32
#chcon -t texrel_shlib_t chcon -t texrel_shlib_t /d01/ora10g/OraHome1//lib32/*
2. Launch $OWHOME/bin/lgcuser.
3. Select create user (#2) and follow the instructions on the screen.
4. Select Update User (#4) and follow the instructions on the screen.
Perform the following procedure if the local user exists or you need to update a network user.
2. Select Update User (#4) and follow the instructions on the screen.
The owsetup script performs a number of configuration steps such as setting permissions and
adding startup commands so that OpenWorks will run properly.
1. Log in as root.
3. When the OpenWorks Set Up utility opens, select the appropriate option:
OpenWorks now uses the Oracle Secure Enterprise Password Store (Oracle Wallet) to store
passwords to the database and to handle the security of the passwords.
A user in OpenWorks 5000.0.0 is now associated with both an Operating System (OS) user and an
Oracle internally identified user. The Oracle user will have the same name as the OS user, but will
now be required to provide a user name and a password to access the OpenWorks database. Users
can now change their Oracle password from the Command Menu. For detailed information and
procedures to manage project databases and access, refer to the OpenWorks Online Help
(ow_online_help.htm).
For the purposes of installation however, the steps to grant database access to the OpenWorks user
are provided here.
Note: The Modify Database Users utility in this procedure replaces the orauser utility from
previous releases of OpenWorks.
From the OpenWorks Command Menu, select Project > Modify Database Users.
Windows: From the Start menu, select All Programs > Landmark > OpenWorks >Project
Administration > Modify Database Users.
4. In User Name, enter the name of a database administrator (DBA) who has sufficient privileges
to allow users to access the OpenWorks database. For example, the SYSTEM user (one of the
internal Oracle database administrators) with SYSDBA privileges is such a user.
6. Click Login. If the correct credentials are entered, the Database Users window opens.
If the Database Users window does not display, the Login Failed dialog displays asking you to
try to log in again. Click OK to reassert the DBA Logon dialog. The login process allows
three login attempts. After three attempts, you must repeat step 2 to try to log in again.
7. Enter the OpenWorks user name and password in the User Details area.
8. Check OW_Admin if the user will be allowed to create and delete projects and create, change,
or delete tables in a project or the OWSys schema. The default state of the box is checked.
9. Check OWSys_Admin if the user will be allowed to alter the OWSys schema in the
OpenWorks database. The default state of the box is unchecked.
Note: For more information about OW_Admin and OWSys_Admin, see Project
Management > Project Administration > OpenWorks Security in the OpenWorks Online
Help (ow_online_help.htm).
The default passwords assigned during installation for the database users “system,” “sys,”
“sysman,” and “dbsnmp” are “system,” “sys,” “sysman,” and “dbsnmp” respectively.
Use the Modify Database Users utility described in the procedure above to change these default
passwords after installation.
In order to configure the Oracle Wallet configuration set up properly, each user who will run
OpenWorks on this computer must have the OW_HOME_DIR User variable set and an
OpenWorks\users folder for their Oracle wallet.
For example, if three users (user1, user2 and user3) will be using this Windows machine, create
the following directories:
%OWHOME%\users\user1
%OWHOME%\users\user2
%OWHOME%\users\user3
4. When the Environment Variables window opens, click New in the User variables pane.
C:\Landmark\OpenWorks\users
C:\Landmark\OpenWorks\users\<your login>
The first time you access an OpenWorks project, you will be prompted for your password. The
wallet information will be automatically created after you input your password.
2. In the Runtime Settings tab, choose XWindow System Settings, then click OK.
3. Choose Registered.
6. Click OK.
7. Reboot.
SeisWorks projects as separate entities have been replaced by the new project structure of
OpenWorks. But, OpenWorks 5000.0.0 may contain large numbers of projects and may still refer
to directories containing seismic data. Districts allow a company to break up large lists of
projects, and allow the company to separate data by business unit for better data security or disk
ownership.
Support for districts has become a part of the framework of OpenWorks. In an installation of
OpenWorks, a company can decide whether it will implement districts or not. To implement
districts, dir.dat and owdir.dat must be configured for each district, as before, but additionally,
district.dat must be configured with the name of each district and the directory of each district's
dir.dat and owdir.dat. Utilities, such as Project Administration and Project Status Tool, support
districts in their interfaces. For example, when a user of OpenWorks creates a new project in
Project Administration, part of the project configuration includes selecting the district to which it
will belong.
If the OpenWorks installation option “Create empty district.dat” was selected, you must configure
district.dat before you can run OpenWorks. The default location of the district.dat file is
$OWHOME/conf. You can change the default location by adding the environment variable
OW_CONF_DIR to the .lgclogin file. The default location of OW_CONF_DIR is $OWHOME/
conf. See Project Management > Districts in the OpenWorks Online Help
(ow_online_help.htm) for detailed procedures to perform district configuration tasks.
If you are restoring an OpenWorks project and its SeisWorks data from a version before Release
5000.0.0, it is especially important to refer to the topics in Project Management > Districts in
the OpenWorks Online Help (ow_online_help.htm) before proceeding because the lines for the
restoring data must follow the syntax of the previous version and a properly configured plist.dat
must reside in the same location as dir.dat.
GeoDataLoad Installation
安装GeoDataLoad
If you have a GeoDataLoad license, follow the installation steps in this section.
Windows
3. When the uninstaller launches, select Complete Uninstall and click Next, and Next again. It is
not necessary to reboot.
Linux or Solaris
Install GeoDataLoad
1. Set the display, if you are running remotely: setenv DISPLAY <hostname>:0.0
3. Click Next.
4. Accept the default or enter the directory where you want to install GeoDataLoad.
5. Click Next.
6. Verify that all settings are correct. If necessary, click Previous to correct settings.
7. Click Done.
This chapter contains information about upgrading an installation of the OpenWorks software
version 5000.x to a higher version of the OpenWorks software.
If you are installing the patch over an existing 5000.0.0.x installation, the installer will not prompt
you for district.dat, flat file setup, and default ORACLE_HOME configurations. These
configurations will be saved during patching. The installation process has the following parts:
Version 5000.0.0.2 of the OpenWorks database does not require an OWSYS upgrade.
Projects from version 5000.0.0.0 or 5000.0.0.1 that are restored to an OpenWorks database with the
5000.0.0.2 update are automatically upgraded to 5000.0.0.2 when restored.
Projects from releases before version 5000.0.0.0 that are restored to an OpenWorks database with the
5000.0.0.2 update are upgraded to version 5000.0.0.2 after the restoration of the project, when you
upgrade the project in Project Administration.
Note: If you do not close out all of the running OpenWorks processes, you may receive “file
busy” messages in the installation log file. These messages can be safely ignored.
Release 5000.0.0.2 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.2 105
OpenWorks® Software Installation Procedures Landmark
$OWHOME/bin/stop_netd
$OWHOME/bin/start_netd
sh setup.bin
setup.exe
After installing version 5000.0.0.2, you must upgrade any 5000.0.0.x projects in the database to
version 5000.0.0.2.
To patch the data model of a project database and its interpretation projects, execute the following
script in a terminal window:
where OW_SID is the system identifier of the OpenWorks database where the project database is
located.
LogDir is the location where the script should store its logs.
更新一个OpenWorks数据库中的所有
Upgrading All Project Databases in an OpenWorks Database
工区数据库
To upgrade all projects in an OpenWorks database, run the script with the ProjectDBName
argument set to the ALL keyword. For example:
106 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.2 Release 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
Or
Project Administration allows you to upgrade project databases. After the OpenWorks software
has been updated, you need to update all the projects already in the database. For project
databases of version 5000.0.0.0 or greater, you can select more than one project database, and
upgrade all the selected projects at one time.
1. Right-click the name of a project database that should be upgraded to the current version of
the OpenWorks software. The pop-up menu displays
2. Select the Upgrade option in the menu. The Project Upgrade dialog displays.
3. In the list of project databases, use Ctrl+Select to select a discontiguous set of project
databases, or Shift+Select to select a contiguous set of project databases, or check the Select
All box to select all project databases in the list.
4. Click Start.
After upgrading the OpenWorks software (for instance, from version 5000.0.0.0 or 5000.0.0.1 to
5000.0.0.2), you should update the user profile of the users of the database. Specifically,
launcher.dat and .lgclogin must be updated. The default versions of the files are in $OWHOME/
templates.
2. Move launcher.dat and .lgclogin in your home directory to another location. For example:
mv launcher.dat launcher_old.dat
mv .lgclogin .lgclogin.old
3. Copy launcher.dat and .lgclogin from the templates directory in the OpenWorks home
directory to your home directory. For example:
Release 5000.0.0.2 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.2 107
OpenWorks® Software Installation Procedures Landmark
cp $OWHOME/templates/launcher.dat ~/.
cp $OWHOME/templates/.lgclogin ~/.
4. If you have edited the files, compare your old files with the new file, and make appropriate
changes to the new file.
You can now run the OpenWorks software with the new profile.
108 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.2 Release 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
This section provides some basic information you should know before you begin upgrading and
migrating your data to a new OpenWorks database instance of Release 5000.0.x.
The major differences in the Oracle databases between the OpenWorks software R2003 and
version 5000.0.x are:
• The OpenWorks software R2003.12 uses Oracle 8.1.7.4 or Oracle 9.2.0.4. The
OpenWorks software version 5000.0.0 uses Oracle 10g Release 2 (10.2.0.3).
• The OpenWorks sotware R2003.12 uses externally identified Oracle users. The
OpenWorks software version 5000.0.0 uses internally identified Oracle users.
1. The runtime environment and database of the OpenWorks software R2003.12 exist.
2. The runtime environment of the OpenWorks software version 5000.0.0.2 exists. For
information about installing, see “Quick Start” on page 7.
3. The OWSYSSID (for example, ow2003) of the R2003.12 instance has been added to
tnsnames.ora (located in $ORACLE_HOME/network/admin) on the machine where the
runtime environment of the OpenWorks software version 5000.0.0.2 is installed.
4. A database connection to the OWSYSSID of the R2003.12 instance can be made from the
runtime environment of the OpenWorks software version 5000.0.0.2 using SQLPlus.
5. The Oracle server, where version 5000.x of the OpenWorks database is located, is on the same
machine as the installation of version 5000.x of the OpenWorks software.
• Perform a full backup of the data in the R2003.12 OpenWorks database. This step is a
safety measure.
• Install a database server for the OpenWorks software version 5000.0. For more
information, see “Quick Start” on page 7. The installation workflow is on the same
page (“Installation Workflow”).
— Installation checklist
— Post-installation steps
• In tnsnames.ora of the Oracle installation for the OpenWorks software version 5000.0,
include the connection information for the OpenWorks database (OWSYSSID) of
R2003.12.
• Using SQLPlus on the system where version 5000.0, test the connect to the R2003.12
database.
Because the OpenWorks database in R2003.12.x.x used Oracle 8i or 9i as its data management
system an existing R2003.12.x.x cannot be upgraded in place. In it most basic terms, the data in a
database for R2003.12.x.x must be exported from that database and imported into an OpenWorks
database of version 5000.0.0.2. The procedures below delineate that procedure.
To prepare the data for exporting from an R2003 database, you must remove any remote projects
and generate a database schema configuration files for the R2003.12 database. The steps below
will help you in those tasks.
These steps should be performed in the environment of version 5000.0.0.2 of the OpenWorks
software.
cd $OWHOME/dat/project5000.0
sqlplus system/Password@OW_DB_SID
SQL>@check_remote_projects.sql "OW_DB_SID"
If there are remote projects, the result will look similar to the following. Perform the
steps shown in the results.
5000.0.0.2 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 111
OpenWorks® Software Installation Procedures Landmark
2. Generate a schema definition file for the existing OpenWorks R2003.12 database.
cd $OWHOME/dat/ project5000.0
sqlplus system/<password>@ow2003
For example:
SQL>@process_ow2003_users.sql /<directory_path>/
ow2003_users.sql
-or-
cd $OWHOME/dat/project5000.0
sqlplus system/<password>@ow2003
112 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
commit;
5000.0.0.2 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 113
OpenWorks® Software Installation Procedures Landmark
Perform the following steps as an Oracle database user (such as the SYSTEM user) in the
environment of Release 2003.12 of the OpenWorks 2003.12 software.
5. Run a full Oracle database export as the database user (e.g., system) against the R2003.12
OWSYSSID ow2003. Modify the settings of the following variables in the fullexport.cntl
configuration file, that was copied in step 4 from the environment of version 5000.0.0.2.
BUFFER=2000000
USERID="system/Password@OW_DB_SID"
FILE=/FullPath/FileNameOfExportFile.dmp
FULL=Y
LOG=/FullPath/FileNameOfLogFile.log
FullPath is the full path to the location of the dmp and log files.
FileNameOfExportFile is the name of the export file. This file must have a dmp extension (or
file suffix).
FileNameOfLogFile is the name of the log file. This file name must have a log extension (or
file suffix).
Note: It is very important to use the matching Oracle export utility to the correct
version of Oracle server. You must use an Oracle 8 export utility for an Oracle 8 server
and use an Oracle 9 export utility for an Oracle 9 server.
su - oracle8
$ORACLE_HOME/bin/exp parfile = fullexport.cntl
su - oracle9
$ORACLE_HOME/bin/exp parfile = fullexport.cntl
114 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
c. Copy the export file from the R2003.12 installation to the installatin of OpenWorks
version 5000.0.0.
在OpenWorks 5000.0.0运行环境中的操作步骤
Procedures in the OpenWorks 5000.0.0 Runtime Environment
The tablespace data file structure will be kept the same as your OpenWorks R2003.12
instance, make sure you pre-create these data file directories in your ow5000 installation with
oracle as the directories' owner. If you want to change the data file structure, edit the
ow2003_tablespace.sql file and create the directories as the Oracle user (e.g. ora10g), the
directories' owner.
9. Run the ow2003_tablespace.sql script (created in Step 2 on page 112) to create the tablespaces
and OpenWorks project users in the OpenWorks 5000.0.0 instance (ow5000).
For a list of possible errors, see “Possible Errors During the Import” on page 122.
10. Run a full Oracle database import as the database user (e.g., system) using the ow2003.dmp
file (created in Step 5.b.) in the ow5000 instance. Modify the parameter values in the file
based on your configuration.
Note: The Oracle import process will change the system password to match the password in
the OW2003 database.
Assumption: You already copied ow2003.dmp (created in Step 6 on page 114 ) from the
OpenWorks R2003.12 runtime image to an OpenWorks 5000.0.0 runtime image.
5000.0.0.2 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 115
OpenWorks® Software Installation Procedures Landmark
a. su - ora10g
BUFFER=2000000
USERID="system/<password>@ow5000"
FILE=/<dir>/ow2003.dmp
FULL=Y
IGNORE=Y
LOG=/<dir>/ow5000.log
Assumption: This step assumes that both the OpenWorks database and the OpenWorks
software are installed on the same machine.
a. As the database user (e.g., system), create an internal account for the Oracle user (e.g.,
ora10g) in the ow5000 database.
sqlplus system/<ow2003_password>@ow5000
116 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
b. As the Oracle user (e.g., ora10g), set the following environment variable. For
example:
su - ora10g
For example:
5000.0.0.2 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 117
OpenWorks® Software Installation Procedures Landmark
13. If the tablespace data file structure in the ow2003_tablespace.sql file is NOT modified, skip
this step and go to Step 14. Otherwise, remove the invalid entries from the
LMSYS.OW_LMSYS_DB_DIR table as follows.
sqlplus system/<ow2003_password>@ow5000
DIR_PATH
/d01/ora9i/OraHome1/owprojects/
/d01/ora9i/OraHome1/owprojects to
/d01/ora10g/OraHome1/owprojects in ow2003_tablespace.sql.
SQL>commit;
Note: Use the $OWHOME/bin/dboradir script to maintain the Oracle database locations.
14. Run the ow2003_users.sql script (created in step 2) to create the OpenWorks project users and
populate the project privileges for each OpenWorks project user.
SQL>@<dir>/ow2003_users.sql
118 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
commit;
Optionally, to change the password for OpenWorks project user “owjune,” do the following:
sqlplus system/<ow2003_password>@ow5000
Exit SQL*Plus.
15. Upgrade each OpenWorks project using the OpenWorks ProjectAdmin or the command line.
Note: You must have an lgcuser and an Oracle internal user first and the usernames of lgcuser
and the Oracle internal user must match.
su - root
OWHOME=<OpenWorks home directory>
export OWHOME
cd ${OWHOME}/bin
./lgcuser
Select option 4 to update an existing user's profile
Select option 7 to quit
su - root
5000.0.0.2 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 119
OpenWorks® Software Installation Procedures Landmark
export OWHOME
cd ${OWHOME}/bin
./lgcuser
i. Login as lgcuser.
iii. From the OpenWorks Command Menu, select Project > Modify Database Users.
iv. When prompted, enter the dba user and password; for example, system and
<system password>.
c. If the Oracle internal user does not have MANAGE role of the project which will be
upgraded, assign MANAGE_<project name> access to the Oracle internal user.
i. From the OpenWorks Command Menu, select Project > Project Admin.
ii. From the Project Administration dialog menu, select ProjectAdmin > User >
Project Access.
iii. Select all the projects you wish to upgrade and click Manage.
i. From the OpenWorks Command Menu, select Project > Project Admin.
ii. In the Project Administration dialog, select the project you want to upgrade to
OpenWorks 5000.0.0.
iii. From the Project Administration dialog menu, select Project > Project Database.
v. Click Upgrade.
120 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
Note: Before upgrading an OpenWorks project in batch mode, set these two environment
variables first:
5000.0.0.2 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 121
OpenWorks® Software Installation Procedures Landmark
1. In the Oracle 10g database, the UNDO tablespace will replace the old Oracle 8.1.7 RBS
tablespace, and a locally managed TEMP tablespace will replace the old dictionary-managed
tablespace TEMP. If you encounter an error in this step like the examples below, it can be
safely ignored.
"ORARY "
"ORARY "
122 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
"BEGIN
SYS.DBMS_DEFER_IMPORT_INTERNAL.QUEUE_IMPORT_CHECK('OW1214P','SVR4
-b"
"e-8.1.0'); END;"
ORA-23327: imported deferred rpc data does not match GLOBAL NAME
and platform of importing db
ORA-06512: at line 1
3. The following error can be safely ignored. For more information on this Oracle error, contact
Landmark Customer Support and reference Solution Document 140676.
Column 1 @
Column 2 1
Column 3
4. The following errors can be safely ignored. For more information on this Oracle error, please
contact Landmark Customer Support and reference Solution Document 140677.
5000.0.0.2 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 123
OpenWorks® Software Installation Procedures Landmark
Column 1 1
Column 2 MINIMUM
5. The following errors can be safely ignored. For more information on this Oracle error, contact
Landmark Customer Support and reference Solution Document 140758.
124 Appendix: Full Oracle Instance Upgrade: Upgrading an R2003.12 Database 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
This appendix contains the procedures to prepare Linux and Solaris machines for Oracle and
OpenWorks. It also contains other configuration information.
Note: Skip this section if you will use Landmark’s Pre-Oracle utility to create the Oracle user and
set the kernel parameters.
• Log on as root.
• Log on as root.
where /d01/ora10g is the home directory of ora10g, dba is the group name, and 7777 is the uid
(user id)
• Add the following lines to the ora10g .login file, if they do not exist. Use values
appropriate to your setup:
Linux 32-bit
126 Appendix: Prerequisites and Oracle Configurations: Linux & Solaris: Create Oracle User Man-
Landmark OpenWorks® Software Installation Procedures
Linux 64-bit
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Linux & Solaris: Create Oracle
OpenWorks® Software Installation Procedures Landmark
3. Click the Users folder in the Local Users and Groups (Local) pane.
7. In the Description field, type “User created to install Oracle 10g and patch.”
8. In the Password field, type a password that conforms to your organization’s password policy.
For example, 04Apr08.
11.Click Create.
13.In the User Accounts window, select ora10g, then click Properties.
14.Click the Group Membership tab, then click Other, then select Administrators from the list.
128 Appendix: Prerequisites and Oracle Configurations: Windows: Create Oracle User
Landmark OpenWorks® Software Installation Procedures
For 10g R2 (32-bit) on RHEL 5 x86, the document “Oracle Database Installation Guide 10g
Release 2 (10.2) for Linux x86” lists the following required package versions or higher:
binutils-2.17.50.0.6-2.el5
compat-db-4.2.52-5.1
control-center-2.16.0-14.el5
gcc-4.1.1-52.el5
gcc-c++-4.1.1-52.el5
glibc-2.5-12 (i686)
glibc-common-2.5-12
libstdc++-4.1.1-52.el5
libstdc++-devel-4.1.1-52.el5
make-3.81-1.1
sysstat-7.0.0-3.el5
libaio-0.3.106-3.2
Oracle requires approximately 3GB of swap space. Check the swap space using the following
command:
For a host with 2GB of RAM, Oracle suggests 3GB of swap. If the machine has more memory,
the Oracle installer may recommend more swap. If you have at least 3GB of swap space, the
installation will be successful and this message in the installer can be safely ignored. However,
ensure that you have enough swap for your host configuration based on the following table.
The following table describes the relationship between installed RAM and the configured swap
space requirement.
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Linux 32-bit Prerequisites 129
OpenWorks® Software Installation Procedures Landmark
You may need to add swap space. If so, use the procedure in the following example of adding
1GB of swap space on the system. Based on your configuration, calculate how much swap space
you need to add.
1. Determine the size of the new swap file and multiple by 1024 to determine the block size. For
example, the block size of a 1024 MB swap file is 1048576.
2. As root, type the following command in an xterm, with count being equal to the desired block
size:
/sbin/mkswap /swapfile
• To enable the swap file immediately but not automatically at boot time:
/sbin/swapon /swapfile
The next time the system boots, it will enable the new swap file.
4. After adding the new swap file and enabling it, make sure it is enabled by viewing the output
of the command:
Set Shell Limits for the Oracle User on Linux 32-bit Servers
在Linux 32位服务器上设置shell限制条件
To improve the performance of the software on Linux systems, you must increase the following
shell limits for the Oracle user (e.g., ora10g):
3. Depending on the Oracle user's default shell, make the following changes to the default shell
start-up file:
For C shell (csh or tcsh), add the following lines to the /etc/csh.login file:
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Linux 32-bit Prerequisites 131
OpenWorks® Software Installation Procedures Landmark
1. Verify that the kernel parameters shown in the following table are set to values greater than or
equal to the recommended value shown. The procedure following the table describes how to
verify and set the values.
Note: If the current value for any parameter is higher than the value listed in this table, do not
change the value of that parameter.
To view the current value specified for these kernel parameters, and to change them if necessary,
follow these steps:
1. Enter the commands shown in the following table to view the current values of the kernel
parameters:
Note:
Make a note of the current values and identify any values that you must change.
Parameter Command
semmsl, semmns, semopm, and # /sbin/sysctl -a | grep sem
semmni
This command displays the value of the semaphore parameters in
the order listed.
2. If the value of any kernel parameter is different than the recommended value, complete the
following steps:
• Using any text editor, create or edit the /etc/sysctl.conf file and add or edit lines similar to
the following:
Note:
Include lines only for the kernel parameter values that you want to change. For the semaphore
parameters (kernel.sem), you must specify all four values. However, if any of the current
values are larger than the recommended value, specify the larger value.
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144
By specifying the values in the /etc/sysctl.conf file, they persist when you reboot the system.
• Enter the following command to change the current values of the kernel parameters:
# /sbin/sysctl -p
• Review the output from this command to verify that the values are correct. If the values
are incorrect, edit the /etc/sysctl.conf file, then enter this command again.
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Linux 32-bit Prerequisites 133
OpenWorks® Software Installation Procedures Landmark
binutils-2.17.50.0.6-2.el5 (x86_64)
compat-db-4.2.52-5.1 (i386)
compat-db-4.2.52-5.1 (x86_64)
control-center-2.16.0-14.el5 (i386)
control-center-2.16.0-14.el5 (x86_64)
gcc-4.1.1-52.el5 (x86_64)
gcc-c++-4.1.1-52.el5 (x86_64)
glibc-2.5-12 (i686)
glibc-2.5-12 (x86_64)
glibc-common-2.5-12 (x86_64)
libstdc++-4.1.1-52.el5 (x86_64)
libstdc++-4.1.1-52.el5 (i386)
libstdc++-devel-4.1.1-52.el5 (x86_64)
make-3.81-1.1 (x86_64)
sysstat-7.0.0-3.el5 (x86_64)
libaio-0.3.106-3.2 (x86_64)
libaio-0.3.106-3.2 (i386)
1. Verify that you are running the x86_64 kernel on a x86_64 platform:
# uname -mi
Note: It is important to have these x86_64 RPMs installed. The above command will list the
architecture of each binary package. You will see that some RPMs are installed twice when you
run this command (x86 RPM and x86_64 RPM). You must ensure that all required x86-64 RPMs
listed here are installed.
Oracle requires approximately 3GB of swap space. Check the swap space using the following
command:
For a host with 2GB of RAM, Oracle suggests 3GB of swap. If the machine has more memory,
the Oracle installer may recommend more swap. If you have at least 3GB of swap space, the
installation will be successful and this message in the installer can be safely ignored. However,
ensure that you have enough swap for your host configuration based on the following table.
The following table describes the relationship between installed RAM and the configured swap
space requirement.
You may need to add swap space. If so, use the procedure in the following example of adding
1GB of swap space on the system. Based on your configuration, calculate how much swap space
you need to add.
1. Determine the size of the new swap file and multiple by 1024 to determine the block size. For
example, the block size of a 1024 MB swap file is 1048576.
2. At a shell prompt as root, type the following command with count being equal to the desired
block size:
/sbin/mkswap /swapfile
• To enable the swap file immediately but not automatically at boot time:
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Linux 64-bit Prerequisites 135
OpenWorks® Software Installation Procedures Landmark
/sbin/swapon /swapfile
The next time the system boots, it will enable the new swap file.
4. After adding the new swap file and enabling it, make sure it is enabled by viewing the output
of the commands
Set Shell Limits for the Oracle User on Linux 64-bit Servers
在Linux64位服务器上为Oracle用户设置shell限制条件
To improve the performance of the software on Linux systems, you must increase the following
shell limits for the Oracle user (e.g. ora10g):
2. Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:
3. Depending on the Oracle (e.g. ora10g) user's default shell, make the following changes to the
default shell start-up file:
For C shell (csh or tcsh), add the following lines to the /etc/csh.login file:
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Linux 64-bit Prerequisites 137
OpenWorks® Software Installation Procedures Landmark
Verify that the kernel parameters shown in the following table are set to values greater than or
equal to the recommended value shown. The procedure following the table describes how to
verify and set the values.
Note: If the current value for any parameter is higher than the value listed in this table, do not
change the value of that parameter.
To view the current value specified for these kernel parameters, and to change them if necessary,
follow these steps:
1. Enter the commands shown in the following table to view the current values of the kernel
parameters:
Note:
Make a note of the current values and identify any values that you must change.
Parameter 参数 Command 命令
semmsl, semmns, semopm, and # /sbin/sysctl -a | grep sem
semmni
This command displays the value of the semaphore parameters in
the order listed.
2. If the value of any kernel parameter is different than the recommended value, complete the
following steps:
• Using any text editor, create or edit the /etc/sysctl.conf file and add or edit lines similar to
the following:
Note:
Include lines only for the kernel parameter values that you want to change. For the semaphore
parameters (kernel.sem), you must specify all four values. However, if any of the current
values are larger than the recommended value, specify the larger value.
kernel.shmall = 2097152
kernel.shmmax = 2147483648
kernel.shmmni = 4096
kernel.sem = 250 32000 100 128
fs.file-max = 65536
net.ipv4.ip_local_port_range = 1024 65000
net.core.rmem_default = 262144
net.core.rmem_max = 262144
net.core.wmem_default = 262144
net.core.wmem_max = 262144
By specifying the values in the /etc/sysctl.conf file, they persist when you reboot the system.
• Enter the following command to change the current values of the kernel parameters:
# /sbin/sysctl -p
• Review the output from this command to verify that the values are correct. If the values
are incorrect, edit the /etc/sysctl.conf file, then enter this command again.
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Linux 64-bit Prerequisites 139
OpenWorks® Software Installation Procedures Landmark
Note: Skip this section if you will use Landmark’s Pre-Oracle utility to create the Oracle user and
set the kernel parameters.
1. Log on as root.
2. Verify that the kernel parameters shown in the following table are set to values greater than or
equal to the recommended value shown. The table also contains the resource controls that
replace the /etc/system file for a specific kernel parameter.
noexec_user_stack NA 1
Note:
On Solaris 10, you are not required to make changes to the /etc/system file to
implement the System V TPC. Solaris 10 uses the resource control facility for its
implementation.
Use the following procedures to view the current value specified for resource controls, and to
change them if necessary:
To view the current values of the resource control, enter the following commands:
140 Appendix: Prerequisites and Oracle Configurations: Solaris 10 (SPARC) 64-bit Prerequisites
Landmark OpenWorks® Software Installation Procedures
3. Open the /etc/system file in any text editor, and if required, add lines similar to the following
(edit the lines if the file already contains them):
set noexec_user_stack=1
5. As root, add the value of max-shm-memory for the Oracle user, e.g., ora10g:
For a host with 2GB of RAM, Oracle suggests 3GB of swap. If the machine has more memory,
the Oracle installer may recommend more swap. If you have at least 3GB of swap space, the
installation will be successful and this message can be safely ignored.
Ensure that you have enough swap for your host configuration based on the following table. If
you do not have enough swap, exit the installer, create the recommended value of swap space on
the host, and run the installer again.
The following table describes the relationship between installed RAM and the configured swap
space requirement.
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Solaris 10 (SPARC) 64-bit Prereq-
OpenWorks® Software Installation Procedures Landmark
During the installation process, it is good practice to turn off any screen savers or power managers
that might lock the screen or might turn off the system during the installation. Screen savers
which lock the screen can prevent access to a command window, forcing a reboot of the system to
regain control of the system and a restart of the installation. The xlock command in SunOS
and the Screen and Power Managers in Common Desktop Environment (CDE) are examples of
processes which can have a negative effect during installation.
1. In the Front Panel, click the Applications icon to display the Application Manager window.
2. Double-click the Desktop Controls item in the Applications window to display the Application
Manager - Desktop Controls window.
3. Double-click the Style Manager item to display the Style Manager (/usr/dt/bin/dtstyle)
window.
4. Click the Screen icon to display the Style Manager - Screen dialog.
5. Select the Off radio button for the Screen Saver item.
6. Select the Off radio button for the Screen lock item.
7. Click OK.
1. Log on as a user who is able to modify the power management parameters. The parameters that
a user is allowed to change depend upon the contents of the file /etc/default/power . For more
information, see the man page for dtpower (such as /usr/dt/share/man/man1m/dtpower.1m).
/usr/openwin/bin/dtpower &
or
142 Appendix: Prerequisites and Oracle Configurations: Solaris 10 (SPARC) 64-bit Prerequisites
Landmark OpenWorks® Software Installation Procedures
• In the Front Panel, click the Applications icon to display the Application Manager
window.
• Double-click the System Admin item in the Applications window to display the
Application Manager - System Admin window.
3. In the Current Power Saving Scheme, click the down arrow to display the drop-down list.
4. Select Disabled in the list. Selecting this item turns off all power saving activities.
5. Click OK. The new configuration is saved, and the Dtpower dialog closes.
Remember to reset the power management parameters to your preferences after you have finished
all of the installations.
Release 5000.0.0.2Appendix: Prerequisites and Oracle Configurations: Solaris 10 (SPARC) 64-bit Prereq-
Windows:在DHCP计算机中安装Oracle
OpenWorks® Software Installation Procedures Landmark
To check if a loopback adapter is installed on your computer, run the ipconfig /all command:
If there is a loopback adapter installed, you will see a section that lists the values for the loopback
adapter. For example:
4. In the “Is the hardware connected?” window, select “Yes, I have already connected the
hardware” and click Next.
5. In the “The following hardware is already installed on your computer” window, in the list of
installed hardware, select “Add a new hardware device,” and click Next.
6. In the “The wizard can help you install other hardware” window, select “Install the hardware
that I manually select from a list,” and click Next.
7. From the list of hardware types, select the “Type of hardware you are installing” window,
select “Network adapters” and click Next.
144 Appendix: Prerequisites and Oracle Configurations: Windows: Installing Oracle on DHCP
Landmark OpenWorks® Software Installation Procedures
9. Click Next.
10.In the “The wizard is ready to install your hardware” window, click Next.
11.In the “Completing the Add Hardware Wizard” window, click Finish.
13.Right-click My Network Places on the desktop and choose Properties. This displays the
Network Connections Control Panel.
14.Right-click the connection that was just created. This is usually named “Local Area
Connection 2.” Choose Properties.
15.On the General tab, select Internet Protocol (TCP/IP), and click Properties.
16.In the Properties dialog box, click Use the following IP address and do the following:
• IP Address: Enter a non-routable IP for the loopback adapter. Oracle recommends the
following non-routable addresses:
• 10.10.10.10
• Record the values you entered; you will them need later in this procedure.
• Click OK.
17.Click OK.
where:
For example:
• Open System in the Control Panel, and select the Computer Name tab. In Full computer
name, make sure you see the host name and the domain name, for example,
sales.us.mycompany.com.
• Click Change. In Computer name, you should see the hostname, and in Full computer
name, you should see the host name and domain name. Using the previous example, the
host name would be sales and the domain would be us.mycompany.com.
• Click More. In Primary DNS suffix of this computer, you should see the domain name, for
example, us.mycompany.com.
146 Appendix: Prerequisites and Oracle Configurations: Windows: Installing Oracle on DHCP
Landmark OpenWorks® Software Installation Procedures
Note: The steps in this section are not necessary if you installed Oracle and OpenWorks using the
instructions in this manual to install and configure Oracle, the OpenWorks database, and
OpenWorks.
Overview 简介
Prior to Release 5000.0.0, Landmark stored passwords in an encrypted file in the user’s home
directory. Landmark now uses an Oracle utility called “Oracle Secure Password Store” or “Oracle
Wallet” for this purpose. The primary advantage of this scheme is that “Oracle Wallet” is tightly
integrated with Oracle itself. Once a wallet is configured you can connect to any Oracle utility or
from any client program with a blank user name. The first time you run an OpenWorks program
against an Oracle instance you will be prompted for a password. The password will be stored in
the wallet and you will not be prompted again. There is also a “Change Password” option on the
“Project Menu” where users can change their own password. This will store the new password in
the wallet. This change improves the security of the overall system.
The OpenWorks user must set the OW_HOME_DIR environment variable; for example:
OW_HOME_DIR=C:\Landmark\OpenWorks\users\hbl9999. This is typically set to your home
directory and it controls the location of the wallet file. In a standard install it will be set in
.lgclogin or by the installer on Windows. Make sure that the OW_HOME_DIR exists and does
not contain any spaces in it.
Make sure the $ORACLE_HOME/network/admin/sqlnet.ora file contains the text shown below.
This new environment variable is necessary because Oracle Wallet will not work if there are
spaces in the directory path. If there are spaces in your home directory path choose another
location.
On Windows
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
(DIRECTORY=%OW_HOME_DIR%\wallet)
)
)
SQLNET.WALLET_OVERRIDE= TRUE
On Linux/Solaris
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
(DIRECTORY=${OW_HOME_DIR}/wallet)
)
)
SQLNET.WALLET_OVERRIDE= TRUE
Notes
• Once cached in the wallet password will not expire. Password prompts will not occur in
batch applications. Once the password is set it will not expire unless the underlying Oracle
password changes. However, to ensure that no GUI is set, then set the environment
variable OW_NO_PASSWORD_DIALOG=TRUE.
• Users are able to connect as “sqlplus /@sidname” (Note: The / means check that correct
credential exists in wallet) as well as “sqlplus usename/password@sidname”
The OpenWorks Database installer uses OW_HOME_DIR when creating an Oracle wallet for the
Oracle owner account. The installer will also automatically configure sqlnet.ora as described
above. Then sqlnet.ora is configured. To enable Oracle wallet support, the Oracle owner must
have a wallet.
If you create a default district.dat during the install, the directory will be
“__Directory_Is_Not_Set_Yet__” instead of $OWHOME/conf. This simplifies diagnosing a
problem with the district.dat.
If you leave the directory as $OWHOME/conf, while it is a valid directory, it typically is not the
correct location for the dir.dat for seismic data. The default owdir.dat is still created in
$OWHOME/conf. This means that OpenWorks flat file access will not function correctly. Even if
you are not using SeisWorks you must edit district.dat and set the directories to the location of
owdir.dat.
Appendix: Troubleshooting
附录:排错
Background 背景
In OpenWorks 5000.0.0 the Oracle wallet functionality is used to store internal Oracle passwords.
Wallet entries in the sqlnet.ora file will cause the Oracle dbca utility to function improperly, and
you may not be able to delete or create a second SID on an OpenWorks server.
Repeat the workaround steps for each SID you need to delete or add.
mkdir -p /d01/ora10g/temp/network/admin
cp $ORACLE_HOME/network/admin/sqlnet.ora /d01/ora10g/temp/network/admin
cp $ORACLE_HOME/network/admin/tnsnames.ora /d01/ora10g/temp/network/
admin
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
(DIRECTORY=${OW_HOME_DIR}/wallet)
)
)
SQLNET.WALLET_OVERRIDE= TRUE
6. Set the TNS_ADMIN environment variable to point to the new directory, e.g.,
7. Run the Oracle dbca utility and delete the existing database.
mkdir -p /d01/ora10g/temp/network/admin
cp $ORACLE_HOME/network/admin/sqlnet.ora /d01/ora10g/temp/network/admin
cp $ORACLE_HOME/network/admin/tnsnames.ora /d01/ora10g/temp/network/
admin
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
(DIRECTORY=${OW_HOME_DIR}/wallet)
)
)
SQLNET.WALLET_OVERRIDE= TRUE
6. Set the TNS_ADMIN environment variable to point to the new directory, e.g.,
7. Verify that the OW_HOME_DIR environment variable is already set to the existing wallet
subdirectory that was created by the first instance, e.g.,
echo $OW_HOME_DIR
If the OW_HOME_DIR environment variable is not set, set it the appropriate directory where
the wallet exists for the Oracle user, e.g.,
8. Set the ORACLE_SID to the new value that you want to create, e.g.,
9. Run the OpenWorksDatabaseInstaller and create the instance. However, when prompted, do
not automatically restart the instance and listener even though it is recommended. Choose to
restart manually.
10.Copy the entry for the newly created instance in $TNS_ADMIN/tnsnames.ora to the master
tnsnames.ora file in $ORACLE_HOME/network/admin/tnsnames.ora., i.e.,
OWTEST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = <hostname>.lgc.com)(PORT =
1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = owtest)
)
)
unsetenv TNS_ADMIN
rm -rf /d01/ora10g/temp/network/admin
sqlplus system/system@owtest
15.If there are any connection problems, try connecting with the full host name, port number and
alias:
sqlplus system/system@hostname:portnumber/alias
For example,
e.g., system/system@<hostname>.lgc.com:1521/owtest
If this connection attempt succeeds there may be something wrong with the entry in the
tnsnames.ora file.
Adobe Reader
On Solaris, Acrobat Reader version 7 comes with the operating system so it is not necessary to
install the reader.
However, if you upgrade to Acrobat Reader version 8.1.1, you may encounter GTK errors which
prevent the reader from launching. This is a known Acrobat issue.
The 8.x Readers require a minimum 2.6 GTK level. Solaris 10 OCT contains GTK 2.4.x.
Therefore, if you must install an 8.x Reader, you must patch to GTK 2.6 or hiher.
By default, Solaris 10 comes bundled with GTK 2.4.9, whereas Adobe Reader 8.1.1 requires a
minimum GTK version 2.6 to run properly (refer point 5 on the Known Issues Page). So if you
try to run acroread on such a system you may observe a host of GTK related warnings on the
console and acroread may not launch. To fix this issue, you can update the GTK version on the
Solaris machine (read the steps below for one way in which the GTK libraries can be updated
easily).
1. You need pkg-get on your system. If you do not have pkg-get, you can install it using the
following command:
pkgadd -d http://www.blastwave.org/pkg_get.pkg
2. Edit the pkg-get configuration file in order to download from the nearest mirror (blastwave.org
lists all mirrors at: http://www.blastwave.org/mirrors.php)
vi /opt/csw/etc/pkg-get.conf
3. Install the wget package (along with all its dependencies) using pkg-get
/opt/csw/bin/pkg-get -i wget
/opt/csw/bin/pkg-get -i gtk2
export LD_LIBRARY_PATH=/opt/csw/lib:$LD_LIBRARY_PATH
PS: The above listed method is just one way of updating the GTK libraries, and other methods
may exist. Irrespective of the method used, before launching acroread, remember to set the
LD_LIBRARY_PATH appropriately to the directory which contains the correct GTK libraries.
Red Hat Linux has a number of viewers for PDF files. In the Gnome desktop, Linux has gv,
ggv, and xpdf. In the K Desktop Environment (KDE), Linux has kghostview. Each viewer
is available from the command line, and xpdf and kghostview are available from the
Gnome panel. For example, to start xpdf:
To start kghostview:
Main Menu > Programs > KDE menus > Graphics > PS/PDF Viewer
These viewers usually display PDF files adequately, but they do not have all of the features of
Acrobat Reader and are not used by Landmark Graphics applications. Among many differences,
these viewers do not have a bookmark pane, or if a viewer does have a bookmark pane, the viewer
does not recognize the named bookmarks, which allow the bookmark pane to act as a table of
contents to the document.
To be able to double-click an Acrobat file (PDF) and open it with Acrobat Reader, do the
following:
1. Select Main Menu > Programs > Settings > File Types and Programs in the Gnome Panel.
The File Types And Programs dialog opens.
2. In the list box, select the line with PDF document in the Description column.
4. Click Add Application in the Add Application List dialog. The Edit Application dialog opens.
• In Application Command, enter the path name for acroread . Assuming a location of
Acrobat Reader,
/usr/local/Acrobat5 , you would enter:
/usr/local/Acrobat5/bin/acroread
• Check both check boxes: Can Open Multiple Files, and Can Open From URI.
6. Click OK in the Add Application and the Edit Application List dialogs.
7. In the Default Action group box of the Files Types And Programs dialog, select the Open With
Application radio button.
8. Also in the Default Action box, click the Arrows button to display a list of names of
applications, and select the name you entered in the Application Name text box in Step 5.
10.In Red Hat Enterprise Linux 5.0, set the LANG environment variable to C in your shell
initialization file. For example, in the Bash shell, you would include the following line in the
file:
LANG=C
To insert an Acrobat Reader item in the menu of the Gnome panel, do the following:
3. In the tree in the left list box, choose the name of a menu (branch) from which you want to be
able to start Acrobat Reader. For instance, you might choose the menus: Programs (System
Menus), and then the Applications submenu.
4. Select File >New Item. A untitled item (leaf) appears at the bottom of the list of items for the
menu, and default tabs appear on the right.
Acrobat Reader 7
• In Comment, you may enter information about the item, but a comment is not required.
The comment appears in a pop-up when the menu is displayed, and your mouse cursor
hovers over the item.
• In Command, enter the full path name for acroread . For example:
/usr/local/Acrobat5/bin/acroread &
—Browse for an icon file. For example, an icon file for Acrobat Reader
( acroread.png ) is located in the following directory:
/usr/share/icons/hicolor/32x32/apps
7. If you want the new item somewhere else in the menu, you can drag and drop the item to a new
location, or you can use the Move Up and Move Down tool bar buttons to move the selected
item to a new location in the menu.
8. In Red Hat Enterprise Linux 5.0, set the LANG environment variable to C in your shell
initialization file. For example, in the Bash shell, you would include the following line in the
file:
LANG=C
After installing Adobe Reader in Linux, you may see the following error :
It doesn't appear to stop until you use the kill command in another terminal window.
To fix it, you must edit ReaderHome/bin/acroread. Basically, a line just needs an asterisk.
The default for file process limits vary from operating system to operating system; however, some
limits on some systems have posed a problem for the applications that use the OpenWorks
database and for Oracle itself. Generally, it is best to give these process (and the users of the
system) unlimited resources or up to the hard limits for the system.
All systems have hard and soft limits. If the hard limits are too low, a user of OpenWorks may or
may not have a resource. Some system limits may have been set by the system administrator to
keep the system within parameters important in the system environment, but which can still be
raised. Other limits may be the actual limits of the system and cannot be raised. Only a user with
root privileges can change hard limits.
On Solaris, some limits can be changed with the ulimit command. However, on Solaris it is
sometimes best to change the kernel settings in /etc/system .
For information about any concerns about process limits for a Landmark application, see the
documentation for the application. For more information on the system commands or changing
the system, consult the documentation for the operating system.
For instance, on a Solaris system the number of file descriptors for a user (the soft limit) maybe
set at sixty-four; however, the hard limit for the system maybe set at 1024. To set the soft limit to
the hard limit, do the following:
csh (Solaris)
or
160 Appendix: Troubleshooting: Linux & Solaris: Process Resource Limits Release 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
sh (Solaris)
ulimit -n 1024
These commands can be executed at the command line in a terminal window to configure a shell
or can be entered in .profile or .login to configure the user’s environment.
Oracle and OpenWorks can manipulate very large files on the order of two gigabytes or more.
When users of OpenWorks back up projects, the backup files can be hundreds of megabytes or
even gigabytes. If the operating system imposes a limit on the file size that is too small,
OpenWorks may incur an error and not be allowed to back up or restore a project.
Limits on processes, especially the file size allowed on the system, can be defined by a number of
means: hard limits, set in the kernel of the operating system or by the configurations of the system
administrator; and soft limits, which can be set by the user. Generally, a user is able to change soft
limits, and may lower hard limits for his account, but a user is not allowed to raise hard limits.
Besides allowing you to changed the limits on the system, the ulimit command can display
the current limits on the system. For instance on Solaris, the ulimit command displays all the
hard limits (the a switch displays all the limits, and the H switch displays the hard limits):
# ulimit -aH
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) 1024
memory(kbytes) unlimited
The command can display all the soft limits (the a switch displays all the limits, and the S
switch displays the soft limits):
# ulimit -aS
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 8192
coredump(blocks) unlimited
nofiles(descriptors) 256
memory(kbytes) unlimited
The set of limits differ from operating system to operating system: Solaris to Linux and Linux to
Solaris, and the values of the limits can differ from implementation to implementation of an
operating system.
Release 5000.0.0.2 Appendix: Troubleshooting: Linux & Solaris: Process Resource Limits 161
OpenWorks® Software Installation Procedures Landmark
As indicated above, the limits on file size ( file (blocks) ) are set to unlimited. In this
case, the hard and soft limits are the same. If the soft limit were lower than the hard limit (lower
than 2 gigabytes for example), the ulimit command would allow you to raise the file size
limit to the hard limit as the file descriptors limits were raised in the section above, “Changing a
Process Resource Limit with ulimit (or limit)” on page 160.
162 Appendix: Troubleshooting: Linux & Solaris: Process Resource Limits Release 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
Use the procedures in this appendix to uninstall Oracle server and then to uninstall OpenWorks.
Sometimes before installing Oracle you may want to completely remove all vestiges of a previous
installation of Oracle. The steps in this section will guide you through the process of completely
removing Oracle Server.
• All data in the database has been backed up in a location other than the database.
• You have backed up certain other files such as SQL configuration files, database files, and
scripts you have written. These files may be stored in Oracle’s home directory as well as
other places.
Warnings 注意事项
Some of the steps in this procedure can cause trouble for the operating system if they are
performed incorrectly or incompletely.
• Aborting the uninstall procedure in the middle of the procedure may leave the system in
an undetermined condition.
• Some of the steps (such as removing a home directory or user) must be executed as Super
User. There is no undo for these steps.
Release 5000.0.0.2 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server 163
OpenWorks® Software Installation Procedures Landmark
2. Run orastat . Note the data file and project locations. You may need to know these
location if the Oracle Universal Installer does not remove these data files. The data file and
project locations might look similar to the following:
6. Check that no users are logged into the Oracle database instances. For example, you might
execute the following with SQL*Plus (sqlplus):
164 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server Release 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
This command will display all of the active users of the database which include the Oracle
processes like pmon, dbw0, lgwr, ckpt, smon, reco, snp0, and snp1 as well as
system (the user name logged into sqlplus in this case).
If you see other users listed in the command’s output, ask them to log out of Oracle before
continuing with the next step.
7. Remove the database instances with dbca (the Oracle Database Configuration Assistant).
$ORACLE_HOME/bin/dbca
• Click Next.
• In the Available Instances list box, select all the names in the list box.
• To delete all of the database files (and all the data in the database), click Finish.
8. In a terminal window, check whether any database processes are still running. For example:
Release 5000.0.0.2 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server 165
OpenWorks® Software Installation Procedures Landmark
lsnrctl stop
11.Use the Oracle Universal Installer to remove the Oracle software. For example:
$ORACLE_HOME/bin/runInstaller
• In the list box, click the plus signs next to the Independent Products and /d01/ora10g/
OraHome1 items in the list.
• Check the boxes in the lines for Oracle Universal Installer, Oracle Enterprise Edition, and
OpenWorks database.
12.Exit from the Oracle user account. For example, enter Exit in the terminal window.
• Remove any remaining project and data files and directories (as noted in step 2).
• Remove oraInst.loc (contains the group and inventory location), and oratab
(lists of the databases on the system). For example:
rm –rf OracleUserHomeDir
166 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server Release 5000.0.0.2
Landmark OpenWorks® Software Installation Procedures
cd /usr/local/bin
rm –f coraenv dbhome oraenv
15.With a text editor (such as vi), delete the line for the Oracle user (oracle) in /etc/passwd
and the line for the DBA group (dba) in /etc/group . Alternatively, in Linux, use the Red
Hat User Manager ( /usr/bin/redhat-config-users ) to delete the Oracle user and
DBA group.
16.It is good practice, but not required, to reboot your operating system.
Release 5000.0.0.2 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server 167
OpenWorks® Software Installation Procedures Landmark
The procedure outlined below will delete anything in the OpenWorks home directory (as well as
other files), including any other applications or files installed in the OpenWorks directory.
1. Log on as root.
OWHOME=/Landmark/programs/OpenWorks
export OWHOME
3. Stop the NetD, PD, and license manager processes. Enter the following commands in the
OpenWorks home directory:
./bin/stop_pd
./bin/stop_netd
./lam/bin/stoplmgrd
4. Run owremove , located in the install subdirectory in the OpenWorks home directory. For
example:
/Landmark/programs/OpenWorks/install/owremove
5. After owremove has finished, delete the OpenWorks home directory if it still exists. For
example:
rm -rf /Landmark/programs/OpenWorks