OpenWorks SoftwareInstallation Procedures

OpenWorks® Software
Installation Procedures
© 2008 Landmark Graphics Corporation
Release 5000.0.0.3 September 2008

© 2008 Landmark Graphics Corporation
All Rights Reserved Worldwide
This publication has been provided pursuant to an agreement containing restrictions on its use. The publication is also protected by Federal
copyright law. No part of this publication may be copied or distributed, transmitted, transcribed, stored in a retrieval system, or translated
into any human or computer language, in any form or by any means, electronic, magnetic, manual, or otherwise, or disclosed to third parties
without the express written permission of:
Landmark Graphics Corporation

2107 CityWest Blvd, Building 2, Houston, Texas 77042-3021, USA
P.O. Box 42806, Houston, Texas 77242, USA
Phone: 713-839-2000
Fax: 713-839-2401
Internet: www.halliburton.com/landmark
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 Solutions, Asset Development Center, AssetDirector, Asset Journal,
AssetLink, AssetLink Advisor, AssetLink Director, AssetLink Observer, AssetObserver, AssetObserver Advisor, Asset Performance, AssetPlanner,
AssetSolver, AssetSolver Online, AssetView, BLITZPAK, CasingLife, CasingSeat, COMPASS, Corporate Data Archiver, Corporate Data Store,
Data Analyzer, DataManager, DataStar, DBPlot, Decision Management System, DecisionSpace, DecisionSpace 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 Infrastructure,
DecisionSpace Nexus, DecisionSpace PowerModel, DecisionSpace PrecisionTarget, DecisionSpace Reservoir, DecisionSpace TracPlanner,
DecisionSpace Well Seismic Fusion, DecisionSpace WellSolver, DecisionSuite, DepthTeam, Depth Team, DepthTeam Explorer, Depth Team
Explorer, DepthTeam Express, Depth Team Express, DepthTeam Extreme, Depth Team Extreme, DepthTeam Interpreter, Depth Team Interpreter,
Desktop Navigator, DESKTOP-PVT, DESKTOP-VIP, DEX, DIMS, Discovery, Discovery Asset, Discovery FrameBuilder, DMS, Drillability Suite,
Drilling Desktop, DrillModel, Drill-to-the-Earth Model, DrillWorks, DSS, Dynamic Reservoir Management, Dynamic Surveillance System,
EarthCube, EDM, EDT, eLandmark, Engineer’s Data Model, Engineer's Desktop, Engineer’s Link, ESP, Event Similarity Prediction, ezFault,
ezModel, ezSurface, ezTracker, FastTrack, FG+, FieldPlan, Field Scenario Planner, FZAP!, GeoAtlas, GeoDataLoad, GeoGraphix, GeoGraphix
Exploration System, GeoLink, GeoProbe GF DataServer, GES, GES97, GESXplorer, GMAplus, GMI Imager, GRIDGENR, Handheld Field
Operator, HHFO, I2 Enterprise, iDIMS, IsoMap, iWellFile, i Wellfile, KnowledgeSource, Landmark, Landmark Decision Center, Landmark &
Design, Landmark Logo and Design, Landscape, Lattix, LeaseMap, LMK Resources, LogEdit, LogM, LogPrep, Make Great Decisions, MathPack,
MIMIC, MIMIC+, Model Builder, MyLandmark, Nexus, Object MP, OpenBooks, OpenJournal, OpenSGM, OpenVision, OpenWells, OpenWire,
OpenWorks, OpenWorks Development Kit, OpenWorks Well File, OpenWorks Production, PAL, Parallel-VIP, PetroBank, PetroBank Explorer,
PetroBank Master Data Store, PetroWorks, PetroWorks Asset, PetroWorks Pro, PetroWorks ULTRA, PlotView, Point Gridding Plus, Pointing
Dispatcher, PostStack, PostStack ESP, PostStack Family, PowerCalculator, PowerExplorer, PowerExplorer Connect, PowerGrid, PowerHub, Power
Interpretation, PowerJournal, PowerModel, PowerView, PrecisionTarget, Presgraf, PressWorks, PRIZM, Production Asset Manager, Production,
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+, QUIKRAY, QUIKSHOT, QUIKVSP, RAVE, RAYMAP, RAYMAP+, Real Freedom, Real Time Asset Management Center, Real Time
Decision Center, Real Time Operations Center, Real Time Production Surveillance, Real Time Surveillance, Real-Time View, Reference Data
Manager, Reservoir Framework Builder, RESev, ResMap, RightTime, RTOC, SCAN, SeisCube, SeisMap, SeisModel, SeisSpace, SeisVision,
SeisWell, SeisWorks, SeisWorks 2D, SeisWorks 3D, SeisWorks PowerCalculator, SeisWorks PowerJournal, SeisWorks PowerSection, SeisWorks
PowerView, SeisXchange, Semblance Computation and Analysis, Sierra Family, SigmaView, SimConnect, SimConvert, SimDataStudio,
SimResults, SimResults+, SimResults+3D, SIVA+, SLAM, smartSECTION, Spatializer, SpecDecomp, StrataAmp, StrataMap, StrataModel,
StrataSim, StrataWorks, StratWorks, StratWorks 3D, StreamCalc, StressCheck, STRUCT, Structure Cube, Surf & Connect, SynTool, SystemStart,
SystemStart for Clients, SystemStart for Servers, System Start 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, TracPlanner Xpress, 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, Well Cost,
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.
Release 5000.0.0.3 ii
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 Linux or Solaris
%OWHOME%\docs\third_party.pdf Windows
Release 5000.0.0.3 iii

Release 5000.0.0.3 iv
Landmark OpenWorks® Software Installation Procedures
Contents
Contents
Introduction
Welcome to the OpenWorks® Software ........................................................................................ 1
Before You Begin .......................................................................................................................... 2
New District Functionality ................................................................................................. 3
System Requirements .................................................................................................................... 4
Minimum Platform Specifications ..................................................................................... 4
Default Minimum OpenWorks Project Size ...................................................................... 4
Graphics Cards ................................................................................................................... 4
Software Specfications ...................................................................................................... 4
Licensing ........................................................................................................................................ 5
Third Party Applications License Agreements .............................................................................. 5
Accessing the OpenWorks Documentation ................................................................................... 6
Online Help ........................................................................................................................ 6
Documents in Portable Document Format (PDF) Format ................................................. 6
Installing Acrobat Reader ............................................................................................ 6
Version 5000.0.0.3 Contents v

OpenWorks® Software Installation Procedures Landmark
Quick Start
Installation Workflow .................................................................................................................... 7
Installation Checklist: All Platforms .............................................................................................. 8
Oracle Installation
Linux 32-bit Server ...................................................................................................................... 11
Prerequisites and Procedures ........................................................................................... 11
Run Pre-Oracle: Linux 32-bit Server ............................................................................... 12
Modify the Linux 32-bit Release File .............................................................................. 13
Install Oracle Database Software (10.2.0.1.0) ................................................................. 13
Install Oracle 10g Release 2 Patch Set 2 (10.2.0.3.0) ...................................................... 15
Fix Directory Permission Problem .................................................................................. 16
Restore Linux Release File .............................................................................................. 17
Install OpenWorks 5000.0.0 Database ............................................................................ 17
Install OpenWorks 5000.0.0 Database Schemas on an Existing Oracle Database .......... 20
What’s Next? ................................................................................................................... 23
Linux 32-bit Client ....................................................................................................................... 24
Run Pre-Oracle: Linux 32-bit Client ............................................................................... 24
Install Oracle Client Software (10.2.0.1.0) ...................................................................... 26
What’s Next? ................................................................................................................... 29
vi Contents Version 5000.0.0.3

Linux 64-bit Server ...................................................................................................................... 30
Run Pre-Oracle: Linux 64-bit Server ............................................................................... 30
What’s Next? ................................................................................................................... 42
Linux 64-bit Client ....................................................................................................................... 43
Run Pre-Oracle: Linux 64-bit Client ............................................................................... 43
What’s Next? ................................................................................................................... 48
Solaris 10 (SPARC) 64-bit Server ............................................................................................... 49
Run Pre-Oracle: Solaris 64-bit Server ............................................................................. 49
Version 5000.0.0.3 Contents vii

What’s Next? ................................................................................................................... 60
Solaris 10 (SPARC) 64-bit Client ................................................................................................ 61
Run Pre-Oracle: Solaris 64-bit Client .............................................................................. 61
What’s Next? ................................................................................................................... 65
Windows XP/2003 SP2 32-bit Server ......................................................................................... 67
Install Oracle 10g Software Patch 2 (10.2.0.3.0) ............................................................. 68
What’s Next? ................................................................................................................... 74
Windows XP/2003 SP2 32-bit Client .......................................................................................... 75
Install Oracle Client Software 32 bit (10.2.0.1.0) ............................................................ 75
Install Oracle 10g Patch Set 2 32 bit (10.2.0.3.0) ............................................................ 77
What’s Next? ................................................................................................................... 78
Windows 2003 SP2 64-bit Server ................................................................................................ 79
viii Contents Version 5000.0.0.3

Install Oracle Database Software 64 bit (10.2.0.1.0) ....................................................... 79
Install Oracle 10g Software Patch 2 64 bit (10.2.0.3.0) ................................................... 80
Install Oracle Client Software 32 bit (10.2.0.1.0) ............................................................ 81
Install Oracle 10g Patch Set 2 32 bit (10.2.0.3.0) ............................................................ 83
Install Windows 2003 SP2 32-bit Client ......................................................................... 89
What’s Next? ................................................................................................................... 89
OpenWorks Installation
Before Installing on Linux & Solaris ........................................................................................... 90
Before Installing on Windows ..................................................................................................... 90
Install OpenWorks ....................................................................................................................... 93
What’s Next? ................................................................................................................... 96
Post-Installation
Overview ...................................................................................................................................... 97
Linux Only ................................................................................................................................... 98
64-bit Servers: Install an Additional Library ................................................................... 98
64-bit Servers: Selinux ..................................................................................................... 98
Linux & Solaris ............................................................................................................................ 99
Linux & Solaris Clients: Create a Local OS User ........................................................... 99
Linux & Solaris Servers: Update Users ........................................................................... 99
Linux & Solaris LAM Servers: Update OS Users’ .lgclogin .......................................... 99
Linux & Solaris Servers and Clients: Run owsetup Script .............................................. 99
Version 5000.0.0.3 Contents ix

All Platforms .............................................................................................................................. 101
Grant Database Access to the OpenWorks User ............................................................ 101
Change Default Passwords ............................................................................................ 102
AutoExtend is on by Default for SYSTEM and Project Table Spaces .......................... 102
Windows .................................................................................................................................... 103
Windows Servers and Clients: Oracle Wallet and Multiple Users ................................ 103
Configure the MKS Toolkit and Hummingbird Exceed ................................................ 104
District Configuration ................................................................................................................ 105
A Brief Overview of the District Concept ..................................................................... 105
Is Configuration Necessary? .......................................................................................... 105
GeoDataLoad Installation
Uninstall Previous Versions of GeoDataLoad ........................................................................... 106
Windows ........................................................................................................................ 106
Linux or Solaris ............................................................................................................. 106
Install GeoDataLoad .................................................................................................................. 106
Upgrading the OpenWorks Software
Upgrading to Version 5000.0.0.3 ............................................................................................... 109
Installing the New Version of the Software ................................................................... 109
Upgrading the Projects in the OpenWorks Database ..................................................... 110
Upgrading One Project Database ............................................................................. 110
Upgrading All Project Databases in an OpenWorks Database ................................ 111
Upgrading Multiple Projects With Project Administration ..................................... 111
Post Installation Steps for Linux and Solaris ................................................................. 111
Update the User Profile (launcher.dat and .lgclogin) .............................................. 111
x Contents Version 5000.0.0.3

Appendix: Upgrade OpenWorks Instance
Before Upgrading ...................................................................................................................... 113
Differences in the Oracle Databases .............................................................................. 113
Assumptions for Uprgrading ......................................................................................... 113
Upgrade Workflow .................................................................................................................... 114
Pre Migration Steps ....................................................................................................... 114
Upgrading to Version 5000.0.x .................................................................................................. 115
Preparing the R2003.12 Database for Export ................................................................ 115
Exporting the Database from OpenWorks R2003.12 .............................................. 118
Procedures in the OpenWorks 5000.0.0 Runtime Environment ............................. 119
Possible Errors During the Import ........................................................................... 126
Appendix: Prerequisites & Configurations
Creating an Oracle User ............................................................................................................. 130
Solaris and Linux ........................................................................................................... 130
Create Oracle User ......................................................................................................... 132
Linux 32-bit Prerequisites .......................................................................................................... 133
Check Software Packages (RPMs) on Linux 32-bit Servers and Clients ...................... 133
Check Swap Space on Linux 32-bit Servers .................................................................. 133
Set Shell Limits for the Oracle User on Linux 32-bit Servers ....................................... 135
Configure Kernel Parameters on Linux 32-bit Servers ................................................. 136
Linux 64-bit Prerequisites .......................................................................................................... 138
Check Software Packages (RPMs) on Linux 64-bit Servers and Clients ...................... 138
Check Swap Space on Linux 64-bit Servers .................................................................. 139
Set Shell Limits for the Oracle User on Linux 64-bit Servers ....................................... 141
Version 5000.0.0.3 Contents xi

Configure Kernel Parameters on Linux 64-bit Servers ................................................. 142
Solaris 10 (SPARC) 64-bit Prerequisites ................................................................................... 144
Configure Kernel Parameters on Solaris 10 Servers ..................................................... 144
Check Swap Space on Solaris 10 Servers ...................................................................... 145
Disable Screen and Power Managers on Solaris 10 ...................................................... 146
Disabling the Screen Manager in CDE .................................................................... 146
Disabling the Power Manager in CDE .................................................................... 146
Windows: Installing Oracle on DHCP Computers .................................................................... 148
Prerequisites for Installing Oracle on DHCP Computers .............................................. 148
Check if a Loopback Adapter is Installed on the Computer .................................... 148
Installing a Loopback Adapter on Windows 2003 or Windows XP ........................ 148
Appendix: About Oracle Wallet
Overview .................................................................................................................................... 151
Environment Changes ................................................................................................................ 151
OpenWorks Database Installer Configures Oracle Wallet ...................................... 153
OpenWorks Installation and sqlnet.ora on Client Machines ................................... 153
Appendix: Troubleshooting
Deleting or Creating a Second SID ............................................................................................ 155
Background .................................................................................................................... 155
Workaround to Delete an Existing Instance .................................................................. 155
Workaround to Create an Additional OpenWorks Instance .......................................... 156
Adobe Reader ............................................................................................................................ 159
Possible GTK Errors on Solaris ..................................................................................... 159
Linux: Other Readers ..................................................................................................... 160

xii Contents Version 5000.0.0.3
Linux: Opening Acrobat Files in the Nautilus File Manager ........................................ 160
Linux: Running Acrobat Reader from the Gnome Panel .............................................. 161
Possible Syntax Error in Linux ...................................................................................... 163
Linux & Solaris: Process Resource Limits ................................................................................ 164
Changing a Process Resource Limit with ulimit (or limit) .............................. 164
Large Files ..................................................................................................................... 165
Appendix: Removing Oracle & OpenWorks
Removing Oracle Server ............................................................................................................ 167
Warnings ........................................................................................................................ 167
Deleting Oracle 10g ....................................................................................................... 168
Removing OpenWorks Server ................................................................................................... 172
Version 5000.0.0.3 Contents xiii

xiv Contents Version 5000.0.0.3

Introduction
Welcome to the OpenWorks® Software
Welcome to the OpenWorks® software, Landmark® Graphics Corporation’s database for access by
Landmark’s integrated suite of applications to data for the oil and gas industry.
This guide will help you install and configure the server and client of Oracle 10g version
10.2.0.3.0 and OpenWorks on the following operating systems:
• Red Hat Enterprise Linux 5.0, 32-bit
• Red Hat Enterprise Linux 5.0, 64-bit
• Solaris 10 (SPARC), 64-bit
• Windows XP/2003, 32-bit
• Windows XP/2003, 64-bit
Use the instructions in “Quick Start” on page 7 to install on all of these platforms.
Upgrading Version 5000.x
For upgrading a previous installation of version 5000.0.0.x to the current version, see “Upgrading the
OpenWorks Software” on page 109.
Version 5000.0.0.3 Introduction: Welcome to the OpenWorks® Software 1

Before You Begin
All applications in Landmark’s Release 5000.0.0 require the version 5000.0.0.0 of the
OpenWorks® data model, or greater. The basic steps to move data from previous releases of the
OpenWorks software to Release 5000.0.0 are:
• If necessary, back up the projects with the backup function of the Project Administration
utility of the OpenWorks software R2003.x.
• Install Oracle 10g and the Oracle patches required for the operating system.
• Install version 5000.0.0.x. of the OpenWorks software.
• Restore 2003.x projects with the restore function of the Project Administration utility in
version 5000.0.0.x of the OpenWorks software.
• Upgrade projects to the version 5000.0.0.x database schema with the upgrade function of
the Project Administration utility.
An upgrade in-place method is not available in version 5000.0.0.x of the OpenWorks software,
because Release 5000.0.0 requires a new version of the Oracle Database Management System.
However, “Appendix: Upgrade OpenWorks Instance” on page 113 contains a procedure for
moving your data to version 5000.0.0 of the OpenWorks database.
Use the Upgrade function of Project Administration to upgrade a project database of any version
since R1998 of the OpenWorks software 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 data from the SeisWorks® software. 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).
2 Introduction: Before You Begin Version 5000.0.0.3

New District Functionality
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
district-related configuration required.
Version 5000.0.0.3 Introduction: Before You Begin 3

System Requirements
Minimum Platform Specifications
Platform Operating Systema Processorb RAM Swapc
Linux (64 bit) Red Hat Enterprise Linux 5.0 X86_64 512 Mb 1 Gb
Solaris Sun Solaris 10 64-bit SPARC 512 Mb 1 Gb
Windows 32-bit Microsoft Windows XP & IA32, X86_64 512 Mb 1 Gb

Microsoft Windows 2003 Server 32-bit
Windows 64-bit Microsoft Windows XP & X86_64 512 Mb 1 Gb
Microsoft Windows 2003 Server 64-bit
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.
Default Minimum OpenWorks Project Size
The default small size for a project in OpenWorks 5000.0.0 is 300 Mb.
Graphics Cards
NVIDIA Quadro FX family of cards
Software Specfications
All platforms:
• 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:
Hummingbird Exceed 2007, except for the installation of OpenWorks Basic

4 Introduction: System Requirements Version 5000.0.0.3
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 can install LAM on a client machine, or as a license server.
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 Release Notes
• at the location defined on page iii in the .pdf manuals
• in the online Help
Version 5000.0.0.3 Introduction: Licensing 5

Accessing the OpenWorks Documentation
The help capability of Landmark Graphics applications assumes an installation of a web browser
and Acrobat Reader.
Online Help
Some of the OpenWorks documentation is available in a platform-independent html format. A

web browser meeting the specifications listed earlier in this chapter is required to view the
OpenWorks Online Help (ow_online_help.html).
Documents in Portable Document Format (PDF) Format
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.
Installing Acrobat Reader
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.
Installing on Windows
Simply download the reader from Adobe’s web site. No configuration is necessary.
Installing on Linux & Solaris
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 .
6 Introduction: Accessing the OpenWorks Documentation Version 5000.0.0.3

Quick Start
Use the steps in this chapter to install Oracle, OpenWorks, and GeoDataLoad with minimal
installation effort.
Installation Workflow
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.
• Linux 32-bit Server

• Linux 32-bit Client
• Linux 64-bit Server

• Linux 64-bit Client
• Solaris 10 (SPARC) 64-bit Server

• Solaris 10 (SPARC) 64-bit Client
• Windows XP/2003 SP2 32-bit Server

• Windows XP/2003 SP2 32-bit Client
• Windows 2003 SP2 64-bit Server

• Windows XP/2003 SP2 32-bit Client
OpenWorks Installation (all platforms, servers and clients)
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.
Version 5000.0.0.3 Quick Start: Installation Workflow 7

Installation Checklist: All Platforms
Servers Clients
Linux Linux Solaris Win Win Linux Linux Solaris Win
Step
64 32 64 64 32 64 32 64 32
Prerequisites
1. Check Software Packages (RPMs) Y Y Y Y
2. Check Swap Space Y Y Y
3. Set Shell Limits for Oracle Y Y
User
4. Run Pre-Oracle or Y Y Y Y Y Y
- Check/Set Kernel Parameters Y Y Y
and
- Create Oracle User Y Y Y Y Y Y Y Y Y
5. Modify Linux Release File Y Y Y Y
and change 5 to 4
6. Check/Install Loopback Y Y
Adapter on DHCP Computers
Install Oracle and Patch
7. Install Oracle (10.2.0.1.0): DB DB DB 64-bit DB C C C C
DB
DB = Database and
C = Client 32-bit
C
- Run Oracle Net Configura- silent silent silent Y
tion
Assistant (occurs silently on
all
clients except Windows 32-
bit)
- Run orainstRoot.sh and Y Y Y Y Y only
root.sh root.sh
scripts
8. Install Oracle Patch Y Y Y Y Y Y Y Y Y
(10.2.0.3.0) 64-bit
and
32-bit
- Run root.sh script Y Y Y
- Fix Directory Permission Y Y Y Y Y Y
Problem
8 Quick Start: Installation Checklist: All Platforms Version 5000.0.0.3

Servers Clients
Step
64 32 64 64 32 64 32 64 32
- Restore Linux Release File Y Y Y Y
back to 5
Install new database (Step 9) or Install schemas on existing database (Step 10)
9. Install OpenWorks 5000.0.0 Y Y Y Y Y
Database.
Installer adds Wallet location to

$ORACLE_HOME/network/admin/
sqlnet.ora
- Database Configuration Y Y Y Y Y
Assistant
- Change system, sys pass- Y Y Y Y Y
words
- Change sysman, dbsnmp Y Y
passwords
- Verify lib32 in Y Y
LD_LIBRARY_PATH
10. Install OpenWorks 5000.0.0 Y Y Y Y Y
Database Schemas on an
Existing Oracle Database.
Installer adds Wallet location

to $ORACLE_HOME/
network/admin/sqlnet.ora
- Check/Set recyclebin param- Y Y Y Y Y
eter
Install OpenWorks
11. Set OW_HOME_DIR Y Y Y
variable
12. Install OpenWorks. Y Y Y Y Y Y Y Y Y
On clients, installer adds wallet

location to $ORACLE_HOME/
network/admin/sqlnet.ora
OpenWorks Post-installation Configuration
13. Install libg2c and run root.sh Y
14. If necessary, create a new, Y Y Y
local OS user using lgcuser,
then update the user. lgcuser
adds $OW_HOME_DIR to
.lgclogin
Version 5000.0.0.3 Quick Start: Installation Checklist: All Platforms 9

Servers Clients
Step
64 32 64 64 32 64 32 64 32
15. Update existing users using Y Y Y
lgcuser. During the update,
lgcuser adds
$OW_HOME_DIR to
.lgclogin
LAM Servers only: Y Y Y
16. Update all users'
LM_LICENSE_FILE in
.lgclogin
17. Create an Oracle account for Y Y Y Y Y Y Y Y Y
OpenWorks
18. Change default passworks Y Y Y Y Y
19. Run owsetup Y Y Y Y Y Y
20. Configure Oracle Wallet if Y Y Y
multiple users will run
OpenWorks on this computer
21. Configure MKS and Exceed Y Y Y
22. District Configuration, if Y Y Y Y Y
necessary
Install GeoDataLoad, if applicable Y Y Y Y Y Y Y Y Y
10 Quick Start: Installation Checklist: All Platforms Version 5000.0.0.3

Oracle Installation
Linux 32-bit Server
Prerequisites and Procedures
1. Linux 32-bit Prerequisites
a. Check Software Packages (RPMs) on Linux 32-bit Servers and Clients

b. Check Swap Space on Linux 32-bit Servers
c. Set Shell Limits for the Oracle User on Linux 32-bit Servers
3. Configure the kernel parameters and create the Oracle user:
a. Run Pre-Oracle: Linux 32-bit Server (Recommended)
or
b. Creating an Oracle User
and
c. Configure Kernel Parameters on Linux 32-bit Servers
3. Modify the Linux 32-bit Release File
4. Install Oracle Database Software (10.2.0.1.0)
5. Install Oracle 10g Release 2 Patch Set 2 (10.2.0.3.0)
6. Fix Directory Permission Problem
7. Restore Linux Release File
8. Install OpenWorks 5000.0.0 Database (Perform these steps to create a new Oracle database for
OpenWorks.)
9. Install OpenWorks 5000.0.0 Database Schemas on an Existing Oracle Database. Perform these
steps if you already have a database created and want to run OpenWorks schemas on that
database.)
Version 5000.0.0.3 Oracle Installation: Linux 32-bit Server 11

Run Pre-Oracle: Linux 32-bit Server
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.
2. Navigate to the location where Pre-Oracle was downloaded.
3. Double-click setup.exe.
The Pre-Oracle Installer: Introduction screen opens.
4. Click Next.
The Choose Install Folder screen opens.
5. Enter the directory where you want to install the Oracle files.
6. Click Next.
The Pre-Installation Summary screen opens.
7. Verify that all settings are correct. If necessary, click Previous to correct settings.
8. Click Install.
The Oracle Setup Installation opens in an xterm.
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.
This becomes ORACLE_HOME= ${ORACLE_BASE}/OraHome1 in the ora10g .login file.
12.When prompted, enter Dba as the group.
13.When prompted, enter 7777 as the uid.
The Linux Configuration Utility opens in the xterm.
12 Oracle Installation: Linux 32-bit Server Version 5000.0.0.3

14.Enter 1 to update the kernel configuration.
The script creates the Oracle user and updates the kernel.
15.Enter 3 to quit the configuration utility.
Modify the Linux 32-bit Release File
The operating system update version should be:
Red Hat Enterprise Linux Server or Workstation release 5
Change the release file so the Oracle Universal Installer can install the Oracle Software
successfully.
1. Open the /etc/redhat-release file in a text editor.
2. Change the release version from 5 to 4 as follows:
Red Hat Enterprise Linux Server release 4 (Tikanga)
You will reverse this change later in the installation procedure.
Install Oracle Database Software (10.2.0.1.0)
1. Log on as root and cd /tmp.
2. Get the Oracle Software 10.2.0.1.0 10201_database_linux32.zip file.
3. Extract the contents in to a temporary directory.
4. Log on as the Oracle user, e.g., ora10g.
5. Set the display, if you are running remotely:
setenv DISPLAY <hostname>:0.0
6. Run the installer command:
/tmp/database/runInstaller
The Oracle Universal Installer: Welcome screen opens.

7. Click Next.
The Installation Method screen opens.
8. Verify that Basic Installation is selected.
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.
10.Set Installation Type to Enterprise Edition.
11.Uncheck the Create Starter Database checkbox.
12.Click Next.
The Specify Inventory directory and credentials screen opens.
13.Accept the inventory directory and group name defaults or make appropriate changes.
14.Click Next.
The Product-Specific Prerequisite Checks screen opens.
15.Verify that the overall result of the check is “Passed.”
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.
3. Click Next.
The Summary screen opens.
4. Verify that all settings are correct.
5. Click Install.
The Execute Configuration scripts window opens, instructing you to execute two scripts,
orainstRoot.sh and root.sh.
6. Execute the configuration scripts:

