Installing Oracle Database Software

<back to oca>

Use optimal flexible architecture

OFA (Installation Guide) has been developed by consulting division or Oracle in 90 it has been introduced in Oracle database with version 8. It is described on Cary Millsap Whitepaper of 24/09/1995 titled “The OFA Standard – Oracle for Open Systems”. OFA is updated on every new release of Oracle and as of 10gR2 version states:

  1. Naming rules and structure of “mount points”: their name must match the pattern /pm where p is as string constant choosen to represent contents and m is a unique fixed length key that distinguishes one mount point from another. Tipically m is a two digits number such as 01, 02, … . It may also be “AA, AB, …. so /pm may be “/ora01, /ora02 or historically were /u01, /u02.
  2. Oracle Base directory naming rules: ORACLE_BASE=/pm/h/u/
  3. Naming rules and structure of home directories (ORACLE_HOME): /pm/h/u/product/v/type_[n]. Where /pm is mount point as decribed at item 1, h is a string selected from a small set of standard directory names, for example {app, home}, u is the owner (for example “oracle”) v is the version (for example 10.2.0) , type is db, client, crs, companion and describe the type of installation, the optianal n provides for multiple installations of same type of same version product.
  4. Naming rules for administrative data directories, those containing alert, archived logs, etc.: /pm/h/u/admin/d/a or ORACLE_BASE/admin/d/a where d is database name (DB_NAME or SID) and a is subdirectory for specific database administration files, such as bdump, udump, cdump, arch, create
  5. Classification of Oracle files A) Product files, software and tools. B) Administrative files, log, parameter, archive, creation scripts… C) Database Files. D) Local Software

It is good practice to have under $ORACLE_HOME only files dependent on versione, so for SPFILE that defaults to $ORACLE_HOME/dbs may be used a PFILE with SPFILE parameter.

Install software with Oracle Universal Installer

OUI has a standard look and feel on all platforms, it is java-based , it makes dependency checking, it supports unattended istallationss (silent installation) it supports intelligent uninstallations, it can do web-based installations, in fact you can specify an URL such as http://webserver/stage/products.xml for path of staging area. (documentazione)

Identify and configure commonly used environment variables

ORACLE_BASE, ORACLE_HOME, NLS_LANG, ORACLE_SID, LD_LIBRARY_PATH, PATH, …

Use installer log

See (installation Guide)

In the file /etc/oraInst.loc the parameter “inventory_loc” specifies oraInventory path, under oraInventory there is a directory named “logs” and under that directory there are files in the format installActions<date>_<time>.log

If the problem happens during relinking phase, the log is $ORACLE_HOME/install/make.log

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: