The document discusses options for partitioning disks and creating mount points for installing an operating system and Oracle software. It is recommended to:
1. Create 3 partitions - a large root partition, a 128MB+/boot partition, and a swap partition equal to 2x RAM for systems under 4GB of RAM.
2. Do not create separate partitions like /u01 and /u02 for Oracle files, as this is an outdated practice. Instead, create a single large partition or raw disks for Oracle Automatic Storage Management (ASM) to manage database storage.
3. If not using ASM, a single mount point like /oracledb is sufficient for Oracle to create an Optimized Flexible Architecture
The document discusses options for partitioning disks and creating mount points for installing an operating system and Oracle software. It is recommended to:
1. Create 3 partitions - a large root partition, a 128MB+/boot partition, and a swap partition equal to 2x RAM for systems under 4GB of RAM.
2. Do not create separate partitions like /u01 and /u02 for Oracle files, as this is an outdated practice. Instead, create a single large partition or raw disks for Oracle Automatic Storage Management (ASM) to manage database storage.
3. If not using ASM, a single mount point like /oracledb is sufficient for Oracle to create an Optimized Flexible Architecture
The document discusses options for partitioning disks and creating mount points for installing an operating system and Oracle software. It is recommended to:
1. Create 3 partitions - a large root partition, a 128MB+/boot partition, and a swap partition equal to 2x RAM for systems under 4GB of RAM.
2. Do not create separate partitions like /u01 and /u02 for Oracle files, as this is an outdated practice. Instead, create a single large partition or raw disks for Oracle Automatic Storage Management (ASM) to manage database storage.
3. If not using ASM, a single mount point like /oracledb is sufficient for Oracle to create an Optimized Flexible Architecture
having 2 Hard disks of size 250GB and 200GB, so what i need to do is
1. While doing installation of OS need to create 2 partitions under Device "Hard Drives " along with others which are required, e.g. Device Mount Point Type Size /dev/sdb1 /boot ext3 102 MB /dev/sdb2 / ext3 51200 MB /dev/sdb3 / ext3 307200 MB
2. After completion of OS installation will create 2 Directories at root, $ mkdir /u01 $ mount /dev/sdb2 /u01
$mkdir /u02 $ mount /dev/sdb3 /u02
3. After that will start using that mount points like /u01 for storing Setup files e.g. /u01/StageR12/ and /u02 for Oracle EBS R12 installation e.g. /u02/OraApps/
m i on right path? o Report Abuse
o Like (0) Helpful Answer6. Re: How to create Mount Point in Linux
BillyVerreynne 23-Mar-2011 05:58 (in response to PriyankaPawar) You're on the right path.
Keep in mind though what you need partition wise just for o/s install. You should have at least 3 partitions: - a ?? GB partition for the / (root) mount (the size depends on what you will install and how much space you will need for running that s/w) - a 128MB or larger partition for the /boot mount - a ?? GB partition as swap space mount (typically rule of thumb is 2x RAM for 4GB and lower, else around 25% of total RAM)
I would not create separate partitions for the old-style +/u01+ mount points for Oracle. That part of the OFA (Oracle Flexible Architecture) standards are old and pre-ASM and pre- automated Oracle managed data files.
You need space for installing an Oracle Home. I do not see the need for a dedicated mount point for that. I use the root file system.
You need space for the actual database. If you use Oracle ASM, then I would create raw partitions (across disks) to be used for database storage. These will not be mounted or formatted. Instead these will be assigned to an ASM diskgroup (and striped by default) and used for database storage.
If you do not use ASM, then you need a cooked file system for storage of database file. In that case separate mount point(s) make sense. Also, it makes sense not to manually apply the old OFA standards, but instead use Oracle managed database files. In that case you need a single mount point (e.g.<i>/oracledb</i>) - and set that as the base directory for Oracle to use for the database. Oracle will create an OFA compliant database directory tree and files under that base directory/mount point.
Keep in mind that the more mount points you have for the database, the more difficult your job becomes to manage storage. The easiest is a single mount point for the database and using Oracle to manage the OFA compliant side for you on that mount point.
Also, you cannot and should not attempt some kind of manual striping layout of the database across multiple mountpoints. This may have made some sense back 10+ years ago. It no longer does. o Report Abuse
o Like (0) 7. Re: How to create Mount Point in Linux
PriyankaPawar 23-Mar-2011 06:23 (in response to BillyVerreynne) okay... yes actually there is no need to create two mount points here like /u01 and /u02. I can create directory as /u01 at root level and store my setup files there too no issues.
But as far as Oracle EBS installation is concern I m not doing it manually so definitely Oracle will use OFA structure for managing Directory structure and installation of software, the reason behind creation of separate mount point is to provide Base Directory for further installation procedure.
What do you suggest, can i assign total space required for setup files and Software installation to root directory and after that instead of creating separate mount points just to create two directories as /u01 and /u02 and proceed with my work ? o Report Abuse
o Like (0) 8. Re: How to create Mount Point in Linux
BillyVerreynne 23-Mar-2011 08:22 (in response to PriyankaPawar) Cannot comment on EBS - have never installed it.
Our complete end-to-end application and business layers are inside the database as PL/SQL code. So the app and business layer scales with the database. And as we use RAC, we leverage the scalability, high availability and redundancy features that comes with the database layer, for the app and business layers too. A lot more flexible and significant simpler and more elegant than separating these layers into separate s/w stacks and then separating these over (slow) hardware boundaries - dealing with increased licensing and h/w costs, dealing with multiple different languages for development, having to troubleshoot and administer several s/w stacks, etc. etc.
In our case the only external moving part is standard Apache. So no need for EBS.. nor the slightest hint of desire to install it either. :-) o Report Abuse
o Like (0) 9. Re: How to create Mount Point in Linux
nop 23-Mar-2011 10:20 (in response to PriyankaPawar) I'd say it depends on the size of your root partition. What is your output of "df -h" command? If root is too small to store several GB of data, then you will either need to resize your root partiton, or mount another disk into i.e. /u01. It may also work to create a symlink and have /u01 point to a directory on another existing disks, e.g. ln -s /big_disk/u01 /u01
Edited by: Dude on Mar 23, 2011 3:17 AM o Report Abuse