a. Open another xterm on the same host machine.
b. Log on as root.
c. Execute the orainstRoot.sh and root.sh scripts.
3. Click OK in the Execute Configuration scripts window only after successfully executing the
orainstRoot.sh and root.sh scripts.
The End of Installation screen opens.
4. Click Exit.
An Exit window opens.
5. Click Yes.
The installer closes.
Install Oracle 10g Release 2 Patch Set 2 (10.2.0.3.0)
1. Get the Oracle Software Patch 10.2.0.3.0 p5337014_10203_LINUX.zip file.
2. Extract the zip file in to a temporary directory.
3. Log on as the Oracle user (e.g. ora10g).
/tmp/Disk1/runInstaller
6. Click Next.
The Specify Home Details screen opens.
7. Accept the default name (OraDb10g_home1) for the installation.

The patch is applied in this path.
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.
11.Execute the configuration script:
b. Log on as root.
c. Execute the root.sh script.
root.sh script.
4. Click Exit.
5. Click Yes.
Fix Directory Permission Problem
Execute the following command as the Oracle user (e.g., ora10g):
chmod -R 775 $ORACLE_HOME
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.

Restore Linux Release File
Return the Linux release file to its original state.
2. Change the version number from 4 to 5 as follows:
Install OpenWorks 5000.0.0 Database
1. Get the OpenWorks 5000.0.0 Database zip file.
3. Log on as the Oracle user (e.g. ora10g).
Important note about installing remotely:
Exceed 2007 is required if you are installing remotely on Linux or Solaris from
Windows. Exceed 2008 will not work.
5. Run the installer:
/tmp/Linux/Disk1/InstData/VM/setup.bin
The Introduction screen opens.
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.
The Installation Options screen opens.

9. Choose the default “OpenWorks Database and Schemas.”
10.Click Next.
The Get Oracle Information screen opens.
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.
13.Click Next.
The Get Database Domain screen opens.
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.
15.Click Next.
The First Set of Datafiles screen opens.
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.
17.Select a Datablock Size. The default is 16 KB.
18.Set the System and SysAux tablespace sizes. The defaults are 1024MB and 256 MB,
respectively.
19.Click Next.
The Second Set of Datafiles screen opens.
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.
22.Set the Redo Logs size. The default is 16 MB.
23.Click Next.
The Third Set of Datafiles screen opens.
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.
26.Set the Users Tablespace size. The default is 5 MB.
27.Click Next.
The Schemas Directory screen opens.
28.Accept the default or enter the directory where you want to create OpenWorks schemas
database files.
29.Click Next.
The Projects Directories screen opens.
30.Enter the directory where you want to create project database files.
31.If desired, enter additional directories for project database files.
32.Click Next.
33.Verify that all settings are correct. If necessary, click Previous to correct settings.
34.Click Install when all settings are correct.
The Database Configuration Assistant window opens.
35.Click OK in the Database Configuration Assistant window after the database is successfully
created.
36.Check for Oracle Error messages in the Log file.

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 OpenWorks Schemas Creation Output screen opens.
37.Click Next.
A Modified SQLNET.ORA popup opens.
38.Click OK in the Modified SQLNET.ORA popup.
The Shutdown and Startup <dbname> and Listener screen opens.
39.Accept the default of Yes.
40.Click Next.
The Shutdown and Startup instance and Listener Output screen opens.
41.Click Next.
If you supplied a domain name, a Modified TNSNAMES.ORA option opens.
42.Click OK.
The Landmark OpenWorks Database R5000 message box opens.
The default passwords for the database users “system” and “sys” are “system” and “sys”
respectively. Change these default passwords after the installation.
43.Click OK.
The Install Complete screen opens.
44.Click Done.
Install OpenWorks 5000.0.0 Database Schemas on an Existing Oracle

Database

3. Log on as the Oracle user, e.g. ora10g.
6. Click Next.
8. Click Next.
9. Choose the “OpenWorks Schemas” option.
10.Click Next.
11.Enter the Oracle Home directory where you installed the Oracle Database software. “<drive>/
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.

13.Click Next.
The Existing Oracle database/instance Connection Testing screen opens.
14.Enter the password for the system user.
15.Click Next.
16.Select the directory where you want to create the OpenWorks schema database files.
17.Click Next.
18.Select the directory where you want to create project database files.
20.Click Next.
Note: Some Oracle errors are acceptable; e.g., errors that occur because of the drop user
24.Click Next.
A Database Initialization Parameters Check window opens.
You are instructed to set the initialization parameter “recyclebin” (which keeps the deleted
objects in a bin) to “off.”
25.Click OK.

26.Click Done.
27.Check the initialization parameter using the following SQL commands:
sqlplus <dba_user>/<dba_password>@sid
SQL> show parameters recyclebin
28.If necessary, set the initialization parameter to “off:”
SQL>alter system set recyclebin=off scope=both;
SQL>exit
What’s Next?
Install OpenWorks using the procedures in OpenWorks Installation.

Linux 32-bit Client
1. Check Software Packages (RPMs) on Linux 32-bit Servers and Clients
2. Create the Oracle user:
• Run Pre-Oracle: Linux 32-bit Client (Recommended)

or
• Creating an Oracle User
4. Install Oracle Client Software (10.2.0.1.0)
Run Pre-Oracle: Linux 32-bit Client
to create the Oracle user that is used to install the Oracle client software.
1. Log on as root.
4. Click Next.
6. Click Next.
24 Oracle Installation: Linux 32-bit Client Version 5000.0.0.3
8. Click Install.
9. Press Enter.
It is not necessary to modify the kernel on clients.
The script creates the Oracle user.
Change the release file so the Oracle Universal Installer can install the Oracle Software
successfully.
Version 5000.0.0.3 Oracle Installation: Linux 32-bit Client 25

Install Oracle Client Software (10.2.0.1.0)
2. Get the Oracle Software 10.2.0.1 10201_client_linux32.zip file.
/tmp/client/runInstaller
7. Click Next.
8. Accept the defaults or make appropriate changes.
9. Click Next.
The Select Installation Type screen opens.
10.Select Administrator.
11.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
14.Click Next.

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.
16.Click Next.
17.Verify that all settings are correct.
18.Click Install.
The Oracle Net Configuration Assistant opens.
19.Check the “Perform typical configuration” box.
20.Click Next.
The Oracle Net Configuration Assistant: Done screen opens.
21.Click Finish.
22.Execute the configuration scripts:
b. Log on as root.
4. Click Exit.
5. Click Yes.

1. Get the Oracle Software Patch 10.2.0.3 p5337014_10203_LINUX.zip file.
3. Log on as the Oracle user (e.g. ora10g) if you are not currently logged as the Oracle user.
6. Click Next.
7. Accept the default name for the installation.
ora10g .login file.
9. Click Next.
11.Click Exit.
The Exit window opens.
12.Click Yes.

2. Change the version number from 4 to 5 as follows:
What’s Next?

Linux 64-bit Server
1. Linux 64-bit Prerequisites
a. Check Software Packages (RPMs) on Linux 64-bit Servers and Clients
b. Check Swap Space on Linux 64-bit Servers
c. Set Shell Limits for the Oracle User on Linux 64-bit Servers
a. Run Pre-Oracle: Linux 64-bit Server (Recommended)
or
and
c. Configure Kernel Parameters 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.)
9. Install OpenWorks 5000.0.0 Database Schemas on an Existing Oracle Database (Perform these
steps if you already have a database created and want to run OpenWorks schemas on that
database.)
Run Pre-Oracle: Linux 64-bit Server

Oracle server.
1. Log on as root.
4. Click Next.
6. Click Next.
8. Click Install.
9. Press Enter.

However, you must change the release file so the Oracle Universal Installer can install the Oracle
Software successfully.
2. Get the Oracle Software 10.2.0.1.0 10201_database_linux_x86_64cpio.gz zip file.
3. Extract the zip file in to a temporary directory:
gunzip /tmp /10201_database_linux_x86_64.cpio.gz
cpio -imdv < 10201_database_linux_x86_64.cpio
7. Click Next.
12.Click Next.
14.Click Next.
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.
16.Click Next.
18.Click Install.

b. Log on as root.
20.Click OK in the Execute Configuration scripts window only after successfully executing the
21.Click Exit.
22.Click Yes.
1. Get the Oracle Software Patch 10.2.0.3.0 p5337014_10203_Linux-x86-64.zip file.
setenv DISPLAY <HOSTNAME>:0.0
/tmp/Disk1/runInstaller.
6. Click Next.

9. Click Next.
root.sh.
b. Log on as root.
root.sh script.
4. Click Exit.
5. Click Yes.

2. Change the version number from 4 back to 5 as follows:
6. Click Next.
8. Click Next.

10.Click Next.
13.Click Next.
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.
15.Click Next.
respectively.
19.Click Next.
files.

23.Click Next.
files.
27.Click Next.
28.Enter the directory where you want to create OpenWorks schemas database files.
29.Click Next.
32.Click Next.
created.

37.Click Next.
A Modified SQLNET.ORA popup opens.
38.Click OK in the Modified SQLNET.ORA popup.
The Shutdown and Startup <dbname> and Listener screen opens.
39.Accept the default of Yes.
40.Click Next.
41.Click Next.
If you supplied a domain name, a Modified TNSNAMES.ORA option opens.
42.Click OK.
The Landmark OpenWorks Database R5000 message box opens.
The default passwords for the database users “system” and “sys” are “system” and “sys”
43.Click OK.
44.Click Done.

Database

5. On Linux 64-bit and Solaris 64-bit, verify that Oracle lib32 is in the LD_LIBRARY_PATH:
echo LD_LIBRARY_PATH ${ORACLE_HOME}/lib32:${LD_LIBRARY_PATH}
7. Click Next.
9. Click Next.
10.Choose the “OpenWorks Schemas” option.
11.Click Next.
• 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.

14.Click Next.
15.Enter the password for the system user. The default is “system.”
16.Click Next.
17.Select the directory where you want to create the OpenWorks schema database files.
18.Click Next.
21.Click Next.
25.Click Next.
You are instructed to set the initialization parameter “recyclebin” that keeps the deleted
objects in a bin.
26.Click OK.

27.Click Done.
SQL>exit
What’s Next?

Linux 64-bit Client
1. Check Software Packages (RPMs) on Linux 64-bit Servers and Clients
• Run Pre-Oracle: Linux 64-bit Client (Recommended)

or
Run Pre-Oracle: Linux 64-bit Client
1. Log on as root.
4. Click Next.
6. Click Next.

8. Click Install.
9. Press Enter.
It is not necessary to modify the kernel on clients.
However, you must change the release file so the Oracle Universal Installer can install the Oracle
Software successfully.

1. Get the Oracle Software 10.2.0.1.0 10201_client_linux_x86_64.cpio.gz file.
3. Extract the zip file in to a temporary directory:
gunzip /tmp /10201_database_linux_x86_64.cpio.gz
cpio -imdv < 10201_client_linux_x86_64.cpio
7. Click Next.
The Select Installation Method screen opens.
10.Select the Installation Type as Enterprise Edition.
12.Click Next.

15.Click Next.
Note: If any of the tests fail, you must exit, set the recommended value of the parameter
17.Click Next.
19.Click Install.
21.Click Next.
A second Oracle Net Configuration Assistant opens.
22.Click Next.
23.Click Finish.
b. Log on as root.
3. Click OK in the Execute Configuration scripts window only after successfully executing

4. Click Exit.
5. Click Yes.
1. Get the Oracle Software Patch 10.2.0.3.0 p5337014_10203_Linux-x86-64.zip file.
2. Extract the zip file in to a temporary directory using the unzip command:
unzip /tmp /p5337014_10203_Linux-x86-64.zip
3. Log on as the Oracle user, e.g., ora10g, if you are not currently logged as Oracle user.
6. Click Next.
9. Click Next.
10.Click Install.
11.Click Exit.

12.Click Yes.
Execute the following command as the Oracle user, (e.g., ora10g):
2. Change the version number from 4 back to 5 as follows:
What’s Next?

Solaris 10 (SPARC) 64-bit Server
1. Check Swap Space on Solaris 10 Servers
a. Run Pre-Oracle: Solaris 64-bit Server (Recommended)
or
and
c. Configure Kernel Parameters on Solaris 10 Servers
OpenWorks.)
steps to add OpenWorks schemas to an existing Oracle database.)
Run Pre-Oracle: Solaris 64-bit Server
Oracle server.
1. Log on as root.
Version 5000.0.0.3 Oracle Installation: Solaris 10 (SPARC) 64-bit Server 49

4. Click Next.
6. Click Next.
8. Click Install.
9. Press Enter.
The Solaris Configuration Utility opens in the xterm.
2. Get the Oracle Software 10.2.0.1.0 10gr2_db_sol.cpio.gz zip file.
3. Extract the zip file in to /tmp/database using the gunzip and cpio commands:
gunzip /tmp/database/10gr2_db_sol.cpio.gz
50 Oracle Installation: Solaris 10 (SPARC) 64-bit Server Version 5000.0.0.3

cpio -imdv < 10gr2_db_sol.cpio
7. Click Next.
11. Uncheck the Create Starter Database checkbox.
12.Click Next.
14.Click Next.
Note: If any of the tests fail, cancel the install, set the recommended value of the parameter
• 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.

16.Click Next.
The Select Configuration Option screen opens.
17.Select the Install database Software only option.
18.Click Next.
20.Click Install.
b. Log on as root.
4. Click Exit.
5. Click Yes.

1. Get the Oracle Software Patch 10.2.0.3.0 p5337014_10203_Solaris64.zip file.
2. Extract the zip file in /tmp using the unzip command:
unzip /tmp /p5337014_10203_Solaris64.zip

6. Click Next.
7. Accept the default name (OraDb10g_home1) for the installation.
9. Click Next.
root.sh.
b. Log on as root.
root.sh script.
4. Click Exit.

5. Click Yes.
Execute the following command as the Oracle user, e.g., ora10g:
2. Get the OpenWorks 5000.0.0 Database zip file and extract it in to the temporary directory.
/tmp/Solaris/Disk1/InstData/VM/setup.bin
5. Click Next.

7. Click Next.
9. Click Next.
12.Click Next.
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.
14.Click Next.
respectively.
18.Click Next.
files.

22.Click Next.
files.
26.Click Next.
27.Enter the directory where you want to create OpenWorks schemas database files.
28.Click Next.
31.Click Next.
33.Click Install.
created.
35.Check for Oracle Error messages in the Log file .
statements, IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts, etc.
However, TNS- errors are installation failure indicators.

