|
|
|
This section contains the following topics:
Oracle Database Installation, Configuration, and Deployment
Oracle includes features that can maximize the efficiency of your file storage system. Consideration of these features when implementing your Oracle MDB may be beneficial.
The Oracle 10g Automatic Storage Management (ASM) is based on this initiative. The main objective of S.A.M.E. offers maximum configuration flexibility and performance tuning by using large I/O and minimize random access by minimizing length of head movement.
For best I/O:
RAID 5 is powerful and inexpensive, but best avoided when configuring Oracle databases. An alternative to RAID 5 is RAID 0, commonly known as disk mirroring.
For optimal performance, the MDB should not be placed on RAID 5 storage subsystem. For best RAID performance, use hardware RAID 1+0. RAID 1+0 is preferred because of the heavy write penalty associated when using RAID 5 and RAID 1 (Mirroring) provide faster READ I/O. If RAID 1+0 (strip + mirror) is not available, then RAID 0+1 (Mirror of strip) would be another alternative.
An Oracle MDB is comprised of several files which store user data, database meta data, and even information to recover from a failure. As such you should take into consideration the type of storage sub-system you will be locating the files on. There are the following options:
Note: File System is the choice recommended for MDB deployment.
The MDB follows the Oracle Optimum Flexible Architecture (OFA) for layout. An OFA implementation is the standard that defines how to set up Oracle Databases across all platforms in a consistent manner.
Place Redo Logs and Archive Logs separate from data files to assist with performance and recovery purposes. Keep key table datafiles on different disks (or separate arrays) and controllers than the corresponding index datafiles if not using ASM.
The Oracle user that is used to run the MDB installation must have database administrator privileges assigned.
Larger block sizes result in more efficient I/O activity at potential expense of less efficient cache utilization and greater strain on the I/O system. An 8KB block size should be utilized in your MDB Oracle deployment. Selecting a block size other than 8KB requires advanced knowledge and should only be done when absolutely required.
Installation allows you to use existing tablespaces or have new ones created for the MDB. If tablespaces are created, a tablespace for data and a tablespace for indexes will be created for optimal performance.
The system defined defaults for temporary and undo tablespaces are used.
Note: Since the MDB schema is predetermined, customers are advised not to alter or add additional tablespaces or tablespaces datafiles without consulting CA support or CA services.
Using Existing Tablespaces for the MDB
If you choose to use existing tablespaces for the MDB, then the tablespaces require a minimum of 200 megabytes of available disk space If this amount of space is not available the creation of the MDB will fail.
Existing tablespaces should have archive logging enabled so that online backups can be taken, archive audit log analysis may be performed, and data recovery options such as complete and point-in-time media are available.
Tablespaces Created by MDB Installation
When the MDB is installed, tablespaces are created with archive logging enabled. Tablespaces are created using the EXTENT MANAGEMENT LOCAL clause, enabling automate extent management. Tablespaces are also created with the SEGMENT SPACE MANAGEMENT AUTO clause enabling Automatic Segment Space Management.
System Temp Tablespace
The MDB uses a system temp tablespace to store temporary tables. At least 50 megabytes of space should be available for this purpose.
AUTOEXTEND is set to enable data files to grow. Proper monitoring of the operating system and disk space should be maintained to insure the space is always available for database growth.
Note: Products such as CA Unicenter Database Performance Management and CA Unicenter NSM may be utilized to automate and monitor such work.
The Global Database Name is the full name of the database which uniquely identifies it from other Oracle databases. The global database name is of the form database_name.database_domain as in omdbprod1.us.ourcompany.com. The database name portion (omdbprod1) designates this as the first production Oracle MDB within the enterprise. The database domain portion (us.ourcompany.com) specifies the domain in which the MDB is located. Together database name and domain make up the Global Database Name.
| Copyright © 2008 CA. All rights reserved. | Tell Technical Publications how we can improve this information |