Global Database Technical Services
Standards
Installation Standards
for
Oracle 9i on Wintel
Version:
Status:
1.0
Final
Last printed:
3/9/2016 6:41:00 AM
Global Database Technical Services
Standards
Document Scope ........................................................................................................................... 1
Introduction 1
Terminology ................................................................................................................................... 1
Section 1.
Platform .................................................................................................................... 1
Section 2.
Requirements ........................................................................................................... 1
Section 3.
Flexibility .................................................................................................................. 3
Section 4.
Compliance ............................................................................................................... 4
Section 5.
Variance Procedure ................................................................................................. 5
Section 6.
Installation Bugs ...................................................................................................... 6
Page i
3/9/2016
Global Database Technical Services
Standards
Document Scope
This document contains the GDTS standards for installing Oracle server based software on
Microsoft servers.
Introduction
Uniform installation and common configuration of Oracle software across GDTS supported
Microsoft servers.
Terminology
See the GDTS Standards Terminology for the definition of guidelines, recommendations and
standards.
Section 1.
Platform
These standards apply to Microsoft Windows NT and Win2000 Servers.
Section 2.
Requirements
2.1 (R) GDTS will need a remote control tool to access the server. The recommendation for a
remote control tool is PCAnywhere. You cannot use WTS or Terminal Services
to install Oracle. An installation with WTS or Terminal Services is not supported and
several tools will not work after installation.
2.2 (R) Oracle should be the only application running on the server.
2.3 (S) Oracle should be installed on the “C:” drive of the server. Oracle must be installed with
an account that has administrative privileges.
2.3.1 (S) ORACLE_HOME name should be defined as the version of Oracle that you are
installing, an example would be ora9201s32 or ora9201e64. The
ORACLE_HOME name path should be similar, c:\Oracle\ora9201s32 or
c:\Oracle\ora9201e64, “9201” is the version release of Oracle. The “s” or “e” is
determined by if this is an Oracle Enterprise Edition installation or Standard
Edition installation, 32 or 64 at the end is the bit word size.
2.4 (S) Installing Perl on your new Server.
2.4.1 Copy folder Wintel_setup from GDTS shared drive location
s:gdts\_private to C:\temp on your new server.
2.4.2 On your server in folder c:\temp\Wintel_setup, just double click on the perl file
“*.msi”. It should be the only perl install file in c:\temp\Wintel_setup folder. Perl
should be installed on the “C:” drive of the server, example C:\Perl. You should
accept all defaults during the Perl install.
Page 1
3/9/2016
Global Database Technical Services
Standards
2.4.3 After the installation is complete you need to install 2 modules, DBI and DBD,
which do not come with the default installation. Instructions for installing these
modules can be found in GDTS’s web site document, “Installing Active State Perl
on Microsoft Servers”.
2.5 (S) Installation of GDTS standard admin utilities/directories for database maintenance.
2.5.1 Edit the script Wintel_setup.cmd to contain the proper drive letter for the
location of your scripts, this should usually be the “C” drive.
2.5.2 Run the file by double clicking on the file, Wintel_setup.cmd. This script will call
script Wintel_admin_dirs.cmd which will create the admin directories, and
populate the directories with standard GDTS perl scripts. The script will also
install gzip for file compression utility and blat for a mail utility in location
c:\Winnt\system32. The result should be directory structure similar to the
example, “C” was the location specified for admin directories.
c:\Cargill\Oracle\Bin
c:\Cargill\Oracle\Bin\Perl
c:\Cargill\Oracle\Cfg
c:\Cargill\Oracle\Logs
c:\Cargill\Oracle\Scripts
2.5.3 When steps 2.4 and 2.5 are complete you can clean up by deleting the
Wintel_setup folder on your server in location C:\temp.
2.6 (S) Performing installation of Oracle database software for “Standard” or “Enterprise” installs
should result in the same base products being installed. Additional products, upon customers
request may be installed if all licensing requirements are met. The list of base products to install
can only be arrived at by doing a “Custom” install and selecting the following products, do not
create a starter database during install and de-select any items that are not listed below. If you
are installing Oracle Standard Edition you must go to “Section 6 Installation Bugs” and
follow instructions in 6.1. If this is an Enterprise Installation you may continue.
Base Products to Install
Oracle 9i Database
-Oracle 9i
Oracle Net Service
-Oracle Net Listener
Oracle Enterprise Manager Products
-Oracle Intelligent Agent
Oracle 9i Development Kit
-Oracle C++ Call Interface
-Oracle Call Interface (OCI)
-Oracle ODBC Driver
-Oracle Programmer
-Oracle XML Developer
Oracle Windows Interfaces
-Oracle Performance Monitor for Windows NT
http://www.oracle.com/ip/deploy/database/oracle9i/index.html?packagingandoptions.html
Page 2
3/9/2016
Global Database Technical Services
Standards
2.7 (S) Client software installation is accomplished through an additional install by doing a client
install. You should select “Runtime” for install type and accept all defaults to complete your install.
2.8 (S) The Oracle Intelligent Agent and Oracle listener, should be run from the highest
$ORACLE_HOME version on the server. The services should be set to “automatic” to restart on
server reboot. The other older versions of Oracle Intelligent Agent and Oracle listener services
should be “disabled”.
2.9 (S) Use the TNS_ADMIN system variable with defined location of C:\Oracle\sqlnet.
Because the account system will start services, databases and the listener, this must be a
system variable and not a user variable. This location will be used for listener.ora, sqlnet.ora and
tnsnames.ora files. This will allow for multiple ORACLE_HOMES to use one set of sqlnet files.
Delete all of these files that are not in this location. To accomplish setting this variable, do the
following:
2.9.1
2.9.2
2.9.3
2.9.4
2.9.5
Right click on my computers and select properties.
Click on Advance tab and then go into Environment Variables.
In the systems variable window highlight variable OS and edit.
Change the name from OS to TNS_ADMIN and set variable value to
C:\Oracle\sqlnet. Click on Ok until you have exited the properties window.
Reboot the server.
2.10 (S) Modify the listener.ora file to contain the logging location for the listener.log file to be
located in c:\oracle\sqlnet. You can accomplish this by running the “Net Manager” tool
on the server or manually editing the listener.ora with the following 2 entries.
LOG_DIRECTORY_LISTENER = c:\oracle\sqlnet
LOG_FILE_LISTENER = listener.log
2.11 (R) The following server configuration must be verified or set with the system administrator.
-It is not recommended to have the database server act as a file and print server.
-If the server is used only as a database server you should maximize it as such.
start-menu, control-panel, Network and Dial up Connections, right click on Local area
Connection, properties, highlight File Print Sharing for Microsoft Networks, click on
properties and select Maximize data throughput for Network Applications. This sets
Large System Cache to Zero and reduces paging.
-Reduce Priority of Foreground Applications. System Properties, Advance Tab,
Performance Options, click on Background Services and Okay.
-If possible remove unused protocols. At a minimum TCP/IP should be installed.
-Page File Size should be 1 ½ times the server memory not to exceed 2 gig.
-Disable the following services: License Logging Service, Plug and Play, Remote Access
Auto Connection Manager, Remote Access Connection Manager and Telephony Server.
Section 3.
Flexibility
In rare cases, such as temporary proof-of-concept or simple evaluation set-ups where
independent servers are not available, web server or application server software can be run on
the same box as the Oracle Database Server.
The data-files path can be specified on drives other than D: if additional drives are available, such
as when EMC is implemented as an E: or F: drive.
Page 3
3/9/2016
Global Database Technical Services
Standards
Section 4.
Compliance
A post-install review with another DBA is required by GDTS.
Page 4
3/9/2016
Global Database Technical Services
Standards
Section 5.
Variance Procedure
Guidelines may be implemented with necessary and appropriate modifications without further
documentation.
Variations from Recommendations must be documented and sent to the Technical Review Group
for review.
Deviations from Standards require a variance. Document the change and the reasons for it and
submit to the Technical Review Group for review, discussion, and approval or denial.
Page 5
3/9/2016
Global Database Technical Services
Standards
Section 6.
Installation Bugs
6.1 There is a bug in Oracle 9i installations that will not be fixed until Oracle 10.x. This only
pertains to installations needing Standard Oracle verses Enterprise Oracle. When selecting a
Custom Install, Oracle automatically installs Enterprise Oracle and now your installation is
non-compliant with your Standard Oracle license agreement. Here is the workaround. From
your installation CD copy the file <cdrom-drive>:\Response\custom.rsp to c:\temp\custom.rsp
on your local server. The file c:\temp\custom.rsp will originally be “Read-only”, right click on
the file, select properties and un-check the “Read-only” box. Open the file c:\temp\custom.rsp
and search for the following string INSTALL_TYPE=”Custom” add the following 3 lines below
the INSTALL_TYPE=”Custom” line so that your entries look like the following and find the
below lines and set them all to true. These lines, when set to true, display all the normal
installer screens. When all the modification are made, save the file.
INSTALL_TYPE=”Custom”
# Parameter
: s_bundleName
# Type
: String
s_bundleName=STD
Set the below parameters:
SHOW_SPLASH_SCREEN=true
SHOW_WELCOME_PAGE=true
SHOW_COMPONENT_LOCATIONS_PAGE=true
SHOW_CUSTOM_TREE_PAGE=true
SHOW_SUMMARY_PAGE=true
SHOW_INSTALL_PROGRESS_PAGE=true
SHOW_REQUIRED_CONFIG_TOOL_PAGE=true
SHOW_OPTIONAL_CONFIG_TOOL_PAGE=true
SHOW_RELEASE_NOTES=true
SHOW_ROOTSH_CONFIRMATION=true
SHOW_END_SESSION_PAGE=true
SHOW_EXIT_CONFIRMATION=true
NEXT_SESSION=true
NEXT_SESSION_ON_FAIL=true
SHOW_DEINSTALL_CONFIRMATION=true
SHOW_DEINSTALL_PROGRESS=true
On the server where the install is taking place, open a command prompt window, change
directories to the servers cdrom-drive. At the command prompt type in the following
command and follow your install screens as you normally would keeping in mind to only install
the products listed in 2.6.
E:\> setup -responsefile c:\temp\custom.rsp
6.2 There is a bug with the 9.2 Intelligent Agent. This does not affect the installation but needs to
be addressed for before monitoring with Oracle Enterprise Manager will work properly.
Cut and paste the below link in your browser for description and resolution to the problem.
http://metalink.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&
p_id=201034.1
Page 6
3/9/2016