36.Click Next.
The Landmark OpenWorks5000.0.0 Database message box opens.
The default passwords for database user “system” and “sys” are “system” and “sys”
37.Click OK.
38.Click Done.

Database
3. On Linux 64-bit and Solaris 64-bit, verify that Oracle lib32 is in the LD_LIBRARY_PATH:
echo LD_LIBRARY_PATH ${ORACLE_HOME}/lib32:${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.

9. Click Next.
11.Click Next.
• 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.
14.Click Next.
15.Enter the Oracle user name “system.”
16.Enter the password for the Oracle system user. The default is “system.”
17.Click Next.
18.Enter the directory where you want to create the OpenWorks schema database files.
19.Click Next.

22.Click Next.
23.Click Install.
statements and IMP_FULL_DATABASE, EXP_FULL_DATABASE role conflicts, etc.
However, TNS- errors are installation failure indicators.
25.Click Next.
26.Click OK.
27.Click Done.
SQL>exit

What’s Next?

Solaris 10 (SPARC) 64-bit Client
1. Solaris 10 (SPARC) 64-bit Prerequisites
• Run Pre-Oracle: Solaris 64-bit Client (Recommended)

or
Run Pre-Oracle: Solaris 64-bit Client
1. Log on as root.
4. Click Next.
6. Click Next.
8. Click Install.
Version 5000.0.0.3 Oracle Installation: Solaris 10 (SPARC) 64-bit Client 61

9. Press Enter.
1. Get the Oracle Software 10.2.0.1.0 10gr2_client_sol.cpio.gz zip file.
3. Extract the zip file in to /tmp/client using the gunzip and cpio commands:
gunzip /tmp/client/10gr2_client_sol.cpio.gz
cpio -imdv < 10gr2_client_sol.cpio
/tmp/client/runInstaller
7. Click Next.
62 Oracle Installation: Solaris 10 (SPARC) 64-bit Client Version 5000.0.0.3

8. Accept the defaults or make appropriate changes.
9. Click Next.
11.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.
14.Click Next.
• 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
16.Click Next.
18.Click Install.
20.Click Next.
21.Click Next.

22.Click Finish.
b. Log on as root.
4. Click Exit.
5. Click Yes.
1. Get the Oracle Software Patch 10.2.0.3.0 p5337014_10203_Solaris64.zip file.
2. Extract the zip file in to /tmp using the unzip command:
unzip /tmp /p5337014_10203_Solaris64.zip

6. Click Next.
ora10g .login file.
9. Click Next.
11.Click Exit.
12.Click Yes.
Execute the following command as the Oracle user, e.g., ora10g:
What’s Next?


Windows XP/2003 SP2 32-bit Server
1. Prerequisites for Installing Oracle on DHCP Computers
2. Create Oracle User
4. Install Oracle 10g Software Patch 2 (10.2.0.3.0)
OpenWorks.)
steps if you already have a database created and want to install OpenWorks schemas on that
database.)
1. Log on as the Oracle user, e.g., ora10g, with administrator privileges. Do not install as
Administrator or using your personal account.
2. Get the Oracle Software 10.2.0.1.0 10201_database_win32.zip file.
C:\Temp\10201_database_win32\database\setup.exe
5. Click Next.
6. Select Basic Installation.
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.
Version 5000.0.0.3 Oracle Installation: Windows XP/2003 SP2 32-bit Server 67

8. Set Installation Type to Enterprise Edition.
10.Click Next.
• If any of the tests fail, cancel the install, set the recommended value of the parameter
• 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.
12.Click Next, if the overall result of the check is “Passed.”
14.Click Install.
15.Click Exit.
Install Oracle 10g Software Patch 2 (10.2.0.3.0)
2. Get the Oracle Software 10.2.0.3.0 p5337014_10203_WINNT.zip file.
C:\Temp\p5337014_10203_WINNT\Disk1\setup.exe
68 Oracle Installation: Windows XP/2003 SP2 32-bit Server Version 5000.0.0.3

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.
10.Click Exit.
11.When prompted “Do you really want to exit?” click OK.
2. Create a directory for the OW_HOME_DIR System variable:
C:\oracle\product\10.2.0f\db_1\users\ora10g
3. Set OW_HOME_DIR as a SYSTEM variable with

C:\oracle\product\10.2.0\db_1\users\ora10g as the variable value.
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.
10.Choose the default “OpenWorks Database and Schemas.”
11.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.
14.Click Next.
15.Accept the default directory or enter the directory where you want to install the first set of
database files.
16.Accept the default Datablock Size of 16 KB.
17.Accept the default System size of 1024 MB and the default SysAux tablespace size of 256
MB.
18.Click Next.
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.
21.Click Next.
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.
24.Click Next.
25.Accept the default directory or enter the directory where you want to create OpenWorks
schemas database files.
26.Click Next.
schemas database files. If desired, enter additional directories for project database files.
28.Click Next.
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.
created.
The Landmark OpenWorks 5000.0.0 Database message box opens.
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.
33.Click OK.

34.Click Next.
The Modified SQLNET.ORA window opens.
35.Click OK.
The Shutdown and Startup <SID> & Listener screen opens.
36.Accept the default Yes to shutdown and startup the instance and listener and click Next.
37.Verify that the commands completed successfully, then click Next.
38.Click Done.

Database
C:\oracle\product\10.2.0\db_1\users\ora10g
3. Set OW_HOME_DIR as a System variable with C:\oracle\product\10.2.0\db_1\users\ora10g

as the variable value.
7. Click Next.

9. Click Next.
11.Click Next.
12.Verify that the default Oracle Home directory is where you installed Oracle.
14.Click Next.
16.Click Next.
17.Select the directory where you want to create OpenWorks schema database files.
18.Click Next.
21.Click Next.

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.
25.Click Next.
26.Click OK.
27.Click Done.
What’s Next?

Windows XP/2003 SP2 32-bit Client
2. Install Oracle Client Software 32 bit (10.2.0.1.0)
3. Install Oracle 10g Patch Set 2 32 bit (10.2.0.3.0)
Install Oracle Client Software 32 bit (10.2.0.1.0)
2. Get the Oracle Software 10.2.0.1.0 10201_client_win32.zip file.
C:\Temp\10201_client_win32\client\setup.exe
5. Click Next.
Version 5000.0.0.3 Oracle Installation: Windows XP/2003 SP2 32-bit Client 75

Installation Type and OpenWorks Basic
For OpenWorks Basic, the Oracle client can be installed with the Runtime or Administrator
installation type; however, if OpenWorks will be used with the DiscoveryTM software from
GeoGraphix®, the Oracle client can be installed with the Administrator installation type or with the
Custom installation type. If the Custum installation type is chosen you must select the following
components among other components you may choose:
• Oracle Database Utilities
• Oracle JDBC/THIN Interfaces
• Oracle Net
• SQL*Plus
The file sqlnet.ora should contain the following lines:
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
(DIRECTORY=%OW_HOME_DIR%\wallet)
)
)
SQLNET.WALLET_OVERRIDE= TRUE
Consult a certified Oracle Database Adminstrator for more information about other Oracle
components your installation may require.
6. Select Administrator.
7. Click Next.
8. Accept the default name of the installation, oraClient10g_home1, or enter a new name.
9. Accept the default path for the Oracle Home Location,

<drive>:\oracle\product\10.2.0\client_1, or select a new location
10.Click Next.
76 Oracle Installation: Windows XP/2003 SP2 32-bit Client Version 5000.0.0.3

installer again.
12.Click Next if the overall result of the check is “Passed.”
14.Click Install.
16.Click Next.
17.Click Next.
18.Click Finish.
19.Click Exit.
20.Click Yes.
Install Oracle 10g Patch Set 2 32 bit (10.2.0.3.0)
Version 5000.0.0.3 Oracle Installation: Windows XP/2003 SP2 32-bit Client 77

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.
10.Click Exit.
11.Click Yes.
What’s Next?
78 Oracle Installation: Windows XP/2003 SP2 32-bit Client Version 5000.0.0.3

Windows 2003 SP2 64-bit Server
1. Prerequisites for Installing Oracle on DHCP Computers
3. Install Oracle Database Software 64 bit (10.2.0.1.0)
4. Install Oracle 10g Software Patch 2 64 bit (10.2.0.3.0)
5. Install Oracle Client Software 32 bit (10.2.0.1.0)
6. Install Oracle 10g Patch Set 2 32 bit (10.2.0.3.0)
OpenWorks.)
steps if you already have a database created and want to run OpenWorks schemas only on that
database.)
Install Oracle Database Software 64 bit (10.2.0.1.0)
2. Get the Oracle Software 10.2.0.1.0 102010_win64_x64_database.zip file.
C:\Temp\10201_win64_x64_database\database\setup.exe
5. Click Next.
6. Select Basic Installation.
Version 5000.0.0.3 Oracle Installation: Windows 2003 SP2 64-bit Server 79

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.
8. Set Installation Type to Enterprise Edition.
10.Click Next.
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.
14.Click Install.
15.Click Exit.
16.Click Yes.
Install Oracle 10g Software Patch 2 64 bit (10.2.0.3.0)
2. Get the Oracle Software 10.2.0.3.0 p5337014_10203_MSWIN-x86-64.zip file.
80 Oracle Installation: Windows 2003 SP2 64-bit Server Version 5000.0.0.3

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.
The Configuration Assistants screen opens briefly, then the End of Installation screen opens.
10.Click Exit.
11.Click Yes.
Install Oracle Client Software 32 bit (10.2.0.1.0)
2. Get the Oracle Software 10.2.0.1.0 10201_client_win32.zip file.
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.
9. Accept the default path for the Oracle Home Location,

<drive>:\oracle\product\10.2.0\client_1, or select a new location
10.Click Next.
installer again.
14.Click Install.
16.Click Next.
17.Click Next.

18.Click Finish.
19.Click Exit.
20.Click Yes.
Install Oracle 10g Patch Set 2 32 bit (10.2.0.3.0)
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.
10.Click Exit.

11.Click Yes.

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.
10.Choose the default “OpenWorks Database and Schemas.”
11.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.
14.Click Next.
15.Accept the default directory or enter the directory where you want to install the first set of
database files.
16.Accept the default Datablock Size of 16 KB.
17.Accept the default System size of 1024 MB and the default SysAux tablespace size of 256
MB.
18.Click Next.
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.
21.Click Next.
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.
24.Click Next.
schemas database files.
26.Click Next.

27.Accept the default directory or enter the directory where you want to create project database
files.
29.Click Next.
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.
created.
The Landmark OpenWorks 5000.0.0 Database message box opens.
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.
33.Click OK.
35.Click Next.
36.The Modified SQLNET.ORA window opens. Click OK.
The Shutdown and Startup <SID> & Listener screen opens.

37.Accept the default Yes to shutdown and startup the instance and listener and click Next.
38.Verify that the commands completed successfully, then click Next.
39.Click Done.

Database

c:\temp\owdb5000\Disk1\InstData\VM\install.exe
7. Click Next.
9. Click Next.
11.Click Next.

12.Verify that the default Oracle Home directory is where you installed Oracle 64-bit.
14.Click Next.
16.Click Next.
schema database files,
18.Click Next.
19.Accept the default directory or enter the directory where you want to create project database
files.
21.Click Next.
24.Check for Oracle Error messages in the log file.
25.Click Next.

objects) to “off.”
26.Click OK.
27.Click Done.
SQL>exit
Install 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
Use the steps in this section to install OpenWorks.
Before Installing on Linux & Solaris
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.
Before Installing on Windows
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.
2. Uninstall any previous version of MKS:
a. In the Add or Remove Programs window, select MKS Platform Components.
b. Click Remove.
c. Reboot.
3. Uninstall any previous version of GeoDataLoad:
a. In the Add or Remove Programs window, select GeoDataLoad.
b. Click Remove.
c. When the uninstaller launches, select Complete Uninstall and click Next, and Next
again. It is not necessary to reboot.
3. Uninstall any previous version of OpenWorks:
90 OpenWorks Installation: Before Installing on Linux & Solaris Version 5000.0.0.3

a. In the Add or Remove Programs window, select OpenWorks.
b. Click Remove.
c. When the uninstaller launches, select Complete Uninstall and click Next, and Next
again. It is not necessary to reboot.
3. 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.
b. Create an installation directory; for example, C:\Landmark\OpenWorks.
c. Launch System from the Control Panel.
The System Properties window opens.
d. On the Advanced tab, click Environment Variables.
e. When the Environment Variables window opens, click New in the User variables pane.
When the New User Variable window opens:
• Type OW_HOME_DIR in the Variable name text box.
• Type the path where OpenWorks will be installed in the Variable value text box;
for example, C:\Landmark\OpenWorks.
• Click OK.
f. In the Environment Variables window, click OK.
g. In the System Properties window, click OK.
h. Close the Control Panel.
Version 5000.0.0.3 OpenWorks Installation: Before Installing on Windows 91

Note concerning multiple users on a Windows installation:
The OpenWorks Database installer creates a wallet folder in the

OW_HOME_DIR directory.
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.
92 OpenWorks Installation: Before Installing on Windows Version 5000.0.0.3

Install OpenWorks
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 as Administrator.
• Do not install if the OW_HOME_DIR User variable has not been set.
2. Navigate to the location where OpenWorks was downloaded.
4. Launch the installer.
The OpenWorks Introduction screen opens.
5. Click Next.
The Enter User and Company Name screen opens.
6. Type the name of the OpenWorks user and company.
7. Click Next.
8. Enter the directory where you want to install OpenWorks.
9. Click Next.
The OpenWorks Flat File Setup screen opens.
• This step creates the OW_SYS_DATA and OW_PROJ_DATA directories.
• Flat files will be stored in the directories specified in this step.
Version 5000.0.0.3 OpenWorks Installation: Install OpenWorks 93

