When I first went thru this, I took the /u01 thru /u09 not to litterally mean "use /u01 to /u09". I took it as an example where you replace them with more meaningfull path names. So, we started using /oradata01 .... /oradata25 and /oralogs01 .... /oralogs05 ... etc. It was not till years later when I found that they actually MEANT for you to use u01 .... u09. Oh well. ________________________________ From: oracle-l-bounce@xxxxxxxxxxxxx [mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Niall Litchfield Sent: Tuesday, May 11, 2010 4:00 PM To: frits.hoogland@xxxxxxxxx Cc: Freek.DHooge@xxxxxxxxx; ORACLE-L Subject: Re: a quick poll regarding the 11gR2 OFA On Tue, May 11, 2010 at 8:54 PM, Frits Hoogland <frits.hoogland@xxxxxxxxx> wrote: ? Anyone know any history of '/u01'? I guess it was used in the past to have a second '/usr' on a separate mountpoint, to have a clear place which holds the database software. If so, /u02 and further for the datafiles and other database files is really bogus.? ? The original paper is available at http://www.method-r.com/downloads/cat_view/38-papers-and-articles?(the author's current home online) and well worth reading.?I'll just quote the objectives here, and remember what the typical server config was like in 1990, specifically relatively few, directly attached, disks on really rather expensive hardware. ? Requirement 1. The file system must be organized so that it is easy to administer growth from: adding data into existing databases, adding users, creating databases, and adding hardware. ? Requirement 2. It must be possible to distribute I/O load across sufficiently many disk drives to prevent a performance bottleneck. ? Requirement 3. It may be necessary to minimize hardware cost. ? Requirement 4. It may be necessary to isolate the impact of drive failure across as few applications as possible. ? Some of these objectives are well addressed by SAN technology, LVMs and so on. I think the idea stacks up pretty well. As far as naming goes, well I think you can tell a mathematically literate individual who understood UNIX?filesystems of the time?wrote it?:( ? Name all mount points that will hold sitespecific data to match the pattern /pm where p is a string constant chosen not to misrepresent the contents of any mount point, and m is a unique fixedlength key that distinguishes one mount point from another? ? Unfortunately I'm not entirely convinced that current definers of 10 and 11g?OFA, are quite so rigorous. :( -- Niall Litchfield Oracle DBA http://www.orawin.info This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately.