ORACLE_HOME for grid components

[edstevens]

In your papers on setting up test systems under vbox, I notice that when you create the two ORACLE_HOMEs (one for db, one for grid components) you create the directories like this:

mkdir -p /u01/app/11.2.0/grid
mkdir -p /u01/app/oracle/product/11.2.0/db_1

My question is why do you put the db home several directory levels lower than the grid home? Why would it not be

mkdir -p /u01/app/oracle/product/11.2.0/grid
mkdir -p /u01/app/oracle/product/11.2.0/db_1

or

mkdir -p /u01/app/11.2.0/grid
mkdir -p /u01/app/11.2.0/db_1

When you then set ORACLE_BASE=/u01/app/oracle, that puts the home for grid outside of the ORACLE_BASE structure.

What am I missing?

[Tim...]

Hi.

The optimal flexible architecture proposed by Cary millsap during his days at Oracle gave rise to this commonly used directory structure.

Code: Select all

/u01/app/oracle/product/11.2.0

later this changed to include another sub-directory for different installation of the same version.

Code: Select all

/u01/app/oracle/product/11.2.0/db_1
/u01/app/oracle/product/11.2.0/db_2

Back in the very early days of RAC, everything was under the same ORACLE_BASE and it was common to see this.

Code: Select all

/u01/app/oracle/product/11.2.0/crs
/u01/app/oracle/product/11.2.0/db_1

Pretty soon, Oracle started to recommend that having the crs (or now grid infrastruture) under the same ORACLE_BASE was a mistake because CRS/GI needs different permission and ownership of some of the parent directories. For this reason, Oracle moved the inventory (oraInventory) our of the ORACLE_BASE and placed it one directory before.

Code: Select all

# now
/u01/app/orainventory

# then
/u01/app/orainventory

You often get people using completely different mount points for GI and ORACLE_HOME.

Cheers

Tim...