• After installation, you can change where the flat files are stored. For OW_SYS_DATA, edit
the path of the OW_SYSDATA_DIR variable in lgcenv.cf, which is located in
$OWHOME/conf . The lines setting the variable appear similar to the following:
# OpenWorks OW_SYS_DATA Directory Location

#
OW_SYSDATA_DIR /d02/OW5000/
• For OW_PROJ_DATA, edit owdir.dat. The location of owdir.dat is determine by

district.dat. Each district in an OpenWorks instance can have a unique version of
owdir.dat. Before editing, make sure you locate the correct owdir.dat that is associated
with the district where your project is located.
10.Enter the system directory.
11.Enter the project directory.
12.Click Next.
13.Accept the default directory or enter the directory where you installed Oracle (see the Oracle
Software Installation section).
15.Click Next.
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.
18.Click Next.
All platforms. The District.dat screen opens.
19.Choose a method for configuring a district.dat file.
94 OpenWorks Installation: Install OpenWorks Version 5000.0.0.3

• Recommended. Select “Create a district.dat from TNSNAMES.ORA” to get started

quickly. This will create a district for each SID entry in the tnsnames.ora file.
• 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.
20.Click Next.
Windows only. The Redistributable Package screen opens.
21.Click Yes to install the Microsoft Visual C++ 2005 SP1 Redistributable Package.
22.Click Next.
Windows only. The MKS Installation screen opens.
23.Click Yes to install MKS.
24.Click Next.
All platforms. The Pre-Installation Summary screen opens.
26.Click Install.
All platforms: The License screen opens.
27.Click Next.
Windows only. The Microsoft Visual C++ 2005 SP1 Redistributable Package License Agreement
window opens.
28.Click Yes.
Version 5000.0.0.3 OpenWorks Installation: Install OpenWorks 95

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.
29.Click OK.
Linux only. The RedHat 5 specific screen opens, instructing you to run the root.sh script after the
OpenWorks installation.
30.Click Next.
All platforms: The Install Complete screen opens.
31.Select Yes, restart my system.
32.Click Done.
What’s Next?
Perform the platform-specific procedures in Post-Installation
96 OpenWorks Installation: Install OpenWorks Version 5000.0.0.3

Post-Installation
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
• Linux & Solaris
• All Platforms
• Windows
• District Configuration
Version 5000.0.0.3 Post-Installation: Overview 97

Linux Only
64-bit Servers: Install an Additional Library
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.
As root, install the library using the following command:
rpm -ivh compat-libf2c-34-3.4.6-4.i386.rpm
64-bit Servers: Selinux
Perform this procedure if instructed to do so via a RedHat 5 specific screen at the end of the
OpenWorks installation.
As root, run the root.sh script:
sh $OWHOME/bin/root.sh
The root.sh script content is as follows:
#!/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/*
98 Post-Installation: Linux Only Version 5000.0.0.3

Linux & Solaris
Linux & Solaris Clients: Create a Local OS User
Skip this section if you do not need to create a local user.
1. As root, set $OWHOME to the location of the OpenWorks installation.
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.
Linux & Solaris Servers: Update Users
Perform the following procedure if the local user exists or you need to update a network user.
1. As root, launch $OWHOME/bin/lgcuser.
2. Select Update User (#4) and follow the instructions on the screen.
Linux & Solaris LAM Servers: Update OS Users’ .lgclogin
If you ran the lgcuser update option on a user, change the license server information.
Open .lgclogin in a text editor and change the line:
# setenv LM_LICENSE_FILE __LM_LICENSE_FILE_Is_Not_Set_
to, for example:
setenv LM_LICENSE_FILE 2014@owlic5.lgc.com
Linux & Solaris Servers and Clients: Run owsetup Script
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.
2. Launch $OWHOME/install/owsetup –o $OWHOME.
3. When the OpenWorks Set Up utility opens, select the appropriate option:
Version 5000.0.0.3 Post-Installation: Linux & Solaris 99

• Clients: choose option 2.
• OpenWorks/Oracle servers: choose option 3.
• LAM servers: choose option 4.
100 Post-Installation: Linux & Solaris Version 5000.0.0.3

All Platforms
Grant Database Access to the OpenWorks User
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.
1. Log in as an OpenWorks user.
2. Launch the Modify Database Users utility:
Linux & Solaris: Launch the OpenWorks Command Menu: ${OWHOME}/bin/startow -i $$
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.
3. If prompted, select a district to get to the correct SID.
The DBA Logon window opens.
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.
5. In Password, enter the DBA's password.
6. Click Login. If the correct credentials are entered, the Database Users window opens.
Version 5000.0.0.3 Post-Installation: All Platforms 101

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).
10.Click Add.
11.Close the Database Users dialog.
Change Default Passwords
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.
AutoExtend is on by Default for SYSTEM and Project Table Spaces
Oracle’s autoextend feature is turned on by default to extend system tables spaces. To turn it off
for the project table space, edit the following file: $OWHOME/lgcenv.cf or
$OW_CONF_DIR/lgcenv.cf .
102 Post-Installation: All Platforms Version 5000.0.0.3

Windows
Windows Servers and Clients: Oracle Wallet and Multiple Users
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.
The OpenWorks installation creates a directory in the OpenWorks installation location

(OWHOME) called users. Under the users directory, create a directory for each user that will be
using OpenWorks on this machine. Each user must have a unique directory so that the Oracle
wallet files can be stored.
For example, if three users (user1, user2 and user3) will be using this Windows machine, create
the following directories:
%OWHOME%\users\user1
1. Log on using your typical user account.
2. Launch System from the Control Panel.
The System Properties window opens.
3. On the Advanced tab, click Environment Variables.
4. When the Environment Variables window opens, click New in the User variables pane.
5. When the New User Variable window opens:
a. Type OW_HOME_DIR in the Variable name text box.
b. Type the path where OpenWorks was installed in the Variable value text box; for example,
C:\Landmark\OpenWorks\users\<user name>.
c. Click OK.
3. In the Environment Variables window, click OK.
4. In the System Properties window, click OK.
5. Close the Control Panel.
Version 5000.0.0.3 Post-Installation: Windows 103

6. Create an OpenWorks folder for your use:
a. Navigate to the OpenWorks users folder; for example,
C:\Landmark\OpenWorks\users
c. Create a folder for your use; for example,
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.
Configure the MKS Toolkit and Hummingbird Exceed
1. On the Control Panel, select Configure MKS Toolkit.
The Configure MKS Toolkit window opens.
2. In the Runtime Settings tab, choose XWindow System Settings, then click OK.
X Server Settings appear in the window.
3. Choose Registered.
4. Click Hummingbird Exceed. A green check mark appears to the left.
5. Ensure that the Use Network Connection box is checked.
6. Click OK.
The Configure MKS Toolkit window closes.
7. Reboot.
104 Post-Installation: Windows Version 5000.0.0.3

District Configuration
A Brief Overview of the District Concept
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.
Is Configuration Necessary?
If the recommended OpenWorks installation option “Create a district.dat from TNSNAMES.ora”

was selected, and a valid SID was created for each district, no additional district-related
configuration is required to run OpenWorks and proceed with new projects.
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.
Version 5000.0.0.3 Post-Installation: District Configuration 105

GeoDataLoad Installation
If you have a GeoDataLoad license, follow the installation steps in this section.
Uninstall Previous Versions of GeoDataLoad
Windows
1. On the Control Panel, launch Add/Remove Programs.
2. Click the GeoDataLoad Remove button.
3. When the uninstaller launches, select Complete Uninstall and click Next, and Next again. It is
not necessary to reboot.
Linux or Solaris
Simply remove the $OWHOME directory and its contents.
Install GeoDataLoad
1. Set the display, if you are running remotely: setenv DISPLAY <hostname>:0.0
2. Launch the GeoDataLoad installer:
Linux or Solaris: <PATH>/IA/CDROM_Installers/<OS>/Disk1/InstData/VM/setup.bin

Windows: <PATH>/IA/CDROM_Installers/Windows/Disk1/InstData/VM/setup.exe
The GeoDataLoad Introduction screen opens.
3. Click Next.
The choose Install Folder screen opens.
4. Accept the default or enter the directory where you want to install GeoDataLoad.
5. Click Next.
106 GeoDataLoad Installation: Uninstall Previous Versions of GeoDataLoad Version 5000.0.0.3

7. Click Done.
Version 5000.0.0.3 GeoDataLoad Installation: Install GeoDataLoad 107

108 GeoDataLoad Installation: Install GeoDataLoad Version 5000.0.0.3

Upgrading the OpenWorks Software
This chapter contains information about upgrading an installation of the OpenWorks software
version 5000.x to a higher version of the OpenWorks software.
Upgrading to Version 5000.0.0.3
If you are installing an update over an existing 5000.0.0.x installation, the installer will not
prompt you for district.dat, the OpenWorks project directories for files external to the OpenWorks
instance, and the ORACLE_HOME configurations. These configurations will be saved during the
update process. The installation process has the following parts:
• Installing the New Version of the Software
• Upgrading the Projects in the OpenWorks Database
• Post-installation Steps for Linux and Solaris
OWSYS and Restored Projects
Version 5000.0.0.3 of the OpenWorks instance does not require an OWSYS upgrade.
Projects from versions of 5000.0.0.x that are restored to an OpenWorks instance with the 5000.0.0.3
update are automatically upgraded to 5000.0.0.3 when restored.
Projects from releases before version 5000.0.0.0 that are restored to an OpenWorks instance with the
5000.0.0.3 update are upgraded to version 5000.0.0.3 after the restoration of the project, when you
upgrade the project in Project Administration.
Installing the New Version of the Software
To patch an existing installation of the OpenWorks software, do the following:
1. Backup all of your OpenWorks projects.
Note: Recommended since the project upgrade script will be run.
2. Make sure all OpenWorks sessions and launchers are closed
Version 5000.0.0.3 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.3 109
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.
3. For Linux and Solaris, in a terminal window, type the following:
$OWHOME/bin/stop_netd
$OWHOME/bin/start_netd
4. Install the update.
For Linux and Solaris, in a terminal window, type the following:
sh setup.bin
For Windows, double-click the installation program:
setup.exe
5. Upgrade existing projects:
Upgrading the Projects in the OpenWorks Database
After installing version 5000.0.0.3, you must upgrade any 5000.0.0.x projects in the database to
version 5000.0.0.3.
Upgrading One Project Database
To patch the data model of a project database and its interpretation projects, execute the following
script in a terminal window:
$OWHOME/bin/OWRuntimeLauncher.sh RunPatchSqlScripts OW_SID

ProjectDBName -logdir LogDir
where OW_SID is the system identifier of the OpenWorks database where the project database is
located.
ProjectDBName is the name of the project database that needs to be upgraded
LogDir is the location where the script should store its logs. The parameters -logdir LogDir
are optional.
110 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.3 Version 5000.0.0.3
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:
%owhome%\bin\OWRuntimeLauncher.bat RunPatchSqlScripts OW5000 ALL

-logdir C:\userhome\LOGS
Or
$OWHOME/bin/OWRuntimeLauncher.sh RunPatchSqlScripts OW5000 ALL

-logdir /d01/userhome/logs
Upgrading Multiple Projects With Project Administration
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.
To upgrade multiple project databases:
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.
Post Installation Steps for Linux and Solaris
Update the User Profile (launcher.dat and .lgclogin)
After upgrading the OpenWorks software (for instance, from version 5000.0.0.x to 5000.0.0.3),
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.
Update the files by do the following:
1. Close any OpenWorks applications, including the OpenWorks Command Menu.
2. Move launcher.dat and .lgclogin in your home directory to another location. For example:
Version 5000.0.0.3 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.3 111
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:
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.
112 Upgrading the OpenWorks Software: Upgrading to Version 5000.0.0.3 Version 5000.0.0.3
Appendix: Upgrade OpenWorks Instance
This appendix describes how to upgrade an OpenWorks® database (R2003.12) residing in an

Oracle version 8.1.7.4 or Oracle 9.2.0.4 instance to an OpenWorks database (Release 5000.0.x) in
an Oracle 10g 10.2.0.3 instance.
Before Upgrading
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.
Differences in the Oracle Databases
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 projects in the OpenWorks software R2003.12 use dictionary-managed tablespaces.

Starting with the OpenWorks software version 5000.0, projects use locally-managed
tablespaces.
• The OpenWorks sotware R2003.12 uses externally identified Oracle users. The
OpenWorks software version 5000.0.0 uses internally identified Oracle users.
Assumptions for Uprgrading
Verify that the following conditions are met:
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, or above, 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, or above, is installed.
Version 5000.0.0.3 Appendix: Upgrade OpenWorks Instance: Before Upgrading 113

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, or above, 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.
Upgrade Workflow
Pre Migration Steps
• 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
— Installing the Oracle database server on a supported operating

system.
— Installing the OpenWorks software.
— 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.
114 Appendix: Upgrade OpenWorks Instance: Upgrade Workflow Version 5000.0.0.3

Upgrading to Version 5000.0.x
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, or above. The procedures below delineate that procedure.
Preparing the R2003.12 Database for Export
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, or above, of the
OpenWorks software.
1. Check for remote projects.
a. Run the check_remote_projects.sql script (located in $OWHOME/dat/

project5000.0) as the database user (for example, system) of the R2003.12 database
to determine if there are any remote projects on the database.
cd $OWHOME/dat/project5000.0
sqlplus system/Password@OW_DB_SID
SQL>@check_remote_projects.sql "OW_DB_SID"
b. If there are no remote projects on the ow2003 instance, go to step 2. Otherwise, perform
the following step to handle the remote projects before proceeding to step 2.
If there are remote projects, the result will look similar to the following. Perform the
steps shown in the results.
Project FLOUNDER is a remote project on sid LATEST

Project GOM is a remote project on sid OWBLACK.LGC.COM
In R5000, the remote project functionality is no longer supported.
Please go back to the R2003.12 instance and use Project Admin to

backup the remote projects, delete them from ow2003 instance and
restore them in the R5000 instance.
If you have further questions, please contact Landmark Customer

