Oracle Server
The following are notes on setting up the Oracle server software for use with LeasePak. Contact your MSI representative for
more information.
========
Contents
========
A. terminology
B. oracle software installation
C. oracle database creation
D. oracle initialization parameters
E. oracle networking configuration
F. oracle tablespace creation
G. oracle database files
H. oracle instance startup and shutdown
I. oracle optimizer statistics
==============
A. terminology
==============
The terms "oracle database" and "LeasePak database" are not synonymous.
An oracle database is the set of physical files (datafiles, control files, redo log files, etc)
which together constitute an oracle database.
A LeasePak database is implemented as a schema within an oracle database.
An oracle database can contain multiple LeasePak databases.
An oracle "instance" is the set of operating system processes and shared memory segments
that operate on an oracle database. A new instance is created every time oracle is started,
and the instance is destroyed when oracle is shutdown.
The oracle database name and instance name should usually be the same.
=======================================================================
A-1. (Linux) preparation for oracle software installation on Linux
===================================================================
These are the minimum kernel settings for installing
Oracle on Linux for use with LeasePak:
SEMMNI 100
SEMMNS 256
SEMOPM 100
SEMMSL 100
SHMMAX 2147483648
SHMMIN 1
SHMMNI 100
SHMSEG 4096
SHMVMX 32767
===============================
B. oracle software installation
===============================
Install the oracle software according to the platform-specific oracle installation and administration manuals.
===========================
C. oracle database creation
===========================
Use the Oracle Database Configuration Assistant (DBCA) to create the oracle database.
===================================
D. oracle initialization parameters
===================================
Initialization parameter values required by LeasePak:
DB_BLOCK_SIZE = 8192
OPEN_CURSORS = 1500
SESSION_CACHED_CURSORS = 300
OPTIMIZER_INDEX_CACHING = 90
OPTIMIZER_INDEX_COST_ADJ = 25
Initialization parameters to be sized according to the available memory
and expected workload on your system:
DB_CACHE_SIZE
SHARED_POOL_SIZE
PGA_AGGREGATE_TARGET
PROCESSES
It is recommended that MSI review the contents of your initialization parameter file,
in order to check for incompatibilities with the LeasePak software.
==================================
E. oracle networking configuration
==================================
Use Oracle Net Manager or similar GUI tool to configure the Listener and the Net Service Name.
For Oracle 9i only, set the following parameter in the sqlnet.ora configuration file:
TCP.NODELAY=yes
This won't be necessary in Oracle 10g, as Oracle is changing the default for TCP.NODELAY
from "no" to "yes" in 10g.
=============================
F. oracle tablespace creation
=============================
When creating tablespaces for LeasePak data (table and index data), an MSI requirement is to
explicitly specify the SEGMENT SPACE MANAGEMENT AUTO attribute in the CREATE TABLESPACE command.
SQL> CREATE TABLESPACE <tablespace-name> ... SEGMENT SPACE MANAGEMENT AUTO;
========================
G. oracle database files
=========================
An oracle database is composed of several types of disk files:
- control files
- datafiles
- tempfiles
- online redo log files
- archived redo log files
It is recommended that MSI review the layout of your database files.
Information to be provided to MSI:
- which files are stored on raw partitions, and which on "cooked" filesystems
- which cooked filesystems have been mounted to use directio (direct I/O)
- which files are stored on dedicated disks, and which on shared disks
- Raid architecture for each database file
- number of online redo log groups
- number of online redo log multiplexed members per group, and size of each redo log group member
- number of multiplexed control files
- tempfile sizes for the default temporary tablespace
- datafile sizes for the system, undo, and end-user tablespaces
- tablespace and datafile attributes
- character set of the database
- character set of the unix box and value of the NLS_LANG environment variable
Miscellaneous guidelines:
- For some database files, the filesystem containing the files should be mounted
to use directio. Directio prevents double-buffering and yields better performance.
- If you have a battery-backed disk cache in front of your Raid, it is probably better to
bias it towards writing rather than reading. A read cache often does not produce better
performance, because it introduces another layer of double-buffering.
However, a write cache can improve performance by helping redo logging and checkpointing.
- The online redo log files should generally not be stored on Raid 5,
due to the write performance penalty incurred by Raid 5.
A sufficiently sized disk cache which is configured as a write cache
can sometimes mitigate the write performance penalty.
- The online redo log files should be stored on dedicated disks, both for performance and
media-failure protection.
- To prevent data loss from media-failure, production databases should be run in archivelog mode.
- Configure the online redo log files and archived redo log files such that
when LGWR is writing to a device, ARCH is not reading that device.
=======================================
H. oracle instance startup and shutdown
=======================================
To automate instance startup and shutdown when the system is booted, add the instance name to
the MSI_INSTANCES variable in the /etc/mccue_oracle_instances file.
==============================
I. oracle optimizer statistics
==============================
The MSI-provided db_update_statistics script should be periodically run for each LeasePak database
to gather fresh oracle optimizer statistics.
LeasePak Documentation Suite
©
by McCue Systems Incorporated. All rights reserved.
The information contained
in this document is the property of McCue Systems, Inc. Use of the information
contained herein is restricted. Conditions of use are subject to change without
notice. McCue Systems, Inc. assumes no liability for any inaccuracy that may
appear in this document; the contents of this document do not constitute a promise
or warranty. The software described in this document is furnished under license and may be used
or copied only in accordance with the terms of said license. Unauthorized
use, alteration, or reproduction of this document without the written consent
of McCue Systems, Inc. is prohibited.
Your document is loading...
This message should disappear within 5-15 seconds, depending on the size of the document and the speed of your connection to the Documentation Suite.
If you can still see this message after 20 seconds, try clicking the Refresh or Reload button on your Web browser.
If your document still does not load, refer to Document Load Troubleshooting for instructions on how to fix possible problems with either your Documentation Suite installation or Web browser setup.
If you do not have read access to the parent docsuite directory, you will not be able to load the Document Load Troubleshooting document. In this case, contact your network administrator for assistance.