Global Database Technical Services
Installation Standards
For
Oracle9i On Unix
Version:
1.1
Status:
Final
Last Changed:
09/03/2016 06:41:00
Global Database Technical Services
Standards
Document Scope ............................................................................................................................. 1
Introduction ...................................................................................................................................... 1
Terminology ..................................................................................................................................... 1
Section 1.
Platform ...................................................................................................................... 1
Section 2.
Requirements............................................................................................................. 1
2.1
Oracle Unix Environment .................................................................................................. 1
2.2.
Oracle Home Naming Convention .................................................................................... 3
2.3.
Standard Product Installation List ..................................................................................... 6
Section 3.
Flexibility .................................................................................................................... 7
Section 4.
Compliance ................................................................................................................ 7
Section 5.
Variance Procedure ................................................................................................... 7
Page i
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
Document Scope
This document contains the GDTS standard for installation and configuration of Oracle9i
server based software on the Unix platform.
Introduction
Uniform installation and common configuration of Oracle9i software across GDTS supported
servers allows for maintenance by a larger number of DBAs and standard scripts than is
possible with unique installations.
Terminology
See the GDTS Standards Terminology for the definition of guidelines, recommendations and
standards.
Section 1. Platform
This standard covers Unix operating systems in general. Unix vendor specific notes are
included where necessary.
Section 2. Requirements
2.1
Oracle Unix Environment
The standard Unix environment includes the following.
2.1.1.(S) Verify that all Unix operating system patches have been applied per the Oracle
installation documentation. On HP-UX 11.x, command show_patches can be used
to display active patches.
Page 1
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
2.1.2.(S) Verify that all Unix operating system kernel parameters have been set at least to
minimum levels per GDTS standards. See:
http://www.gdts.cargill.com/documents/db_admin/oracle/kernelmap.htm
On HP-UX, kernel parameter overrides can be viewed in file /stand/system.
2.1.3.(S) Verify that the dba group is 121 in file /etc/group.
2.1.4.(S) Verify that the oracle account in file /etc/passwd is account number 5096 and is
in the dba group as the default group.
2.1.5.(S) Verify standard GDTS scripts and subdirectories are present under
/cargill/oracle. Standard scripts are available from the depot server under
/cargill/oracle.
2.1.6.(S) Verify standard Unix startup and shutdown scripts for Oracle are in place.
Standard scripts are available from the depot server under /etc/rc.config.d/oracle,
/sbin/init.d/oracle
2.1.7. (S) /etc/oratab (/var/opt/oracle/oratab on Sun) file. Verify the file is owned by
oracle:dba, permissions 644. This file contains all Oracle SIDs for the server. The
automatic startup switch should be set to Y for normal database startup upon server
startup. The file should contain an entry for SID bogus pointing to the highest
version of installed software, which will be used by the OEM agent and listener
processes.
2.1.8.(S) /etc/listener.ora file. Verify the file is owned by oracle:dba, permissions 644.
This file configures the listener used by all databases on the server. A standard
template file is available from the depot server under /cargill/oracle/cfg/listener.ora.
2.1.9.(R) /etc/tnsnames.ora file. This file should be created by executing a touch file
command as follows: touch /etc/tnsnames.ora. Verify that the file is owned by
oracle:dba, with the file permissions set to 644 (owner: read/write, group and global:
read only). This file should be empty; Oracle Names should be used instead.
Page 2
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
2.1.10. (R) $ORACLE_HOME/network/admin/sqlnet.ora file. Verify the file is owned by
oracle:dba, permissions 644. The physical server geographic location dependent
sqlnet.ora file to enable use of Oracle Names is available from:
http://www.gdts.cargill.com/documents/sqlnet/sqlnetclient.htm
2.1.11. (S) Verify Perl is installed under /opt/oracle/perl
2.1.12. (S) Verify gzip is installed and supports large files.
2.1.13. (S) Oracle Home root directory is /opt/oracle/product. Verify the directory is
owned by oracle:dba, permissions 750.
2.1.14. (S) ORACLE_BASE directory is /var/opt/oracle. Verify the directory is owned by
oracle:dba, permissions 755.
2.1.15. (S) Oracle account $HOME/.users.profile and .profile files. The .users.profile file
should use the setdb shell script to set the ORACLE_SID to bogus by default upon
login. Standard template files are available from the depot server under
/cargill/oracle/cfg.
2.1.16. (S) Oracle 9i requires the installation of Java 1.3x Development Kit. When
prompted to set the JDK Home, use the browse button to open a navigation window
and set the path to the Java 1.3x JDK, which will usually be /opt/java1.3. If you are
unable to locate the JDK Home on the server, contact UTS and have them install
the Java 1.3x JDK or higher release.
2.2. Oracle Home Naming Convention
The directory name directly under /opt/oracle/product denotes the version of Oracle
software installed.
2.2.1.Database Software
2.2.1.1.
Page 3
(S) The naming of the Oracle Home directory is the concatenation of:
-
The leading 4-digit database version number separated by periods.
-
Either the letter e (Enterprise Edition) or s (Standard Edition)
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
The bit version, 32 or 64.
-
Examples:
64-bit Enterprise Edition of base 9.2.0 patch to 9.2.0.3: 9.2.0.3e64
32-bit Standard Edition 9.2.0 base: 9.2.0.3s32
2.2.1.2.
(S) Standard Oracle Homes contain only non-extra cost Oracle Options.
If extra cost options are installed in an Oracle Home then a separate Oracle
Home is used. Use the above naming convention then add a x to the end.
Create a CARGILL_README file under this directory listing each of the extra
cost options that are installed and the business unit paying for them.
Example:
64-bit Enterprise Edition 9.2.0.3 with extra costs options installed:
9.2.0.3e64x
2.2.1.3.
(S) When doing a fresh install with the intention to immediately patch to a
point release, create the directory using the version of the patch. Do not
attempt to rename Oracle Home directories; this causes problems for the
Oracle Installer, which will not be able to recognize the directory.
2.2.1.4.
(S) Do not apply a patch to an existing Oracle Home. Instead create a
new Oracle Home directory using the appropriate base install and naming the
directory based upon the final patch version to be installed, then patch this
new directory.
2.2.1.5.
(S) When applying a patch, create a directory directly under the Oracle
Home called patchset to hold the patch. After the patch installation has been
completed, remove the patch files under the patchset directory and touch a
empty file into the patchset directory with the following naming convention:
version_applied_MonDD_YYYY where version is the 5 digit version of the
patch applied, and MonDD_YYYY is the date the patch was applied.
Page 4
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
Example: touch 9203_applied_Mar13_2003
2.2.2.Oracle Enterprise Manager Agent and Listener Software
2.2.2.1.
(S) OEM agent software should be installed with the Oracle database
software. The OEM agent and listener processes should run from the latest
release of software available on the server. As mentioned above, the SID
bogus in file oratab is used to set this ORACLE_HOME. Starting of the
listener and OEM agent processes from bogus is accomplished by script
/cargill/oracle/bin/lsnrctl which is available from the depot server under
/cargill/oracle/cfg/lsnrctl. Verify the file is owned by oracle:dba, permissions
700. Verify that $PATH is set correctly by issuing command “ type
lsnrctl” which should return “ lsnrctl is /cargill/oracle/bin/lsnrctl” . If it does
not, verify that the standard Oracle account $HOME/.users.profile and .profile
files are in place as stated above.
2.2.3.Oracle Names Software
Oracle Names software is only installed on specific designated servers. It is not
installed as part of a standard installation.
2.2.3.1.
(S) Oracle Names software is installed into its own Oracle Home. This
home is used for Oracle Names only; databases, OEM agents and listeners
should not run from this Oracle Home directory.
2.2.3.2.
(S) The naming of the Oracle Home directory is the concatenation of:
-
The 3-digit version number separated by periods.
-
The letters onames.
Example: 8.1.7onames
2.2.3.3.
(R) A file named README is created in the directory and contains the
exact patch and bit (32/64) versions installed in the Oracle Home.
Page 5
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
2.2.3.4.
(S) An entry is added to /etc/oratab for the Oracle Home using a SID of
the letters onames followed by the 3-digit version without the periods.
Example: onames920
2.3. Standard Product Installation List
A standard installation includes both server and client software to be installed into the
Oracle Home. The Oracle 9i distribution contains both Enterprise and Standard
editions on the same CD-ROM set. There is a bug in the installer when attempting to
install Standard Edition using a Custom install method that incorrectly identifies the
server install as being Enterprise Edition.
2.3.1.(R) 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 starter database during
install or run the sqlnet configuration assistant.
Base Products to Install
Oracle 9i Server
Enterprise Edition Options
- select to install Enterprise Edition
- deselect to install Standard Edition
Net Services 9
- Net Listener 9
Oracle Utilities (all)
Oracle Configuration Assistants (all)
Development Kit (all)
Oracle Java Products (all)
Oracle Enterprise Manager Products
-Intelligent Agent
Oracle Installation Products
-Oracle Universal Installer (Note: install under the new Oracle Home)
Oracle No additional Cost Options (all)
-Use the following URL to Oracles web site for information on the
availability of options for your specific installation
http://www.oracle.com/ip/deploy/database/oracle9i/index.html?packagingandoptions.html
Page 6
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
Section 3. Flexibility
Section 4. Compliance
A post-install review with another DBA is required if GDTS will support the Oracle installation.
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.
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 depot the file <oracle depot>/response/custom.rsp to /tmp/custom.rsp
on
your local server. The file /tmp/custom.rsp will originally be “Read-only”; chmod 644
/tmp/custom.rsp to set the permissions to read/write access for the Oracle user. Open the file
/tmp/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
Page 7
Installation Standards For Oracle On Unix
3/9/2016
Global Database Technical Services
Standards
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.3.
oracle_depot_path> ./runInstaller -silent -responseFile /tmp/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 8
Installation Standards For Oracle On Unix
3/9/2016