Support.
Version 5000.0.0.3 Appendix: Upgrade OpenWorks Instance: Upgrading to Version 5000.0.x 115
3. Generate a schema definition file for the existing OpenWorks R2003.12 database.
Run the $OWHOME/dat/project5000.0/process_ow2003_tablespaces.sql script as the

database user (e.g., system) against the R2003.12 OWSYSSID ow2003 to generate an
OpenWorks R2003.12 schema definition (tablespaces and users) SQL file called
ow2003_tablespace.sql.
cd $OWHOME/dat/ project5000.0
sqlplus system/<password>@ow2003
SQL>@ process_ow2003_tablespaces.sql /<directory_path>/

ow2003_tablespaces.sql
The result will look similar to the following:
create tablespace FLOUNDER datafile '/d01/ora9i/OraHome1/

owprojects/FLOUNDER02090191891A.dbs' size 200M autoextend on
extent management local;
create user FLOUNDER identified by values 'DDC631FBD8763204'

default tablespace FLOUNDER temporary tablespace TEMP;
grant create session, connect to FLOUNDER;
4. Run the $OWHOME/dat/project5000.0/process_ow2003_users.sql script as the database user

(e.g., system) against the R2003.12 OWSYSSID ow2003 to grant roles to the OpenWorks
project users. The script generates an SQL file called ow2003_users.sql.
For example:
Continuing the SQL session in Step 2:
SQL>@process_ow2003_users.sql /<directory_path>/
ow2003_users.sql
-or-
Starting a new SQL session:
cd $OWHOME/dat/project5000.0
sqlplus system/<password>@ow2003
116 Appendix: Upgrade OpenWorks Instance: Upgrading to Version 5000.0.x Version 5000.0.0.3
SQL>@process_ow2003_users.sql /< directory_path >/

ow2003_users.sql
The result will look similar to the following:
alter user owjune identified by owjune;
alter user owtest identified by owtest;
grant MANAGE_EMPTY to OWJUNE;
grant L_INTERP_FLOUNDER to OWJUNE;
grant OW_ADMINISTRATOR to OWJUNE;
insert into owsys.ow_sys_user (user_id) values ('OWJUNE');
insert into owsys.ow_sys_user (user_id) values ('OWTEST');
commit;
5. Copy $OWHOME/dat/project5000.0/fullexport.cntl from the OpenWorks 5000.0.0 runtime to

the R2003.12 image.
Exporting the Database from OpenWorks R2003.12
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.
6. 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 5 from the environment of version 5000.0.0.2, or
above.
BUFFER=2000000
USERID="system/Password@OW_DB_SID"
FILE=/FullPath/FileNameOfExportFile.dmp
FULL=Y
LOG=/FullPath/FileNameOfLogFile.log
Where Password is the password of the System user.
OW_DB_SID is the OWSYSSID of the database.
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).
7. Execute the export command:
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.
For an Oracle 8 server:
su - oracle8
$ORACLE_HOME/bin/exp parfile = fullexport.cntl
Note: Ensure this is the Oracle 8 ORACLE_HOME.
For an Oracle 9 server:
su - oracle9
$ORACLE_HOME/bin/exp parfile = fullexport.cntl
Note: Ensure this is the Oracle 9 ORACLE_HOME.
c. Copy the export file from the R2003.12 installation to the installatin of OpenWorks
version 5000.0.0.
Procedures in the OpenWorks 5000.0.0 Runtime Environment
Run Steps 7 through 15 in the OpenWorks 5000.0.0 runtime environment.
8. Create the directory structure for the new datafiles.
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. Rename sqlnet.ora if wallet is configured in the file.
If you have sqlnet.ora file similar to the following example in $ORACLE_HOME/network/

admin, rename it to sqlnet.ora_orig, otherwise, skip this step.
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
(DIRECTORY=${OW_HOME_DIR}/wallet)
)
)
10.Run the ow2003_tablespace.sql script (created in Step 3 on page 116) to create the tablespaces
and OpenWorks project users in the OpenWorks 5000.0.0 instance (ow5000).
sqlplus system/<system password>@ow5000

SQL>@/<directory_path>/ow2003_tablespace.sql
For a list of possible errors, see “Possible Errors During the Import” on page 126.
11.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 7 on page 118 ) from the
OpenWorks R2003.12 runtime image to an OpenWorks 5000.0.0 runtime image.
a. su - ora10g
b. Modify $OWHOME/dat/project5000.0/fullimport.cntl as follows:
BUFFER=2000000
USERID="system/<password>@ow5000"
FILE=/<dir>/ow2003.dmp
FULL=Y
IGNORE=Y
LOG=/<dir>/ow5000.log
c. Execute the following command:
imp parfile = fullimport.cntl
Note: See Possible Errors During the Import.
3. Rename sqlnet.ora_orig back to sqlnet.ora (renamed in Step 9 on page 119).
If you do not have sqlnet.ora_orig in $ORACLE_HOME/network/admin, create a sqlnet.ora

file like this as Oracle user (e.g., ora10g) in the $ORACLE_HOME/network/admin directory:
NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
)
)
4. Upgrade the OpenWorks schemas owsys and ow_admin_utils.
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
SQL>create user ora10g identified by ora10g;
SQL>grant connect, create session to ora10g;
b. As the Oracle user (e.g., ora10g), set the following environment variable. For example:
su - ora10g
setenv ORACLE_SID ow5000
Note: ow5000 is OpenWorks database SID name, for example: ow5000
setenv OWSYSSID ow5000.lgc.com
Note: ow5000.lgc.com is the alias name in $ORACLE_HOME/network/admin/

tnsnames.ora.
setenv OW_USER ora10g

setenv OW_PASSWORD ora10g
setenv OWHOME /d01/ow_nc
setenv ORACLE_HOME /d01/ora10g/OraHome1
setenv PATH ${OWHOME}/bin:${ORACLE_HOME}/bin:${PATH}
setenv LM_LICENSE_FILE 2014@owlic5
c. Set the LD_LIBRARY_PATH environment variable based on the Oracle server:
For 32-bit Oracle:
setenv LD_LIBRARY_PATH ${ORACLE_HOME}/lib:${OWHOME}/

lib:${LD_LIBRARY_PATH}
For 64-bit Oracle:
setenv LD_LIBRARY_PATH ${ORACLE_HOME}/lib32:${OWHOME}/

lib:${LD_LIBRARY_PATH}
d. Make sure an entry is made in $OWHOME/conf/district.dat for sid ow5000, otherwise

you will receive an “ERROR: No entry found for <SID_NAME>.”
OW5000 /d01/owhome/conf "OW5000" OW5000
d. Run the following upgrade command as the Oracle owner (ora10g):
$OWHOME/bin/owsysUpgradeR5000 <owsyssid> <log file directory>
For example:
$OWHOME/bin/owsysUpgradeR5000 ow5000 /d01/owjune/
3. If the tablespace data file structure in the ow2003_tablespace.sql file is NOT modified, skip
this step and go to Step 4. Otherwise, remove the invalid entries from the
LMSYS.OW_LMSYS_DB_DIR table as follows.
SQL>select dir_path from lmsys.OW_LMSYS_DB_DIR;
DIR_PATH
/d01/ora9i/OraHome1/owprojects/
Asssume the database data file is modified from
/d01/ora9i/OraHome1/owprojects to
/d01/ora10g/OraHome1/owprojects in ow2003_tablespace.sql.
SQL>delete from lmsys.OW_LMSYS_DB_DIR where dir_path='/d01/ora9i/

OraHome1/owprojects';
Note: If the entry “/d01/ora10g/OraHome1/owprojects/” already exists in the

