I will defer to a much more intelligent individual than myself to detail the Oracle components, as I cannot even spell Larry Ellison. I do recommend reading the Oracle Database Deployment Considerations document (available via InfoSight) if you have not:
Edit: replied to wrong post ... removed unrelated section.
As Ryan pointed out, please review the Oracle Database Deployment and Consideration guide. This has the most up to date information. We don't necessarily recommend changing the allocation unit size (AU Size), unless there is a specific need/requirement.
Can you tell me where you are seeing that recommendation? In some of the older documents, we recommended 64MB, but this was recommended mostly from a "max" performance perspective.
The AU Size only comes into play during the writing of new data to the diskgroup. It will help to lay the data down in a more sequential manner. I have seen some benefit with larger AU Sizes when dealing with sequential read performance.
I typically recommend a 16MB size.
As far as diskgroup breakouts...we recommend the following:
1. ASM diskgroup for datafiles (4-8 LUNs)
2. ASM diskgroup for redo files (2-4 LUNs)
3. ASM diskgroup for archive/multiplex redo files (2-4 LUNs)
Could you go with less LUNs and less diskgroups? Sure...it all depends on what this database is being used for. For smaller non-production databases you could consider the following:
1. ASM diskgroup for datafiles (2-4 LUNs)
2. ASM diskgroup for redo files and archives (1-2 LUNs)
As far as mirroring the redo logs...this is somewhat up to you. It certainly doesn't hurt to mirror them. We've seen some customers mirror them in the same diskgroup, and then others mirror them to a separate diskgroups. In my opinion, I would use the first option above...three diskgroups, and then use the number of LUNs that are necessarily (again, the number of LUNs is based on the requirements of the database).
The Oracle Database Deployment and Consideration guide goes into each of the above in more detail.
Hope that helps!
As always, let me know if you have any additional questions!
Thanks for the updates.
Regarding "Can you tell me where you are seeing that recommendation? In some of the older documents, we recommended 64MB, but this was recommended mostly from a "max" performance perspective."
I found the recommendation on the following document:
Nimble Storage for Oracle Database on OL6 & RHEL6 with Fibre Channel or iSCSI
That is one of the older docs that I was referring to.
Did you recently download that from InfoSight, or was it something you downloaded a while back?
There are new documents that cover our deployment considerations or “best practices”.
Those should be the latest documents that I would consider reviewing.
Hope that helps!
On an Oracle RAC/ASM environment, Nimble white papers recommend a separate disk group for the online logs.
They also recommend setting the allocation unit of the disk groups to 64MB instead of the default 1MB.
Is there any documentation that further explains these recommendations?
Does Nimble recommend mirroring the online logs?