Best tips for ASM architecture [message #643758] |
Sat, 17 October 2015 01:22 ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](//www.gravatar.com/avatar/6cfdbdc57ab6eee69f4fb81d1a115c15?s=64&d=mm&r=g) |
fabi88
Messages: 112 Registered: November 2011
|
Senior Member |
|
|
Hi,
1- How many Disk Group is recommended?(one for DATA, one For REDO and ...)
2- What is the right value of allocation unit for each Disk Group? ( what factors should be considered to select size of AU?)
3-How many LUNs for each Disk Group should be considered? What is the effect of the difference in the number of LUNs?
Regards.
|
|
|
|
|
|
Re: Best tips for ASM architecture [message #643780 is a reply to message #643777] |
Sun, 18 October 2015 03:30 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](//www.gravatar.com/avatar/6cfdbdc57ab6eee69f4fb81d1a115c15?s=64&d=mm&r=g) |
fabi88
Messages: 112 Registered: November 2011
|
Senior Member |
|
|
Thanks Michel Cadot,
When there is just one physical disk, for example a disk with 360G storage space, and we create one Disk Group using it, is needed to partition it (for example 8 partition) for creating LUNs(8 Luns) or not(one partition with 360G space(one Lun with 360G space) is enough)?
[Updated on: Sun, 18 October 2015 03:58] Report message to a moderator
|
|
|
|
|
|
|
Re: Best tips for ASM architecture [message #643799 is a reply to message #643798] |
Mon, 19 October 2015 01:15 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
![](/forum/images/custom_avatars/102589.gif) |
Michel Cadot
Messages: 68733 Registered: March 2007 Location: Saint-Maur, France, https...
|
Senior Member Account Moderator |
|
|
I say that forum is not a replacement to reading.
Forum comes AFTER reading when something is not clear.
You waste others time and steal others help time when you do the opposite.
Why should we just repeat the documentation?
I pointed you to the section which answers your first question, that is I did the work you should do before posting here.
This means I spent time for something you should and then did not take this time to help someone who really need it.
[Updated on: Mon, 19 October 2015 01:16] Report message to a moderator
|
|
|
|
Re: Best tips for ASM architecture [message #643807 is a reply to message #643780] |
Mon, 19 October 2015 02:24 ![Go to previous message Go to previous message](/forum/theme/orafaq/images/up.png) ![Go to next message Go to next message](/forum/theme/orafaq/images/down.png) |
John Watson
Messages: 8964 Registered: January 2010 Location: Global Village
|
Senior Member |
|
|
fabi88 wrote on Sun, 18 October 2015 09:30Thanks Michel Cadot,
When there is just one physical disk, for example a disk with 360G storage space, and we create one Disk Group using it, is needed to partition it (for example 8 partition) for creating LUNs(8 Luns) or not(one partition with 360G space(one Lun with 360G space) is enough)?
My opinion: As you you have only one disc the number of LUNs and groups, and the AU size, are largely irrelevant. ASM is not designed to manage such a small environment.
Theoretically, even with one disc multiple partitions will force Unix to create multiple IO queues. But you'll get this benefit (if indeed it is any benefit) without the added complexity of ASM. I would not bother with it at all.
|
|
|
|
|
|