LMSYS.OW_LMSYS_DB_DIR table go to Step 4.
SQL>insert into lmsys.OW_LMSYS_DB_DIR values ('DATA', '/d01/

ora10g/OraHome1/owprojects');
SQL>commit;
Note: Use the $OWHOME/bin/dboradir script to maintain the Oracle database locations.
4. 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
The result of ow2003_users.sql will look similar to the following:
create user owjune identified by owjune;

create user owtest identified by owtest;
grant MANAGE_EMPTY to OWJUNE;
grant L_INTERP_FLOUNDER to OWJUNE;
grant OW_ADMINISTRATOR to OWJUNE;
insert into owsys.ow_sys_user (user_id) values ('OWJUNE');
insert into owsys.ow_sys_user (user_id) values ('OWTEST');
commit;
Optionally, to change the password for OpenWorks project user “owjune,” do the following:
SQL>alter user owjune identified by xxxxxx;
where "xxxxxx" is the new password for OpenWorks user “owjune.”
Exit SQL*Plus.
5. 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.
a. Create/update a user of the OpenWorks database in the R5000 environment that matches
the owner of your projects in the 2003 environment that was created during the
ow2003_users.sql process, in this case OWJUNE.
i. If you already have an OpenWorks R2003 lgcuser, do the following:
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
ii. To create a new lgcuser, do the following:
su - root
OWHOME=<OpenWorks home directory>
export OWHOME
cd ${OWHOME}/bin
./lgcuser
Select option 2 to create a new user account
Select option 7 to quit
b. Assign the OW_ADMINISTRATOR role to the Oracle internal user:
i. Login as lgcuser.
ii. Launch the OpenWorks Command Menu: ${OWHOME}/bin/startow.
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>.
v. Select the OW_ADMINISTRATOR option.
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.
d. Upgrade the project from the GUI:
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.
e. Or, upgrade the project in batch mode:
Note: Before upgrading an OpenWorks project in batch mode, set these two environment
variables first:
setenv OW_USER owjune
setenv OW_PASSWORD owjune
where owjune is the OpenWorks project user and password.
• If there is no seismic project to upgrade, do the following:
$OWHOME/bin/projectUpgradeR5000 <Project Name> <OWSYSSID> <User

Specified Log Directory> <Create Directory Flag>
• If there is a seismic project to upgrade, do the following:
$OWHOME/bin/OWRuntimeLauncher.sh OwBatchUpgrade ALL
Possible Errors During the Import
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.
IMP-00017: following statement failed with ORACLE error 12913:
"CREATE TABLESPACE "RBS" DATAFILE '/pa/oracle/dbs_2/database/

datafiles/fla"
"nders/rbsflanders.dbf' SIZE 209715200 DEFAULT

STORAGE(INITIAL 2097152"
" NEXT 2097152 MINEXTENTS 10 MAXEXTENTS 505 PCTINCREASE 50)

ONLINE PERMANENT"
"ORARY "
IMP-00003: ORACLE error 12913 encountered
ORA-12913: Cannot create dictionary managed tablespace
"CREATE TABLESPACE "TEMP" DATAFILE '/pa/oracle/dbs_3/database/

datafiles/fla"
"nders/tempflanders.dbf' SIZE 104857600 DEFAULT

STORAGE(INITIAL 26214"
"4 NEXT 262144 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0)

ONLINE TEMP"
"ORARY "
ORA-12913: Cannot create dictionary managed tablespace
2. The GLOBAL_NAME in R2003 does not match the GLOBAL_NAME in OpenWorks

5000.0.0. The following error can be safely ignored. For more information on this Oracle error,
contact Landmark Customer Support and reference Solution Document 140760.
"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 "SYS.DBMS_SYS_ERROR", line 86
ORA-06512: at "SYS.DBMS_DEFER_IMPORT_INTERNAL", line 30
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.
IMP-00019: row rejected due to ORACLE error 1
ORA-00001: unique constraint (SYSTEM.HELP_TOPIC_SEQ) violated
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.
"ALTER TABLE "REPCAT$_PRIORITY_GROUP" ADD CONSTRAINT

"REPCAT$_PRIORITY_GROUP"
"_C1" CHECK (data_type_id in (1, 2, 3, 4, 5, 6, 7)) ENABLE

NOVALIDATE"
ORA-02264: name already used by an existing constraint
IMP-00019: row rejected due to ORACLE error 1
ORA-00001: unique constraint (SYSTEM.REPCAT$_RESOL_METHOD_PK)

violated
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.
"ALTER TABLE "DEF$_CALLDEST" ADD CONSTRAINT

"DEF$_CALL_DESTINATION" FOREIGN "
"KEY ("DBLINK") REFERENCES "DEF$_DESTINATION" ("DBLINK") ENABLE

NOVALIDATE"
ORA-02270: no matching unique or primary key for this column-list
Appendix: Prerequisites & Configurations
This appendix contains the procedures to prepare Linux and Solaris machines for Oracle and
OpenWorks. It also contains other configuration information.
• Linux 32-bit Prerequisites
• Linux 64-bit Prerequisites
• Solaris 10 (SPARC) 64-bit Prerequisites
• Windows: Installing Oracle on DHCP Computers
Version 5000.0.0.3 Appendix: Prerequisites & Configurations: 129

Creating an Oracle User
In Solaris and Linux, Landmark’s Pre-Oracle utility can create an Oracle sser as well as set kernel
parameters. This procedure shows how an Oracle user can be create manually.
Solaris and Linux
To create an Oracle user in Linux or Solaris, do the following:
1. Create the dba group if it does not exist:
• Log on as root.
• Execute the command: “/usr/sbin/groupadd -g 501 dba” or
• Add the line “dba:x:501:” line to the /etc/group file
2. Create the new Oracle user (e.g., ora10g):
• Log on as root.
• Execute the following command:
/usr/sbin/useradd -d /d01/ora10g -g dba -s /bin/csh -u 7777 ora10g
where /d01/ora10g is the home directory of ora10g, dba is the group name, and 7777 is the
uid (user id)
• Execute the command: chmod -R 775 /d01/ora10g
3. Edit the new Oracle user’s login script:
• Log on as the Oracle user (e.g., ora10g).
• Add the following lines to the ora10g .login file, if they do not exist. Use values
appropriate to your setup:
Linux 32-bit
setenv ORACLE_SID owmarlin

setenv ORACLE_OWNER ora10g
setenv OW_HOME_DIR $HOME
setenv ORACLE_BASE /d01/ora10g
setenv ORACLE_HOME ${ORACLE_BASE}/OraHome1
umask 022
130 Appendix: Prerequisites & Configurations: Creating an Oracle User Version 5000.0.0.3
setenv PATH /usr/bin:${PATH}:${ORACLE_HOME}/bin

if ($?LD_LIBRARY_PATH == 0) then
setenv LD_LIBRARY_PATH ${ORACLE_HOME}/lib32:${ORACLE_HOME}/lib
else
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:${ORACLE_HOME}/
lib32:${ORACLE_HOME}/lib
endif
setenv CLASSPATH ${ORACLE_HOME}/JRE/lib:${ORACLE_HOME}/JRE/lib/
rt.jar:${ORACLE_HOME}/jlib
Linux 64-bit

umask 022
else
endif
Solaris 10 (SPARC) 64-bit

umask 022
else
endif
Version 5000.0.0.3 Appendix: Prerequisites & Configurations: Creating an Oracle User 131
Create Oracle User
1. Launch User Accounts from the Control Panel.
The User Accounts window opens.
2. On the Advanced tab, click Advanced.
The Local Userrs and Groups window opens.
3. Click the Users folder in the Local Users and Groups (Local) pane.
4. Select Action > New User.
The New User window opens.
5. In the User Name field, type ora10g.
6. In the Full Name field, type ora10g.
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.
9. In the Confirm Password field, retype the password.
10.Uncheck the “User must change password at next logon” box.
11.Click Create.
12.Close the Local Users and Groups window.
13.In the User Accounts window, select ora10g, then click Properties.
The <DOMAIN>/ora10g Properties window opens.
14.Click the Group Membership tab, then click Other, then select Administrators from the list.
15.Click OK. The <DOMAIN>/ora10g Properties window closes.
16.Click OK in the User Accounts window.
17.Close the Control Panel.
132 Appendix: Prerequisites & Configurations: Creating an Oracle User Version 5000.0.0.3
Linux 32-bit Prerequisites
Check Software Packages (RPMs) on Linux 32-bit Servers and Clients
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
Check the RPMs using the following command:
rpm -q binutils compat-db control-center gcc gcc-c++ glibc glibc-

common libstdc++ libstdc++-devel make sysstat libaio
Check Swap Space on Linux 32-bit Servers
Oracle requires approximately 3GB of swap space. Check the swap space using the following
command:
# grep SwapTotal /proc/meminfo
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.
RAM Swap Space
Between 1024 MB and 2048 MB 1.5 times the size of RAM

Between 2049 MB and 8192 MB Equal to the size of RAM
More than 8192 MB 0.75 times the size of RAM
Version 5000.0.0.3 Appendix: Prerequisites & Configurations: Linux 32-bit Prerequisites 133
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.
To add a 1GB swap file:
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:
dd if=/dev/zero of=/swapfile bs=1024 count=1048576
3. Setup the swap file with the command:
/sbin/mkswap /swapfile
• To enable the swap file immediately but not automatically at boot time:
/sbin/swapon /swapfile
• To enable it at boot time, edit /etc/fstab to include:
/swapfile swap swap defaults 0 0
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:
cat /proc/swaps or free
134 Appendix: Prerequisites & Configurations: Linux 32-bit Prerequisites Version 5000.0.0.3
Set Shell Limits for the Oracle User on Linux 32-bit Servers
To improve the performance of the software on Linux systems, you must increase the following
shell limits for the Oracle user (e.g., ora10g):
Shell Limit Item in Hard Limit

limits.conf
Maximum number of open file descriptors nofile 65536
Maximum number of processes available to a single user nproc 16384
To increase the shell limits:
1. Add the following lines to the /etc/security/limits.conf file:
ora10g soft nproc 2047

ora10g hard nproc 16384
ora10g soft nofile 1024
ora10g hard nofile 65536
2. Add or edit the following line in the /etc/pam.d/login file:
session required /lib/security/pam_limits.so
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:
if ( $USER == "ora10g" ) then

limit maxproc 16384
limit descriptors 65536
endif
Configure Kernel Parameters on Linux 32-bit Servers
Note: Skip this section if you will use Landmark’s Pre-Oracle utility to create the Oracle user and
set the kernel parameters.
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.
Parameter Value File
semmsl semmns semopm 250 32000 100 /proc/sys/kernel/sem

semmni 128
shmall 2097152 /proc/sys/kernel/shmall
shmmax Half the size of /proc/sys/kernel/shmmax

physical
memory (in
bytes)
shmmni 4096 /proc/sys/kernel/shmmni
file-max 65536 /proc/sys/fs/file-max
ip_local_port_range 1024 65000 /proc/sys/net/ipv4/ip_local_port_range
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.
shmall, shmmax, and shmmni # /sbin/sysctl -a | grep shm
file-max # /sbin/sysctl -a | grep file-max
ip_local_port_range # /sbin/sysctl -a | grep ip_local_port_range
This command displays a range of port numbers.
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.
Linux 64-bit Prerequisites
Check Software Packages (RPMs) on Linux 64-bit Servers and Clients
For 10g R2 (64-bit) on RHEL 5 x86_64, the document “Oracle Database Release Notes 10g
Release 2 (10.2) for Linux x86-64” lists the following required package versions or higher:
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
The result should be: “x86_64 x86_64”
2. Check the RPMs using the following command:
rpm -q --qf '%{NAME}-%{VERSION}-%{RELEASE} (%{ARCH})\n' binutils

compat-db control-center gcc gcc-c++ glibc glibc-common libstdc++
libstdc++-devel make sysstat libaio
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.
Check Swap Space on Linux 64-bit Servers
Oracle requires approximately 3GB of swap space. Check the swap space using the following
command:
# grep SwapTotal /proc/meminfo
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.
space requirement.
RAM Swap Space
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.
To add a 1GB swap file:
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:
dd if=/dev/zero of=/swapfile bs=1024 count=1048576
3. Setup the swap file with the command:
/sbin/mkswap /swapfile
• To enable the swap file immediately but not automatically at boot time:
/sbin/swapon /swapfile
• To enable the swap file at boot time, edit /etc/fstab to include:
/swapfile swap swap defaults 0 0
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
cat /proc/swaps or free
Set Shell Limits for the Oracle User on Linux 64-bit Servers
To improve the performance of the software on Linux systems, you must increase the following
shell limits for the Oracle user (e.g. ora10g):
Shell Limit Item in limits.conf Hard Limit

Maximum number of open file descriptors nofile 65536
Maximum number of processes available to a single user nproc 16384
To increase the shell limits:
1. Add the following lines to the /etc/security/limits.conf file:
ora10g soft nproc 2047

ora10g hard nproc 16384
ora10g soft nofile 1024
ora10g hard nofile 65536
2. Add or edit the following line in the /etc/pam.d/login file, if it does not already exist:
session required /lib/security/pam_limits.so
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:
if ( $USER == "ora10g" ) then

limit maxproc 16384
endif
Configure Kernel Parameters on Linux 64-bit Servers
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.
Parameter Value File
semmsl semmns semopm 250 32000 100 128 /proc/sys/kernel/sem

semmni
shmall 2097152 /proc/sys/kernel/shmall
shmmax Half the size of /proc/sys/kernel/shmmax

physical memory (in
bytes)
shmmni 4096 /proc/sys/kernel/shmmni
file-max 65536 /proc/sys/fs/file-max
ip_local_port_range 1024 65000 /proc/sys/net/ipv4/ip_local_port_range
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.
shmall, shmmax, and shmmni # /sbin/sysctl -a | grep shm
file-max # /sbin/sysctl -a | grep file-max
ip_local_port_range # /sbin/sysctl -a | grep ip_local_port_range
This command displays a range of port numbers.
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.
Solaris 10 (SPARC) 64-bit Prerequisites
Configure Kernel Parameters on Solaris 10 Servers
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.
Parameter Resource Control Recommended Value
noexec_user_stack NA 1
semsys:seminfo_semmni project.max-sem-ids 100
shmsys:shminfo_shmmax project.max-shm-memory 4294967295
shmsys:shminfo_shmni project.max-shm-ids 100
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:
# id -p // to verify the project id

uid=0(root) gid=0(root) projid=1 (user.root)
# prctl -n project.max-shm-memory -i project user.root
# prctl -n project.max-sem-ids -i project user.root
If you must change any of the current values, do so as follows:
144 Appendix: Prerequisites & Configurations: Solaris 10 (SPARC) 64-bit Prerequisites

1. To modify the value of max-shm-memory to 4 GB:
# prctl -n project.max-shm-memory -v 4gb -r -i project user.root
2. To modify the value of max-sem-ids to 256:
# prctl -n project.max-sem-ids -v 256 -r -i project user.root
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
4. Save the /etc/system file.
5. As root, add the value of max-shm-memory for the Oracle user, e.g., ora10g:
#projadd –c “ora10g” user.ora10g

#projmod –K “project.max-shm-memory=(privileged,4GB,deny)” user.ora10g
Check Swap Space on Solaris 10 Servers
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.
space requirement.
RAM Swap Space
Version 5000.0.0.3Appendix: Prerequisites & Configurations: Solaris 10 (SPARC) 64-bit Prerequisites 145
Disable Screen and Power Managers on Solaris 10
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.
Disabling the Screen Manager in CDE
To disable the activity of the Screen Manager, do the following:
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.
8. Close other unnecessary windows.
Disabling the Power Manager in CDE
To disable the activity of the Power Manager (dtpower), do the following:
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).
2. To display the Dtpower dialog:
• Enter the following command in an xterm:
/usr/openwin/bin/dtpower &
or
146 Appendix: Prerequisites & Configurations: Solaris 10 (SPARC) 64-bit Prerequisites

• 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.
• Double-click the Power Manager item to display the Dtpower dialog.
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.
Version 5000.0.0.3Appendix: Prerequisites & Configurations: Solaris 10 (SPARC) 64-bit Prerequisites 147
Windows: Installing Oracle on DHCP Computers
Prerequisites for Installing Oracle on DHCP Computers
Check if a Loopback Adapter is Installed on the Computer
To check if a loopback adapter is installed on your computer, run the ipconfig /all command:
SYSTEM_DRIVE:\> ipconfig /all
If there is a loopback adapter installed, you will see a section that lists the values for the loopback
adapter. For example:
Ethernet adapter Local Area Connection 2:
Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 199.999.99.999
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Installing a Loopback Adapter on Windows 2003 or Windows XP
To install a loopback adapter on Windows 2003 or Windows XP:
1. Open the Windows Control Panel.
2. Double-click Add Hardware to start the Add Hardware wizard.
3. In the “Welcome” window, click Next.
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.
148 Appendix: Prerequisites & Configurations: Windows: Installing Oracle on DHCP Computers
8. In the “Select Network Adapter” window, make the following selections:
• Manufacturer: Select Microsoft.
• Network Adapter: Select Microsoft Loopback Adapter.
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.
12.If you are using Windows 2003, restart your computer.
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:
• 192.168.x.x (x is any value between 0 and 255)
• 10.10.10.10
• Subnet mask: Enter 255.255.255.0.
• Record the values you entered; you will them need later in this procedure.
• Leave all other fields empty.
• Click OK.
17.Click OK.
18.Close Network Connections.
19.Restart the computer.
Version 5000.0.0.3Appendix: Prerequisites & Configurations: Windows: Installing Oracle on DHCP Com-
20.Add a line to the SYSTEM_DRIVE:\WINDOWS\system32\drivers\etc\hosts file with the

following format, after the localhost line:
IP_address hostname.domainname hostname
where:
• IP_address is the non-routable IP address you entered in step 16.

• hostname is the name of the computer.
• domainname is the name of the domain.
For example:
10.10.10.10 mycomputer.mydomain.com mycomputer
21.Check the network configuration:
• 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.
150 Appendix: Prerequisites & Configurations: Windows: Installing Oracle on DHCP Computers
Appendix: About Oracle Wallet
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.
On servers, the OpenWorks 5000.0.0 Database Installation process configures everything

necessary for Oracle Wallet. On clients, the OpenWorks 5000.0.0 Installation process configures
everything necessary for Oracle Wallet.
However, in non-standard installs or development environments, you must be aware of the

requirements of the Oracle Wallet system.
Environment Changes
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.
Version 5000.0.0.3 Appendix: About Oracle Wallet: Overview 151

On Windows
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
(DIRECTORY=%OW_HOME_DIR%\wallet)
)
)
On Linux/Solaris
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
)
)
Notes
• The OW_USER and OW_PASSWORD environment settings are obsolete.
• 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.
• The cached password in encrypted format in a file created by OpenWorks on a client

machine is obsolete.
• 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”
152 Appendix: About Oracle Wallet: Environment Changes Version 5000.0.0.3

OpenWorks Database Installer Configures Oracle Wallet
OW_HOME_DIR must be set before running the OpenWorks Database installer. If

OW_HOME_DIR is not set, the following error dialog will open:
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.
OpenWorks Installation and sqlnet.ora on Client Machines
The OpenWorks installation configures the wallet entry in the sqlnet.ora file on client machines. If
you change the location pointed to by the TNSADMIN variable after the install you must ensure
that a valid sqlnet.ora is in the new location.
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.
Version 5000.0.0.3 Appendix: About Oracle Wallet: Environment Changes 153

154 Appendix: About Oracle Wallet: Environment Changes Version 5000.0.0.3

Appendix: Troubleshooting
Deleting or Creating a Second SID
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.
Workaround to Delete an Existing Instance
1. Log on to the Oracle server as the Oracle user, e.g., ora10g.
2. Create a temporary TNS_ADMIN directory to contain backup sqlnet.ora and tnsnames.ora

files; e.g.,
mkdir -p /d01/ora10g/temp/network/admin
3. Copy the original sqlnet.ora and tnsnames.ora files from $ORACLE_HOME/network/admin

to the new directory, e.g.,
cp $ORACLE_HOME/network/admin/sqlnet.ora /d01/ora10g/temp/network/admin
cp $ORACLE_HOME/network/admin/tnsnames.ora /d01/ora10g/temp/network/
admin
4. Edit /d01/ora10g/temp/network/admin/sqlnet.ora and remove the following wallet text:
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
)
)
5. Save the /d01/ora10g/temp/network/admin/sqlnet.ora file after removing the wallet text.
Version 5000.0.0.3 Appendix: Troubleshooting: Deleting or Creating a Second SID 155

