This is a discussion on Oracle installation using Sun Volume Manager within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> Hello gurus, The DBA in our team has a task to install Oracle DB server in atleast 3 Sun ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hello gurus, The DBA in our team has a task to install Oracle DB server in atleast 3 Sun Servers. Since, she lakcs experience and since I am unaware of Oracle myself I need help in this topic. If any one can help that will be great. My questions are: How many filesystems are required for Oracle DB installation and how do I create those filesystems using Sun Volume Manager? Knowing the fact the internal drive has a limit of only 7 fiesystems/ partitions how should I create the HDD partitions? If I am missing something here please let me know. thanks to all. |
| |||
| On 2007-03-15 17:57:19 +0000, "learner" <Zabaloch@gmail.com> said: > How many filesystems are required for Oracle DB installation and how > do I create those filesystems using Sun Volume Manager? > Knowing the fact the internal drive has a limit of only 7 fiesystems/ > partitions how should I create the HDD partitions? If you have only one disk then the only purpose of multiple filesystems is isolation. So (apart from any system information) make one large metadevice and use soft partitions to carve it up if need be. |
| |||
| learner wrote: > Hello gurus, > > The DBA in our team has a task to install Oracle DB server in atleast > 3 Sun Servers. Since, she lakcs experience and since I am unaware of > Oracle myself I need help in this topic. > If any one can help that will be great. > My questions are: > > How many filesystems are required for Oracle DB installation and how > do I create those filesystems using Sun Volume Manager? > Knowing the fact the internal drive has a limit of only 7 fiesystems/ > partitions how should I create the HDD partitions? > > If I am missing something here please let me know. > thanks to all. > I think you are missing something. While you can install Oracle on a single internal disk, performance will be somewhere between horrible and impossible! Oracle needs a minimum of five disks (physical disks) for best performance. For a very small and little used database you might get away with a single disk but, if that is the case, why are you paying Oracle's outrageous prices? Look in the index of your Oracle documentation for "OFA" (I think I recall that correctly). You should find a discussion of how many disks you will need and how to lay out the database using those disks; e.g. redo-logs get a disk by themselves, you don't put a table and its indices on the same disk, etc, etc. The last time I had systems running Oracle we had something like nine or ten mirror sets (hardware RAID 1). Oracle does not insist on a filesystem. It is quite happy with raw disk; it just wants a lot of them. :-) |
| |||
| Hey Richard, I am just worried about the binaries for the Orale DB at the moment. I know it requires a lot of disk, but all of that will be created over the SAN. I am not sure about all of that part, but I am hoping the DBA would do that part. I am currently writing up the process that I would have to follow in order to install just the Oracle Binaries on a particular server. Any help in making me understand that it will be great. Thanks |
| |||
| learner wrote: > Hey Richard, > I am just worried about the binaries for the Orale DB at the moment. I > know it requires a lot of disk, but all of that will be created over > the SAN. I am not sure about all of that part, but I am hoping the DBA > would do that part. > I am currently writing up the process that I would have to follow in > order to install just the Oracle Binaries on a particular server. > > Any help in making me understand that it will be great. > Thanks > > I've never installed Oracle successfully! I tried once, on an X86 system running Solaris 8. All we needed was the client part, the actual database was running on another machine. I followed the directions but couldn't get it to work no matter what I did. Someone else finally copied a bunch of files from a system where it was installed and working. . . . Follow the directions with great care and, when it doesn't work, seek professional help. |
| ||||
| In article <1174072591.791254.110620@d57g2000hsg.googlegroups .com>, learner <Zabaloch@gmail.com> wrote: >Hey Richard, >I am just worried about the binaries for the Orale DB at the moment. I >know it requires a lot of disk, but all of that will be created over >the SAN. I am not sure about all of that part, but I am hoping the DBA >would do that part. Silly question: other than that the Oracle binaries take up smaller amount of space than your SAN prople probaly want to allocate a LUN for, why don't you just carve off a LUN from the SAN for the Oracle binaries? In general, you'll only need one partition for each unique set of Oracle binaries (e.g., one for /oracle/product/9.2, one for /oracle/product/1.2, etc.). Each of these will be relatively small. You *might* also want to create an area for $ORACLE_HOME so that your dba doesn't fill your harddrive while staging install files. >I am currently writing up the process that I would have to follow in >order to install just the Oracle Binaries on a particular server. Like I said, parent directory for the Oracle binaries. This can be a subdirctory of any filesystem on your root drive, its own slice off the root drive, a dedicated SAN-local LUN. How you do it depends greatly on your environment's policy or your/your dba's preference. The binaries are the *easy* part (you want real fun, wait till they want to deploy a multiple-SID RAC 10g environment!) -tom -- "You can only be -so- accurate with a claw-hammer." --me |