6. Set the TNS_ADMIN environment variable to point to the new directory, e.g.,
setenv TNS_ADMIN /d01/ora10g/temp/network/admin
7. Run the Oracle dbca utility and delete the existing database.
Workaround to Create an Additional OpenWorks Instance
2. Create a temporary TNS_ADMIN directory to contain backup sqlnet.ora and tnsnames.ora

files, e.g.,
mkdir -p /d01/ora10g/temp/network/admin
3. Copy the original sqlnet.ora and tnsnames.ora files from $ORACLE_HOME/network/admin

to the new directory; e.g.,
cp $ORACLE_HOME/network/admin/sqlnet.ora /d01/ora10g/temp/network/admin
cp $ORACLE_HOME/network/admin/tnsnames.ora /d01/ora10g/temp/network/
admin
4. Edit /d01/ora10g/temp/network/admin/sqlnet.ora and remove the following wallet text:
WALLET_LOCATION=
(SOURCE=
(METHOD=FILE)
(METHOD_DATA=
)
)
5. Save the /d01/ora10g/temp/network/admin/sqlnet.ora file after removing the wallet text.
6. Set the TNS_ADMIN environment variable to point to the new directory, e.g.,
setenv TNS_ADMIN /d01/ora10g/temp/network/admin
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
156 Appendix: Troubleshooting: Deleting or Creating a Second SID Version 5000.0.0.3

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.,
setenv OW_HOME_DIR ${HOME}
8. Set the ORACLE_SID to the new value that you want to create, e.g.,
setenv ORACLE_SID owtest
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)
)
)
11.Save the $ORACLE_HOME/network/admin/tnsnames.ora file with the changes.
12.Unset the TNS_ADMIN environment variable.
unsetenv TNS_ADMIN
13.Remove the temporary TNS_ADMIN directory that you created earlier.
rm -rf /d01/ora10g/temp/network/admin
14.Test the connection to the database.
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
Version 5000.0.0.3 Appendix: Troubleshooting: Deleting or Creating a Second SID 157

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.
158 Appendix: Troubleshooting: Deleting or Creating a Second SID Version 5000.0.0.3

Adobe Reader
Possible GTK Errors on Solaris
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.
The following is taken from the Adobe 801 Launch file:
• Adobe Reader 8.1.1 doesn't launch on Solaris
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).
Updating the GTK Libraries on Solaris, from BlastWave.org
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
4. Install gtk+ using pkg-get
/opt/csw/bin/pkg-get -i gtk2
5. Set the LD_LIBRARY_PATH appropriately before running acroread
Version 5000.0.0.3 Appendix: Troubleshooting: Adobe Reader 159

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.
Linux: Other Readers
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:
Main Menu > Programs > Graphics > 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.
Linux: Opening Acrobat Files in the Nautilus File Manager
The Adobe installation program installs the Acrobat Reader files so that you can run Acrobat
Reader from the command line (for example,
/usr/local/Acrobat5/bin/acroread ). The Gnome desktop provides more than a
terminal window and a command line to start a program and open a file. A Nautilus window
allows you to double-click on a file and open it.
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.
3. Click Edit List. The Edit Application List dialog opens.
4. Click Add Application in the Add Application List dialog. The Edit Application dialog opens.
5. In the Add Application dialog, do the following:

160 Appendix: Troubleshooting: Adobe Reader Version 5000.0.0.3
• In Application Name, enter a name for the application. For example:
Adobe Acrobat Reader 7
• 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.
9. Click OK in the File Types And Programs dialog.
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
Linux: Running Acrobat Reader from the Gnome Panel
If you want to run Acrobat Reader before attempting to open an Acrobat file, you can run
acroread from the command line, or you can insert it in the menu in the Gnome panel.
To insert an Acrobat Reader item in the menu of the Gnome panel, do the following:
1. In a terminal window, log in as Super User
su - (su followed by a dash)

Password:
2. Enter gmenu to open the GNOME Menu Editor window.
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.
5. In the Basic tab, do the following:
• In Name, enter a name for Acrobat Reader. For example:
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 &
• In Type, select Application.
• If you want to associate an icon with Acrobat Reader, do the following:
—Click the Icon button to open the Choose An Icon dialog.
—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
—Click OK in the Choose An Icon dialog.
• Uncheck Run In Terminal.
6. Click the Save button under the Basic tab.
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
162 Appendix: Troubleshooting: Adobe Reader Version 5000.0.0.3

Possible Syntax Error in Linux
After installing Adobe Reader in Linux, you may see the following error :
expr: syntax error

expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
expr: syntax error
[2]+ Killed ./acroread

[root@owhp64 bin]#
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.
Fix Adobe Acrobat Reader's "expr: syntax error" message
Find acroread (it is a shell script, probably in /usr/local/bin or under whichever-directoy-you-

specified-during-installation/bin) and apply this patch:
--- acroread.old 2007-06-01 18:18:49.000000000 -0500

+++ acroread 2007-06-01 18:20:57.000000000 -0500
@@ -415,7 +415,7 @@
return 1
fi
- echo $mfile| sed 's/libgtk-x11-$[0-

9]*$.0.so.0.$[0-9]$00.$[0-9]*$\|$.*$/\1\2\3/g'
+ echo $mfile| sed 's/libgtk-x11-$[0-
9]*$.0.so.0.$[0-9]*$00.$[0-9]*$\|$.*$/\1\2\3/g'
return 0
fi
Alternatively, edit acroread using a text editor such as vi(1) and add an asterisk after the second
[0-9] block in line 418.

Linux & Solaris: Process Resource Limits
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 .
On Linux, it is best to change the system limits by changing /etc/sysctl.conf . To some

extent, changing the limits in the bash interpreter with the ulimit built-in command can be
useful.
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.
Changing a Process Resource Limit with ulimit (or limit)
The number of file descriptors allowed for a process and its subprocesses must be sufficiently
high. If not, a system error may occur. The error indicates the system cannot open any more files
or create new processes. This error occurs when all the available file descriptors have been used.
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
unlimit descriptors (sets the limit to the hard limit, which is

1024 in this case)
164 Appendix: Troubleshooting: Linux & Solaris: Process Resource Limits Version 5000.0.0.3
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.
Large Files
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.
Version 5000.0.0.3 Appendix: Troubleshooting: Linux & Solaris: Process Resource Limits 165
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 164.
166 Appendix: Troubleshooting: Linux & Solaris: Process Resource Limits Version 5000.0.0.3
Appendix: Removing Oracle &

OpenWorks
Use the procedures in this appendix to uninstall Oracle server and then to uninstall OpenWorks.
Removing Oracle Server
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.
This procedure has the following assumptions:
• 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.
• You want to cleanly uninstall Oracle.
• You want to delete all Oracle instances and databases.
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.
Version 5000.0.0.3 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server 167
Deleting Oracle 10g
Use the Oracle Universal Installer to delete an Oracle 10g installation.
1. Log in as an OpenWorks user.
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:
host.com {OpenWorks}% orastat

… …
… …
… …
------------------------------------------------------------------
# ORACLE tablespace files on this machine are ...
File Total MBytes Remaining MBytes
---------------------------------------- ------------ ------------
/d01/ora10g/OraHome1/databa 5 4.953125
se/datafiles/owman10g/ow_admin_utils_owma
n8i.dbf
/d01/ora10g/OraHome1/databa 20 13.78125
se/datafiles/owman10g/owsys_owman10g.dbf
… …
… …
… …
------------------------------------------------------------------
# project location list on this machine is ...
Project Locations
----------------------------------------
/export/home1/owprojects
/export/home2/owprojects_2
------------------------------------------------------------------
3. Log out from the OpenWorks user account.
4. Log in as the Oracle user (ora10g).
5. Set the DISPLAY environment variable. For example:
setenv DISPLAY hostname:0.0
6. Check that no users are logged into the Oracle database instances. For example, you might
execute the following with SQL*Plus (sqlplus):
168 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server Version 5000.0.0.3
[oracle@sealy ~]$ sqlplus internal

SQL> select sid, serial#, user#, username, machine, program, server,
2 status, command, type
3 from v$session
4 order by username;
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).
• For instance, to start dbca .
$ORACLE_HOME/bin/dbca
The Oracle Database Configuration Assistant dialog displays.
• Select the Delete A Database radio button.
• 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.
• Click Yes to confirm your desire to delete the databases.
• After the databases are deleted, click OK.
8. In a terminal window, check whether any database processes are still running. For example:
ps –ef | grep –i OracleSID
9. If database processes exist, do the following:
setenv ORACLE_SID OracleSID

svrmgrl
SVRMGR> connect internal
SVRMGR> shutdown abort
SVRMGR> exit
10.Stop the listener by entering the following:
lsnrctl stop
11.Use the Oracle Universal Installer to remove the Oracle software. For example:
• Start the Oracle Universal Installer.
$ORACLE_HOME/bin/runInstaller
The Oracle Universal Installer dialog displays.
• Click Deinstall Products. The Inventory dialog displays.
• 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.
• Click Remove to delete all of the installed Oracle products.
• Click Yes to confirm your desire to delete the software.
• Click Close in the Inventory dialog.
• Click Exit in the Oracle Universal Installer dialog.
12.Exit from the Oracle user account. For example, enter Exit in the terminal window.
13.Log on as Super User (or root). For example, su - root .
14.Remove the following directories and files:
• 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 -f /etc/oraInst.loc /etc/oratabDefault Location in Linux
rm -f /var/opt/oracle/oraInst.loc /var/opt/oracle/oratabDefault Location

in Solaris
• Remove the Oracle home directory. For example:
rm –rf OracleUserHomeDir
170 Appendix: Removing Oracle & OpenWorks: Removing Oracle Server Version 5000.0.0.3
• In /usr/local/bin , remove coraenv, dbhome, and oraenv . For example:
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.
Removing OpenWorks Server
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.
2. Set the OpenWorks home environment variable, OWHOME. For example:
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
172 Appendix: Removing Oracle & OpenWorks: Removing OpenWorks Server Version 5000.0.0.3

OpenWorks SoftwareInstallation Procedures

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OpenWorks SoftwareInstallation Procedures

Uploaded by

Copyright:

Available Formats

OpenWorks® Software

Release 5000.0.0.3 September 2008

Landmark Graphics Corporation

$OWHOME/docs/third_party.pdf Linux or Solaris

Release 5000.0.0.3 iii

Welcome to the OpenWorks® Software ........................................................................................ 1

Before You Begin .......................................................................................................................... 2

New District Functionality ................................................................................................. 3

System Requirements .................................................................................................................... 4

Minimum Platform Specifications ..................................................................................... 4

Default Minimum OpenWorks Project Size ...................................................................... 4

Graphics Cards ................................................................................................................... 4

Software Specfications ...................................................................................................... 4

Third Party Applications License Agreements .............................................................................. 5

Accessing the OpenWorks Documentation ................................................................................... 6

Online Help ........................................................................................................................ 6

Documents in Portable Document Format (PDF) Format ................................................. 6

Installing Acrobat Reader ............................................................................................ 6

Version 5000.0.0.3 Contents v

Installation Workflow .................................................................................................................... 7

Installation Checklist: All Platforms .............................................................................................. 8

Linux 32-bit Server ...................................................................................................................... 11

Prerequisites and Procedures ........................................................................................... 11

Run Pre-Oracle: Linux 32-bit Server ............................................................................... 12

Modify the Linux 32-bit Release File .............................................................................. 13

Install Oracle Database Software (10.2.0.1.0) ................................................................. 13

Install Oracle 10g Release 2 Patch Set 2 (10.2.0.3.0) ...................................................... 15

Fix Directory Permission Problem .................................................................................. 16

Restore Linux Release File .............................................................................................. 17

Install OpenWorks 5000.0.0 Database ............................................................................ 17

Install OpenWorks 5000.0.0 Database Schemas on an Existing Oracle Database .......... 20

What’s Next? ................................................................................................................... 23

Linux 32-bit Client ....................................................................................................................... 24

Prerequisites and Procedures ........................................................................................... 24

Run Pre-Oracle: Linux 32-bit Client ............................................................................... 24

Modify the Linux 32-bit Release File .............................................................................. 25

Install Oracle Client Software (10.2.0.1.0) ...................................................................... 26

Install Oracle 10g Release 2 Patch Set 2 (10.2.0.3.0) ...................................................... 28

Fix Directory Permission Problem .................................................................................. 29

Restore Linux Release File .............................................................................................. 29

What’s Next? ................................................................................................................... 29

vi Contents Version 5000.0.0.3

Linux 64-bit Server ...................................................................................................................... 30

Prerequisites and Procedures ........................................................................................... 30

Run Pre-Oracle: Linux 64-bit Server ............................................................................... 30

Modify the Linux 64-bit Release File .............................................................................. 32

Install Oracle Database Software (10.2.0.1.0) ................................................................. 32

Install Oracle 10g Release 2 Patch Set 2 (10.2.0.3.0) ...................................................... 34

Fix Directory Permission Problem .................................................................................. 35

Restore Linux Release File .............................................................................................. 36

Install OpenWorks 5000.0.0 Database ............................................................................ 36

Install OpenWorks 5000.0.0 Database Schemas on an Existing Oracle Database .......... 39

What’s Next? ................................................................................................................... 42

Linux 64-bit Client ....................................................................................................................... 43

Prerequisites and Procedures ........................................................................................... 43

Run Pre-Oracle: Linux 64-bit Client ............................................................................... 43

Modify the Linux 64-bit Release File .............................................................................. 44

Install Oracle Client Software (10.2.0.1.0) ...................................................................... 45

Install Oracle 10g Release 2 Patch Set 2 (10.2.0.3.0) ...................................................... 47

Fix Directory Permission Problem .................................................................................. 48

Restore Linux Release File .............................................................................................. 48

What’s Next? ................................................................................................................... 48

Solaris 10 (SPARC) 64-bit Server ............................................................................................... 49

Prerequisites and Procedures ........................................................................................... 49